Malformed month names in syslog messages cause logengine crash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
Medium
|
Morten Brekkevold |
Bug Description
A customer keeps getting these error message from the logengine in their cronmail:
ERROR:logengine
Traceback (most recent call last):
File "/usr/lib/
message = create_
File "/usr/lib/
timestamp = datetime.
TypeError: an integer is required
Presumably, the start of this message has been truncated by the previous run of the logengine (which is bad by itself, but has to be expected due to the braindead way logengine works).
The message is basically unparseable, and can easily be thrown away. But instead, it crashes the logengine,, which potentially prevents further processing of log lines.
Changed in nav: | |
status: | Fix Committed → Fix Released |
fix here: https:/ /nav.uninett. no/hg/stable/ rev/175bd2b89bf 2