[Bug 272] New: When syslog-ng server is not available, all syslog-ng clients are frozen
https://bugzilla.balabit.com/show_bug.cgi?id=272 Summary: When syslog-ng server is not available, all syslog-ng clients are frozen Product: syslog-ng Version: 3.4.x Platform: PC OS/Version: Linux Status: NEW Severity: critical Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: carl.chenet-ext@cloudwatt.com Type of the Report: bug Estimated Hours: 0.0 Os: Ubuntu Precise Syslog-ng version: 3.4.7-1~mhp1.sysvinit Hi, When the syslog-ng server is not available, all syslog-ng clients are frozen. We have to restart syslog-ng by mco because no other access work (ssh, direct console...). I'm including your syslog-ng configuration files. Feel free to ask me whenever information you need. Regards, Carl Chenet -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=272 --- Comment #1 from Carl Chenet <carl.chenet-ext@cloudwatt.com> 2014-03-04 12:03:33 --- Created an attachment (id=92) --> (https://bugzilla.balabit.com/attachment.cgi?id=92) syslog-ng configuration files This is a tar.gz archive with the complete syslog-ng configuration files. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=272 --- Comment #2 from Balazs Scheidler <bazsi@balabit.hu> 2014-03-07 19:23:48 --- Hmm. This is more than a surprise. Something strange must happen in your env. I'm unable to check the tarball now, as I'm reading this on a phone. What does it mean the server is down? Is it not running or running and stuck? Do you use flow control? Are all syslog-ng instances the same version? -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
bugzilla＠bugzilla.balabit.com