Description of problem: When using syslog-ng from EPEL under CentOS5.5, setroubleshootd complains about a missing syslog channel on startup Version-Release number of selected component (if applicable): syslog-ng-2.1.4-1.el5 chkconfig-1.3.30.2-2.el5 How reproducible: With setroubleshootd and syslog-ng installed under CentOS 5.5, we find that the boot sequence for setroubleshootd complains about a missing syslog channel. This may be reproduced post-boot by starting up setroubleshootd with the host's syslog server stopped, ( where that can be either syslogd or syslog-ng ). By default, chkconfig/RHEL puts syslog-ng/EPEL in startup position 26 instead of 18, which is AFTER setroubleshootd. By removing some of the LSB init block in the syslog-ng init script, it is possible to "kludge" it to run at start point 18 so that setroubleshoot stops complaining. In the example invocations of chkconfig below, /etc/init.d/syslog-ng.epel5 contains the original init script, whereas /etc/init.d/syslog-ng.repaired just has the LSB Required-Start/Required-Stop clauses removed. The implication is that the syslog-ng init script works perfectly happily under Fedora, but the same init script under RHEL5/CentOS5.5 sometimes confuses RHEL5's chkconfig. [whatever@standard-build-centos-5-5 ~]$ sudo chkconfig --level 0123456 syslog-ng.epel5 off [whatever@standard-build-centos-5-5 ~]$ sudo chkconfig --level 345 syslog-ng.epel5 on [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ ls -l /etc/rc?.d/???syslog-ng.epel5 lrwxrwxrwx 1 root root 25 Aug 2 10:25 /etc/rc0.d/K74syslog-ng.epel5 -> ../init.d/syslog-ng.epel5* lrwxrwxrwx 1 root root 25 Aug 2 10:25 /etc/rc1.d/K74syslog-ng.epel5 -> ../init.d/syslog-ng.epel5* lrwxrwxrwx 1 root root 25 Aug 2 10:25 /etc/rc2.d/K74syslog-ng.epel5 -> ../init.d/syslog-ng.epel5* lrwxrwxrwx 1 root root 25 Aug 2 10:25 /etc/rc3.d/S26syslog-ng.epel5 -> ../init.d/syslog-ng.epel5* lrwxrwxrwx 1 root root 25 Aug 2 10:25 /etc/rc4.d/S26syslog-ng.epel5 -> ../init.d/syslog-ng.epel5* lrwxrwxrwx 1 root root 25 Aug 2 10:25 /etc/rc5.d/S26syslog-ng.epel5 -> ../init.d/syslog-ng.epel5* lrwxrwxrwx 1 root root 25 Aug 2 10:25 /etc/rc6.d/K74syslog-ng.epel5 -> ../init.d/syslog-ng.epel5* [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ grep chkconfig /etc/init.d/syslog-ng.epel5 # chkconfig: - 12 88 [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ sudo chkconfig --level 0123456 syslog-ng.repaired off [whatever@standard-build-centos-5-5 ~]$ sudo chkconfig --level 345 syslog-ng.repaired on [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ ls -l /etc/rc?.d/???syslog-ng.repaired lrwxrwxrwx 1 root root 28 Aug 2 10:26 /etc/rc0.d/K88syslog-ng.repaired -> ../init.d/syslog-ng.repaired* lrwxrwxrwx 1 root root 28 Aug 2 10:26 /etc/rc1.d/K88syslog-ng.repaired -> ../init.d/syslog-ng.repaired* lrwxrwxrwx 1 root root 28 Aug 2 10:26 /etc/rc2.d/K88syslog-ng.repaired -> ../init.d/syslog-ng.repaired* lrwxrwxrwx 1 root root 28 Aug 2 10:26 /etc/rc3.d/S12syslog-ng.repaired -> ../init.d/syslog-ng.repaired* lrwxrwxrwx 1 root root 28 Aug 2 10:26 /etc/rc4.d/S12syslog-ng.repaired -> ../init.d/syslog-ng.repaired* lrwxrwxrwx 1 root root 28 Aug 2 10:26 /etc/rc5.d/S12syslog-ng.repaired -> ../init.d/syslog-ng.repaired* lrwxrwxrwx 1 root root 28 Aug 2 10:26 /etc/rc6.d/K88syslog-ng.repaired -> ../init.d/syslog-ng.repaired* [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ sudo chkconfig --del syslog-ng.repaired [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ grep chkconfig /etc/init.d/syslog-ng.repaired # chkconfig: - 12 88 [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ diff -u /etc/init.d/syslog-ng.epel5 /etc/init.d/syslog-ng.repaired --- /etc/init.d/syslog-ng.epel5 2009-03-24 17:08:49.000000000 +0000 +++ /etc/init.d/syslog-ng.repaired 2010-07-22 15:27:30.000000000 +0100 @@ -9,8 +9,6 @@ ### BEGIN INIT INFO # Provides: $syslog -# Required-Start: $local_fs -# Required-Stop: $local_fs # Short-Description: Next-generation syslog server # Description: syslog-ng, as the name shows, is a syslogd replacement, but # with new functionality for the new generation. The original syslogd [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ egrep "Provides|Required" /etc/init.d/* /etc/init.d/lvm2-monitor:# Provides: /etc/init.d/netfs:# Provides: $local_fs $remote_fs /etc/init.d/network:# Provides: $network /etc/init.d/syslog:# Provides: $syslog /etc/init.d/syslog-ng:# Provides: $syslog /etc/init.d/syslog-ng.epel5:# Provides: $syslog /etc/init.d/syslog-ng.epel5:# Required-Start: $local_fs /etc/init.d/syslog-ng.epel5:# Required-Stop: $local_fs /etc/init.d/syslog-ng.repaired:# Provides: $syslog /etc/init.d/vmware-tools:# Provides: VMware_Tools /etc/init.d/vmware-tools:# Required-Start: /etc/init.d/vmware-tools:# Required-Stop: $network [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ chkconfig --list netfs netfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off [whatever@standard-build-centos-5-5 ~]$ [whatever@standard-build-centos-5-5 ~]$ ls -l /etc/rc3.d/S* lrwxrwxrwx 1 root root 22 Jul 22 13:39 /etc/rc3.d/S02lvm2-monitor -> ../init.d/lvm2-monitor* lrwxrwxrwx 1 root root 17 May 23 2009 /etc/rc3.d/S03sysstat -> ../init.d/sysstat* lrwxrwxrwx 1 root root 15 May 8 2009 /etc/rc3.d/S05kudzu -> ../init.d/kudzu* lrwxrwxrwx 1 root root 18 May 8 2009 /etc/rc3.d/S08iptables -> ../init.d/iptables* lrwxrwxrwx 1 root root 17 Nov 6 2009 /etc/rc3.d/S10network -> ../init.d/network* lrwxrwxrwx 1 root root 16 May 8 2009 /etc/rc3.d/S11auditd -> ../init.d/auditd* lrwxrwxrwx 1 root root 21 May 8 2009 /etc/rc3.d/S12restorecond -> ../init.d/restorecond* lrwxrwxrwx 1 root root 19 Jul 22 15:44 /etc/rc3.d/S12syslog-ng -> ../init.d/syslog-ng* lrwxrwxrwx 1 root root 18 May 8 2009 /etc/rc3.d/S13mcstrans -> ../init.d/mcstrans* lrwxrwxrwx 1 root root 22 Jul 22 14:55 /etc/rc3.d/S19vmware-tools -> ../init.d/vmware-tools* lrwxrwxrwx 1 root root 20 Jul 22 13:40 /etc/rc3.d/S22messagebus -> ../init.d/messagebus* lrwxrwxrwx 1 root root 24 Nov 6 2009 /etc/rc3.d/S23setroubleshoot -> ../init.d/setroubleshoot* lrwxrwxrwx 1 root root 20 May 8 2009 /etc/rc3.d/S26lm_sensors -> ../init.d/lm_sensors* lrwxrwxrwx 1 root root 14 May 8 2009 /etc/rc3.d/S55sshd -> ../init.d/sshd* lrwxrwxrwx 1 root root 20 Nov 6 2009 /etc/rc3.d/S56rawdevices -> ../init.d/rawdevices* lrwxrwxrwx 1 root root 14 May 8 2009 /etc/rc3.d/S58ntpd -> ../init.d/ntpd* lrwxrwxrwx 1 root root 18 Jul 21 13:42 /etc/rc3.d/S80sendmail -> ../init.d/sendmail* lrwxrwxrwx 1 root root 15 May 8 2009 /etc/rc3.d/S90crond -> ../init.d/crond* lrwxrwxrwx 1 root root 17 May 8 2009 /etc/rc3.d/S95anacron -> ../init.d/anacron* lrwxrwxrwx 1 root root 19 May 8 2009 /etc/rc3.d/S98haldaemon -> ../init.d/haldaemon* lrwxrwxrwx 1 root root 11 Nov 6 2009 /etc/rc3.d/S99local -> ../rc.local* [whatever@standard-build-centos-5-5 ~]$
Fedora EPEL 5 changed to end-of-life (EOL) status on 2017-03-31. Fedora EPEL 5 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora or Fedora EPEL, please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.