[Bug 29] New: syslog-ng segfault when HUP signal arrives
https://bugzilla.balabit.com/show_bug.cgi?id=29 Summary: syslog-ng segfault when HUP signal arrives Product: syslog-ng Version: 2.0.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: sasa@debian.org Type of the Report: bug Estimated Hours: 0.0 If there are two udp driver in the config file syslog-ng will segfault when a HUP signal arrive. Example config: source s_network_1 { udp(); }; source s_network { udp(); }; I know that this is not a valid config, but the segfault is not the humble way to tell me. :) -- 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=29 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #1 from Balazs Scheidler <bazsi@balabit.hu> 2009-02-02 17:56:41 --- Trying with the latest 3.0 it reports this: Internal error, duplicate configuration elements refer to the same persistent config; name='afsocket_sd_connections(dgram,AF_INET(0.0.0.0:514))' Trying the same with latest 2.0, it also reports this: Internal error, duplicate configuration elements refer to the same persistent config; name='afsocket_sd_connections(dgram,AF_INET(0.0.0.0:2000))' I'm not saying it is the best possible indication of the configuration file conflict, rather it is a very bad way of doing it, however I can't seem to reproduce the segfault. But I'd appreciate some more information, like the exact version number, the configuration file, a backtrace. -- 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