This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author elelement
Recipients elelement
Date 2016-10-10.14:43:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476110606.71.0.15020812007.issue28404@psf.upfronthosting.co.za>
In-reply-to
Content
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 message length to delimit a syslog message
--------------------------------

So I think it must be a Fluentd error. This is what caused my confusion:

From in_syslog.rb (https://github.com/athenahealth/fluent-plugin-newsyslog/blob/master/lib/fluent/plugin/in_newsyslog.rb):

--------------------------------
# syslog family add "\n" to each message and this seems only way to split messages in tcp stream
Coolio::TCPServer.new(@bind, @port, SocketUtil::TcpHandler, log, "\n", callback)
--------------------------------
History
Date User Action Args
2016-10-10 14:43:26elelementsetrecipients: + elelement
2016-10-10 14:43:26elelementsetmessageid: <1476110606.71.0.15020812007.issue28404@psf.upfronthosting.co.za>
2016-10-10 14:43:26elelementlinkissue28404 messages
2016-10-10 14:43:26elelementcreate