[issue6444] multiline exception logging via syslog handler

Vinay Sajip added the comment: > Do you suggest to file bug report to syslog-ng maintainer? Yes, I do. Otherwise you can't use it as a drop-in replacement, which people would expect to be possible. -- status: open -> closed ___ Python tracker

[issue6444] multiline exception logging via syslog handler

Max Arnold added the comment: Sorry for long delay, I was on vacation. I have installed sysklogd, metalog and syslog-ng on a virtual machine and executed test script. First two daemons log exception as single concatenated line. Syslog-ng splits it as described in original report. Do you sugge

[issue6444] multiline exception logging via syslog handler

Simon Litchfield added the comment: >From the manual for logging.handlers.SysLogHandler -- emit(record) The record is formatted, and then sent to the syslog server. If exception information is present, it is not sent to the server. Ideal, for me, would be to have each traceback line logged as

[issue6444] multiline exception logging via syslog handler

Vinay Sajip added the comment: Marked as pending, as there has been no activity for a while. Will close if there is no followup. -- status: open -> pending ___ Python tracker ___

[issue6444] multiline exception logging via syslog handler

R. David Murray added the comment: I can confirm the issue with syslog-ng, and also that it works fine with FreeBSD's syslogd. That said, in the googling I did I ran across code from another project that splits log lines at newlines and also if the logged line is too long...apparently some impl

[issue6444] multiline exception logging via syslog handler

Max Arnold added the comment: I'll try to investigate this issue a bit more in a few days. I plan to compare sysklogd, sylog-ng and probably metalog. Maybe this issue is specific to syslog-ng only. -- status: pending -> open ___ Python tracker

[issue6444] multiline exception logging via syslog handler

Vinay Sajip added the comment: I'm using whatever came with my Ubuntu system - I supposes that's syslogd. Perhaps there's some additional configuration with syslog-ng which will give you the results you want? Plainly, logging is send all the information across, whether it's via UDP or a domain

[issue6444] multiline exception logging via syslog handler

Max Arnold added the comment: Which syslog daemon you use? I've encountered this on syslog-ng. There is stripped down syslog-ng.conf (messages with facility LOCAL0 are routed to /var/log/local.log and all others to /var/log/default.log): #--

[issue6444] multiline exception logging via syslog handler

Vinay Sajip added the comment: Well, I copied your script to "log1.py" and ran it twice. Here's a screenshot from my system log viewer: http://imgur.com/EYnfQ.png I know you can't see all the output in the screenshot, but if I scroll to the right as far as possible I can see that all the excep

[issue6444] multiline exception logging via syslog handler

Max Arnold added the comment: > Why can't you either use %r in the format string, or define your own handler/formatter to do exactly what you want? I'm describing default behaviour of logger.exception(). Out of the box (with SyslogHandler and "/dev/log") I'm unable to use it, because of this pr

[issue6444] multiline exception logging via syslog handler

Vinay Sajip added the comment: Why can't you either use %r in the format string if you know you'll be printing out multiple lines, or define your own handler/formatter to do exactly what you want? I can't see how to provide what you need in a generally useful way in the stdlib. -- assig

[issue6444] multiline exception logging via syslog handler

New submission from Max Arnold : I use syslog message routing mechanism to log high-priority messages from my python code to separate file. When exceptions are logged, only first line routed to specified file, and the rest goes in /var/log/messages. Such problem exists when SyslogHandler instan