-
-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syslog messages are not properly formatted #285
Comments
BSD-syslog or legacy-syslog messages look OK now. I don't have setup to test IETF-syslog messages at this moment. |
When testing with rsyslog-ng I split the logs by the hostname in the logline. It seems to be okay like 99% of the time, but then randomly I get hostnames with stuff like
It almost looks like it keeps appending the text and putting out the entire message again. That being said I see the same thing in the expected log file name:
It's just that in some cases the first part of the line is not the host IP address, it's some random truncated text. So I wonder if there is an underlying issue here with the buffer size. |
There is no real buffer reserved for the syslog messages except for the UDP packet size. |
I will see if I can use wireshark to find something. It smells like somehow the buffer isn't clearing and its concatenating, but it could be like you said and the messages are overflowing a buffer on the rsyslog end. |
Since this is working 99% of the time I will consider this issue as resolved. |
Perform all steps below and tick them with [x]
Describe the bug
As reported by @geiseri in issue: Allow ANSI codes to be disabled for syslog #261 the syslog messages are garbled.
To Reproduce
Configure syslog and watch the output below.
Expected behavior
Properly formed IETF (RFC 5424) / BSD (RFC 3164) syslog messages to be sent.
Screenshots or video
The text was updated successfully, but these errors were encountered: