You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If for some reason the Syslog Server is not able to start, for example by missing permissions on address binding, there's no way to detect it, since the UDP implementation "swallows" the exception.
@atduarte This is a relict from the original source code.
We're only using some parts of syslog4j in Graylog and the server implementations are not part of that and we have no interest in fixing issues in these parts ourselves.
If for some reason the Syslog Server is not able to start, for example by missing permissions on address binding, there's no way to detect it, since the UDP implementation "swallows" the exception.
See https://github.com/graylog-labs/syslog4j-graylog2/blob/master/src/main/java/org/graylog2/syslog4j/server/impl/net/udp/UDPNetSyslogServer.java#L66.
Is there a reason behind this design choice?
The text was updated successfully, but these errors were encountered: