[issue28404] Logging SyslogHandler not appending '\n' to the end

Change by rea haas : -- nosy: +reahaas nosy_count: 2.0 -> 3.0 pull_requests: +23337 pull_request: https://github.com/python/cpython/pull/24556 ___ Python tracker ___

[issue28404] Logging SyslogHandler not appending '\n' to the end

Change by Vinay Sajip : -- resolution: not a bug -> out of date status: pending -> closed ___ Python tracker ___ ___

[issue28404] Logging SyslogHandler not appending '\n' to the end

José Manuel added the comment: Sorry to bother you again, but I've tested this not only with Fluentd, but with a RSYSLOG server and it does not work with TCP except if you manually add the trailer LF character. Other than that, UDP default transport protocol has no issues and works fine with

[issue28404] Logging SyslogHandler not appending '\n' to the end

Vinay Sajip added the comment: > So I think it must be a Fluentd error. So I'll close this. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue28404] Logging SyslogHandler not appending '\n' to the end

Changes by Berker Peksag : -- nosy: +vinay.sajip ___ Python tracker ___ ___

[issue28404] Logging SyslogHandler not appending '\n' to the end

José Manuel added the comment: After reading the RFC5424 it seems that there is no such "new line message delimiter": 4.3.1. Message Length The message length is the octet count of the SYSLOG-MSG in the SYSLOG-FRAME. A transport receiver MUST use the

[issue28404] Logging SyslogHandler not appending '\n' to the end

New submission from José Manuel: I'm using SyslogHandler from logging.handlers to send syslog messages to a Fluentd input (https://github.com/fluent/fluentd/blob/master/lib/fluent/plugin/in_syslog.rb), both in TCP and UDP. UDP works fine, but TCP does not work. The "problem" is that the