[issue27373] logging.handlers.SysLogHandler with TCP not working on rsyslog5.8

Changes by Vinay Sajip : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue27373] logging.handlers.SysLogHandler with TCP not working on rsyslog5.8

Stéphane Wirtel added the comment: For me, it's an issue with the management of the protocol in rsyslog and not with the logging library. You can close the issue. -- nosy: +matrixise status: pending -> open ___ Python tracker

[issue27373] logging.handlers.SysLogHandler with TCP not working on rsyslog5.8

Vinay Sajip added the comment: If no more information is available, I will close this issue soon as "not a bug". -- status: open -> pending ___ Python tracker

[issue27373] logging.handlers.SysLogHandler with TCP not working on rsyslog5.8

Vinay Sajip added the comment: If it works fine with rsyslog 8.19 but fails with rsyslog 5.8, what exactly is logging doing wrong? How is rsyslog configured in the two cases? How exactly was the fail.log generated (I know you said tcpdump was used, but can you provide more detail)? I'm not

[issue27373] logging.handlers.SysLogHandler with TCP not working on rsyslog5.8

New submission from 吴冉波: logging.handlers.SysLogHandler with TCP not working on rsyslog5.8, but newer version rsyslog8.19 is fine. I use SysLogHandler with TCP to send message to remote rsyslog server failed, but success with bash below: echo "<133>$0[$$]: Test syslog message from Netcat" |