Unexpected EOF in Syslog Notification from Devolutions Server
I recently set up notification in DPS to send "Entry" events to my elasticsearch cluster.
Problem is, there is a strange character in the syslog message that cannot be interpreted by the TCP syslog input, so syslog parsing fails.
Notifications look like this:
The problem is definitely not on the elastic side because I also grabbed the same line with the same symbol via tcpdump.
Out DPS Version is 2023.1.8.0.
85491e93-558f-43e0-86a4-54cdd5bcb725.png
All Comments (7)
Hello,
I verified on my end, and I also receive a strange character in the Syslog:
When copying the string, it is the following
‹¯¨
I will verify with the engineering team if it can be removed, since it does not seem to have any purpose.
Best regards,
Richard Boisvert
ca7a21dc-bc6e-42d4-9cbe-17b6489058b9.png
Do you have any update on this?
Hello,
QA is currently testing the fix, it should be available in the next Devolutions Server release.
Best regards,
Richard Boisvert
Awesome. Thank you!
Hello,
The fix is available in the 2023.2.2 version, which is now available. Let us know if you still have any issues.
Best regards,
Richard Boisvert
Just updated and it works! Great support as always.
Thanks
Hello,
Glad to see it fixed your issue, thank you for your comment!
Best regards,
Richard Boisvert