We had Enabled Syslog Server for a while but didn't use it. Because of this I disabled Syslog server in Devolutions Server (under Administration > Server settings > Logging > Syslog Server > Log in to Syslog server).
After that we receive every minute a large amount of emails about Syslog server is unreachable. Because of this I had to re enable this setting and the alerts stopped.
We use version 2025.3.11.0 of Devolutions Server.
This looks like a bug to me. Is this a known bug and can this be solved so I can disable Syslog Server?
Thanks for reporting this.
I’ll try to reproduce the behavior on my side to see if I can confirm the same results when disabling the Syslog Server configuration. I’ll report back once I have more information.
Elevate your learning - Join the Devolutions Academy !
Kind regards,
Kelly
@hjbos In my testing, I received a notification when I enabled the syslog server option in the logging. My configuration was set deliberately to fail to ensure a notification message was generated. Once the failure to connect massage was received, I removed the syslog option from the logging settings and two notification messages were almost immediately triggered, again stating a failure to connect to the syslog server. I received not further notifications afterward.
How often are you seeing these notifications? It sounds like something went awry with save when removing the syslog option.?. Have you tried to add/remove and resave again? Maybe stop/start the DVLS from the Console after saving the removal of the syslog option.