Closed Bug 599032 Opened 15 years ago Closed 11 years ago

Need better logging of thrift errors

Categories

(Socorro :: General, task)

task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dre, Assigned: lars)

Details

When a processor shuts down due to a thrift problem, it outputs a message that, while pithy, is not very informative. I need some clue as to what exception Thrift returned so I can try to figure out what is going on and fix it.
All exceptions are logged in the same way throughout the Socorro Python code: the exception class, the message embedded within the exception (if any), a traceback and finally a pithy comment. If all you are seeing is the pithy comment, then you need to scroll back in the logs the see the rest of the messages. There is the possibility that the components of the exception may be physically separated in the log because of interleaving mutlithreading. If there is an example where the logs are missing all the components of exception handling, please attach it so that it can be located and corrected.
Component: Socorro → General
Product: Webtools → Socorro
long resolved
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.