When your /etc/syslog-ng/syslog-ng.conf is broken, /etc/init.d/syslog-ng restart causes firewall to stop, then says that cannot start syslog, and finally, do not start firewall again. Reproducible: Always Steps to Reproduce: 1. broke your /etc/syslog-ng/syslog-ng.conf 2. # /etc/init.d/syslog-ng restart Actual Results: # /etc/init.d/syslog-ng restart * Stopping firewall ... [ ok ] * Stopping syslog- ng ... [ ok ] syntax error at 1 Parse error reading configuration file, exiting. (line 1) * Configuration error. Please fix your configfile (/etc/syslog-ng/syslog- ng.conf) [ !! ] (now, i've fixed syslog-ng.conf and) # /etc/init.d/syslog-ng restart [ ok ] * Starting syslog- ng ... [ ok ] Where is my firewall? Expected Results: If syslog-ng init script is smart enough to clear firewall before restarting syslogd (wtf? what is the reason of this?) it should be also able to set rules again, no matter if restarting syslog itself was successful, or not.
fix your firewall script. It shouldn't "need logger". Not a problem with syslog-ng.
I use default /etc/init.d/iptables from distro, so You should consider it as a buggy one and fix it (I've done it for myself earlier, thanks for your suggestions.)
No. It's not a bug in syslog-ng.
Going to reopen and assign properly...
Oops, it
Oops, it´s already fixed in Bug 92406. Sorry for bugspam.
*** Bug 92406 has been marked as a duplicate of this bug. ***
