Unspecified IOExeption on admin server / logging failure

Steps to reproduce

Steps to reproduce:
1. I started a matterhorn admin server with "service matterhorn start"
2. I ingested serveral jobs with the inbox.
3. The Matterhorn logs show no errors
4. In the bash where I executed the service script, I get the IOExeption in the code snippet section several times (20+). IT DOES NOT SHOW UP IN THE LOGS!

Actual Results:

Expected Results:

Workaround (if any):

Activity

Show:
Tobias Wunden
January 31, 2012, 12:42 AM

The only reason I can see for this to happen is that somewhere in the Jetty code, the exception is written to std error or std out, so it doesn't look like a logging configuration error to me. It may help to attach the debugger to the admin machine and set an exception breakpoint (IOException) to find out what kind of communication is faling.

Greg Logan
May 19, 2019, 3:33 AM

This continues to pop up on occasion, although more of them show up in the logs. I'm going to keep this open since it does occasionally still slip through to stdout or stderr

Greg Logan
October 9, 2019, 9:43 PM

I remember what you are talking about, but not the specifics. JIRA appears to have lost the snippet as well. Please refile if this is still occurring.

Assignee

Unassigned

Reporter

Rüdiger Rolf

Severity

Data Loss/Corruption

Tags (folksonomy)

None

Components

Fix versions

Affects versions

Priority

Minor
Configure