SyslogAppender failing silently
I'm trying to setup SyslogAppender to log to a virtual machine that's running rsyslog, and because of a firewall rule on the VM, SyslogAppender wasn't connecting to rsyslog, but I didn't see any errors or warnings from Logback, even after setting a OnConsoleStatusListener. If I change the "syslogHost" parameter to a non-existing name, I get an error message on the console, but the same doesn't happen for a refused connection. I expected to see some sort of notification about this problem. Regards, Daniel Serodio
Sounds like a bug. Could you create a jira issue for this please? On 15/08/2011 10:40 PM, Daniel Serodio (lists) wrote:
I'm trying to setup SyslogAppender to log to a virtual machine that's running rsyslog, and because of a firewall rule on the VM, SyslogAppender wasn't connecting to rsyslog, but I didn't see any errors or warnings from Logback, even after setting a OnConsoleStatusListener.
If I change the "syslogHost" parameter to a non-existing name, I get an error message on the console, but the same doesn't happen for a refused connection. I expected to see some sort of notification about this problem.
Regards, Daniel Serodio
-- QOS.ch, main sponsor of cal10n, logback and slf4j open source projects, is looking to hire talented software developers. For further details, see http://logback.qos.ch/job.html
Was it sending the messages via udp? If so, there is no way to know that the firewall has blocked the udp packets. On 15 Aug 2011, at 21:49, Ceki Gülcü <ceki@qos.ch> wrote:
Sounds like a bug. Could you create a jira issue for this please?
On 15/08/2011 10:40 PM, Daniel Serodio (lists) wrote:
I'm trying to setup SyslogAppender to log to a virtual machine that's running rsyslog, and because of a firewall rule on the VM, SyslogAppender wasn't connecting to rsyslog, but I didn't see any errors or warnings from Logback, even after setting a OnConsoleStatusListener.
If I change the "syslogHost" parameter to a non-existing name, I get an error message on the console, but the same doesn't happen for a refused connection. I expected to see some sort of notification about this problem.
Regards, Daniel Serodio
-- QOS.ch, main sponsor of cal10n, logback and slf4j open source projects, is looking to hire talented software developers. For further details, see http://logback.qos.ch/job.html _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
Yes, because Logback's SyslogAppender currently work only with UDP. Thanks for the explanation, make sense. Ceki, should I file a new issue, or should I comment on LBCLASSIC-116 (SyslogAppender should support RFC 5424) ? Regards, Daniel Serodio David Roussel wrote:
Was it sending the messages via udp? If so, there is no way to know that the firewall has blocked the udp packets.
On 15 Aug 2011, at 21:49, Ceki Gülcü<ceki@qos.ch> wrote:
Sounds like a bug. Could you create a jira issue for this please?
On 15/08/2011 10:40 PM, Daniel Serodio (lists) wrote:
I'm trying to setup SyslogAppender to log to a virtual machine that's running rsyslog, and because of a firewall rule on the VM, SyslogAppender wasn't connecting to rsyslog, but I didn't see any errors or warnings from Logback, even after setting a OnConsoleStatusListener.
If I change the "syslogHost" parameter to a non-existing name, I get an error message on the console, but the same doesn't happen for a refused connection. I expected to see some sort of notification about this problem.
Regards, Daniel Serodio
-- QOS.ch, main sponsor of cal10n, logback and slf4j open source projects, is looking to hire talented software developers. For further details, seehttp://logback.qos.ch/job.html _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
Although RFC 5424 mentions various transports I don't think adding TCP support to the existing syslog appender would be appropriate for LBCLASSIC-116. The formatting of the systog records is a bit different in RFC 5424 than in "normal" BSD syslog records. Ralph On Aug 17, 2011, at 11:29 AM, Daniel Serodio (lists) wrote:
Yes, because Logback's SyslogAppender currently work only with UDP. Thanks for the explanation, make sense.
Ceki, should I file a new issue, or should I comment on LBCLASSIC-116 (SyslogAppender should support RFC 5424) ?
Regards, Daniel Serodio
David Roussel wrote:
Was it sending the messages via udp? If so, there is no way to know that the firewall has blocked the udp packets.
On 15 Aug 2011, at 21:49, Ceki Gülcü <ceki@qos.ch> wrote:
Sounds like a bug. Could you create a jira issue for this please?
On 15/08/2011 10:40 PM, Daniel Serodio (lists) wrote:
I'm trying to setup SyslogAppender to log to a virtual machine that's running rsyslog, and because of a firewall rule on the VM, SyslogAppender wasn't connecting to rsyslog, but I didn't see any errors or warnings from Logback, even after setting a OnConsoleStatusListener.
If I change the "syslogHost" parameter to a non-existing name, I get an error message on the console, but the same doesn't happen for a refused connection. I expected to see some sort of notification about this problem.
Regards, Daniel Serodio
-- QOS.ch, main sponsor of cal10n, logback and slf4j open source projects, is looking to hire talented software developers. For further details, see http://logback.qos.ch/job.html _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
participants (4)
-
Ceki Gülcü -
Daniel Serodio (lists) -
David Roussel -
Ralph Goers