Description of problem: There are no syslog-ng packages built for EPEL6. Additional info: See also the fedora ticket for specfile cleanups: * Bug 651823 - please update to syslog-ng version 3.2 https://bugzilla.redhat.com/show_bug.cgi?id=651823
I have imported and build syslog-ng-3.1.4-2 for EPEL6 * http://koji.fedoraproject.org/koji/buildinfo?buildID=240607 Notes about this build: * build with eventlog-devel 0.2.7 (see build log) * no SSL support (no --enable-ssl configure option) * no SQL support (no --enable-sql configure option) Note: It should be feasible to update the Fedora 14 branch using this build files.
Todo list: * bump eventlog-devel BR version to 0.2.12 * try to enable SSL support using the openssl static library so that the syslog-ng binary doesn't depend on /usr/lib{,64} libraries (/usr may be a network mount point; and the network is started after the main syslog daemon) * check the SELinux rules; the following appear to be missing: - allow syslogd_t self:process setrlimit; - allow syslogd_t syslogd_var_lib_t:sock_file create;
Todo: Correct the changelog entry (s/4.x/3.x/): * dropped support for EPEL-4 and EPEL-5 (syslog-ng 4.x requires pcre >= 7.3)
The syslog-ng 3.1.4 have been pushed to the EPEL6 testing repositories. Just execute the following command to install activate it: * yum install --enablerepo=epel-testing syslog-ng * chkconfig rsyslog off * chkconfig syslog-ng on * chkconfig rsyslog stop; chkconfig syslog-ng start Note: there will be a couple of SElinux violations.
A couple of problems have been already detected: * Log entry: syslog-ng[3165]: Error opening control socket, bind() failed; socket='/var/lib/syslog-ng/syslog-ng.ctl', error='Permission denied (13)' * ps aux reports it as using a non-compliant pid file "syslog-ng -p /var/run/syslog-ng.pid" * it is also shipping a /etc/logrotate.d/syslog-ng file instead off /etc/logrotate.d/syslog Please, expect a new build shortly...
(In reply to comment #5) > * it is also shipping a /etc/logrotate.d/syslog-ng file > instead off /etc/logrotate.d/syslog This one is a false alarm. I forgot to delete a file created manually (see https://bugzilla.redhat.com/show_bug.cgi?id=651823#c16).
(In reply to comment #5) > * ps aux reports it as using a non-compliant pid file > > "syslog-ng -p "/var/run/syslog-ng.pid" The init script is also creating a symbolic link "syslogd.pid" pointing to "/var/run/syslog-ng.pid".
(In reply to comment #5) > A couple of problems have been already detected: > > * Log entry: > syslog-ng[3165]: Error opening control socket, bind() failed; > socket='/var/lib/syslog-ng/syslog-ng.ctl', error='Permission denied (13)' Blocked by the missing SELinux rule: * allow syslogd_t syslogd_var_lib_t:sock_file create;
Hi, Does anyone know why the syslog-ng init script has to maintain 2 pidfiles ( /var/run/syslog-ng.pid and the symbolic link /var/run/syslogd.pid ) ? /jpo
(In reply to comment #9) > Hi, > > Does anyone know why the syslog-ng init script has to maintain 2 pidfiles ( > /var/run/syslog-ng.pid and the symbolic link /var/run/syslogd.pid ) ? > > /jpo I did this so it was more obvious what syslog daemon was running in the case that you had multiple syslog daemons running on a box for some reason. I had the init script drop down it's "own" pid file and symlink in the one for the "main" syslog daemon if it wasn't already running. This allows logrotate to reload the correct syslogger and still allow running multiple syslog daemons (in theory).
(In reply to comment #5) > A couple of problems have been already detected: > > * Log entry: > syslog-ng[3165]: Error opening control socket, bind() failed; > socket='/var/lib/syslog-ng/syslog-ng.ctl', error='Permission denied (13)' > > * ps aux reports it as using a non-compliant pid file > > "syslog-ng -p /var/run/syslog-ng.pid" > > * it is also shipping a /etc/logrotate.d/syslog-ng file > instead off /etc/logrotate.d/syslog > > Please, expect a new build shortly... Or not. The EPEL 6 SELinux policies appear to be out of sync with the Fedora ones, at least regarding syslogd_t (the listed SELinux problems don't occur in F-14; same SRPM build and tested in F-14).
Syslog-ng 3.1 SELinux problems reported againt Fedora (fixed in F14): * Bug 618033 - Updated permissions for syslog-ng (Fedora/selinux-policy bugs) https://bugzilla.redhat.com/show_bug.cgi?id=618033 Syslog-ng 3.1 SELinux problems reported against RHEL6 selinux-policy: * Bug 700235 - syslog-ng 3.1.x SElinux violations (Red Hat Enterprise Linux 6/selinux-policy bugs) https://bugzilla.redhat.com/show_bug.cgi?id=700235
Does syslog-ng 3.1 really require pcre-devel >= 7.3? syslog-ng 3.2.x has a more conservative requirement. I ask because I was attempting to build 3.1 for EPEL5 as well given that the 2.1 series is no longer supported. I'm not sure if this was a change we even want to consider introducing (unless a security issue pops up), but it might be nice to at least have the option if we so choose (or even to introduce syslog-ng31 or syslog-ng32 to EPEL5).
(In reply to comment #13) > Does syslog-ng 3.1 really require pcre-devel >= 7.3? syslog-ng 3.2.x has a > more conservative requirement. It was only downgraded for syslog-ng 3.2.3 (see https://bugzilla.redhat.com/show_bug.cgi?id=651823#c26). > I ask because I was attempting to build 3.1 for EPEL5 as well given that the > 2.1 series is no longer supported. I'm not sure if this was a change we even > want to consider introducing (unless a security issue pops up), but it might be > nice to at least have the option if we so choose (or even to introduce > syslog-ng31 or syslog-ng32 to EPEL5). Feel free to help compiling and testing syslog-ng 3.2.3 for EPEL6 and EPEL5. Upstream appears to be planning a new release - 3.2.4 - this week. (see https://lists.balabit.hu/pipermail/syslog-ng/2011-May/016517.html) /jpo
3.2.3 SRPMS for EPEL 5 and 6: * http://um-pe09-2.di.uminho.pt./fedora/syslog-ng-3.2.3-0.el5.1.src.rpm * http://um-pe09-2.di.uminho.pt./fedora/syslog-ng-3.2.3-0.el6.src.rpm Diff between the EPEL5 and EPEL6 specfiles: * http://um-pe09-2.di.uminho.pt./fedora/syslog-ng-3.2.3-specfile-diff-epel5-epel6.patch
syslog-ng-3.1.4-3.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/syslog-ng-3.1.4-3.el6
The first SELinux problem * allow syslogd_t self:process setrlimit; has already been fixed in * [RHEL6] selinux-policy >= 3.7.19-80.el6 * [RHEL5] selinux-policy >= 2.4.6-301.el5 due to the tickets * [RHEL6] selinux blocks rsyslogd from opening more file descriptors https://bugzilla.redhat.com/show_bug.cgi?id=689431 * [RHEL5] selinux blocks rsyslogd from opening more file descriptors https://bugzilla.redhat.com/show_bug.cgi?id=674452 The problem is that both these selinux-policy packages have not been released yet. The second SELinux problem still hasn't been fixed in the RHEL SELinux policies.
Package syslog-ng-3.1.4-3.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing syslog-ng-3.1.4-3.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/syslog-ng-3.1.4-3.el6 then log in and leave karma (feedback).
RHEL6 ----- Both problems are fixed by the SELinux Policy version 3.7.19 release 93: * RPMS selinux-policy-3.7.19-93.el6 http://people.redhat.com/dwalsh/SELinux/RHEL6/noarch/ Note: this SELinux policy is for RHEL 6.1
syslog-ng 3.2.4 SRPMS for EPEL 5 and 6 for a future submission: * http://um-pe09-2.di.uminho.pt/fedora/syslog-ng-3.2.4-0.el5.1.src.rpm * http://um-pe09-2.di.uminho.pt/fedora/syslog-ng-3.2.4-0.el6.src.rpm Diff between the EPEL5 and EPEL6 specfiles/configuration files: * http://um-pe09-2.di.uminho.pt/fedora/syslog-ng-3.2.4-epel5-epel6.diff Note: They build and install. More testing won't hurt ...
(In reply to comment #20) > syslog-ng 3.2.4 SRPMS for EPEL 5 and 6 for a future submission: > > * http://um-pe09-2.di.uminho.pt/fedora/syslog-ng-3.2.4-0.el5.1.src.rpm > * http://um-pe09-2.di.uminho.pt/fedora/syslog-ng-3.2.4-0.el6.src.rpm > > Diff between the EPEL5 and EPEL6 specfiles/configuration files: > > * http://um-pe09-2.di.uminho.pt/fedora/syslog-ng-3.2.4-epel5-epel6.diff > > Note: They build and install. More testing won't hurt ... New SRPMS: * http://um-pe09-2.di.uminho.pt/fedora/syslog-ng-3.2.4-0.0.2.el5.1.src.rpm * http://um-pe09-2.di.uminho.pt/fedora/syslog-ng-3.2.4-0.0.2.el6.src.rpm Packaging differences: * http://um-pe09-2.di.uminho.pt/fedora/syslog-ng-3.2.4-0.0.2-epel5-epel6-differences.patch Note: the previous EPEL5 SRPM - syslog-ng-3.2.4-0.el5.1.src.rpm - was buggy (see https://bugzilla.redhat.com/show_bug.cgi?id=704690#c3)
Hi, Any chance of having a couple of minutes of your time to help testing and improve the karma levels of the following packages? Three karma points are need to change their status to stable. EPEL6 * https://admin.fedoraproject.org/updates/syslog-ng-3.1.4-3.el6 (eventlog-0.2.12-1.el6 is already available in stable) EPEL5 * https://admin.fedoraproject.org/updates/syslog-ng-2.1.4-9.el5 * https://admin.fedoraproject.org/updates/eventlog-0.2.12-1.el5 (eventlog-0.2.12-1.el5 has already reached 14 days in testing) tia, jpo
(In reply to comment #19) > RHEL6 > ----- > > Both problems are fixed by the SELinux Policy version 3.7.19 release 93: > > * RPMS selinux-policy-3.7.19-93.el6 > http://people.redhat.com/dwalsh/SELinux/RHEL6/noarch/ > > Note: this SELinux policy is for RHEL 6.1 * Red Hat Delivers Red Hat Enterprise Linux 6.1 http://www.redhat.com/about/news/prarchive/2011/Red-Hat-Delivers-Red-Hat-Enterprise-Linux-6-1 * selinux-policy ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/selinux-policy-3.7.19-93.el6.src.rpm :)
syslog-ng-3.1.4-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.