On Mon, 21 Dec 2015, Spyropoulou, Theoni Katerina (Nokia - GR/Athens) wrote:

Hello,

I am observing the following errors:
rsyslogd: Framing Error in received TCP message: delimiter is not SP but has 
ASCII value 93. [v8.10.0]
rsyslogd: received oversize message: size is 1560608370 bytes, max msg size is 
4096, truncating... [v8.10.0]

Are they related to each other? Why "$InputTCPSupportOctetCountedFraming" is 
not even recognized (rsyslogd-3003: invalid or yet-unknown config file command 
'InputTCPSupportOctetCountedFraming' - have you forgotten to load a module? [v8.10.0 try 
http://www.rsyslog.com/e/3003 ])?

configuration is done as follows:

$MaxMessageSize 4096
$ModLoad immark
$ModLoad imtcp
$EscapeControlCharactersOnReceive off
$OptimizeForUniprocessor off
$InputTCPServerRun 1025
$InputTCPMaxSessions 1000
$InputTCPSupportOctetCountedFraming off
$IncludeConfig /etc/rsyslog-master.d/*.conf

you would be better off using the new style config to load the modules and set the options. I think you have some things in the wrong order (you need to set parameters for the input moduel before you start it with serverrun). It will be much clearer what's happening if you use the new syntax.

David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to