After upgrading syslog-ng, I started seeing the following errors from a third-party application: - unix dgram connect: Connection refused at /usr/lib/perl5/vendor_perl/5.16.3/Net/Server/Log/Sys/Syslog.pm line 70. no connection to syslog available ... repeated frequently. I assumed that syslog-ng had crashed, so attempted to restart it: $ sudo /etc/init.d/syslog-ng restart Password: * WARNING: you are stopping a boot service * Stopping syslog-ng ... * start-stop-daemon: no matching processes found [ ok ] * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ... Error opening plugin module; module='afsmtp', error='libsyslog-ng-3.4.7.so: cannot open shared object file: No such file or directory' [ ok ] * Starting syslog-ng ... Error opening plugin module; module='afsmtp', error='libsyslog-ng-3.4.7.so: cannot open shared object file: No such file or directory' [ ok ] $ epm -ql syslog-ng | sudo xargs grep libsyslog-ng-3.4.7 Binary file /usr/lib/syslog-ng/libafsmtp.so matches $ sudo ldd /usr/lib/syslog-ng/libafsmtp.so linux-gate.so.1 (0xa7717000) libesmtp.so.6 => /usr/lib/libesmtp.so.6 (0xa76e6000) libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0 (0xa7689000) libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0xa74f8000) libdl.so.2 => /lib/libdl.so.2 (0xa74f3000) libsyslog-ng-crypto.so => /usr/lib/syslog-ng/libsyslog-ng-crypto.so (0xa74eb000) libsyslog-ng-3.4.7.so => not found libpthread.so.0 => /lib/libpthread.so.0 (0xa74d0000) libc.so.6 => /lib/libc.so.6 (0xa7329000) libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0xa7277000) libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0xa7247000) libz.so.1 => /lib/libz.so.1 (0xa7233000) /lib/ld-linux.so.2 (0xa7718000) libsyslog-ng-3.4.8.so => /usr/lib/libsyslog-ng-3.4.8.so (0xa71b8000) libuuid.so.1 => /lib/libuuid.so.1 (0xa71b3000) libcom_err.so.2 => /lib/libcom_err.so.2 (0xa71ae000) libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0xa71a1000) libkeyutils.so.1 => /lib/libkeyutils.so.1 (0xa719c000) libresolv.so.2 => /lib/libresolv.so.2 (0xa7185000) librt.so.1 => /lib/librt.so.1 (0xa717c000) libnsl.so.1 => /lib/libnsl.so.1 (0xa7163000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xa715d000) libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xa715a000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xa7045000) libevtlog.so.0 => /usr/lib/libevtlog.so.0 (0xa7040000) libcap.so.2 => /lib/libcap.so.2 (0xa703a000) libpcre.so.1 => /lib/libpcre.so.1 (0xa6fdc000) libattr.so.1 => /lib/libattr.so.1 (0xa6fd6000) ... so somehow libafsmtp.so is linked against *both* libsyslog-ng-3.4.8.so and libsyslog-ng-3.4.7.so - which is no longer present. (Please note that, contrary to the output on restarting syslog-ng, 'afsmtp' does not appear in any file below /etc/syslog-ng/)
please paste the outputs of scanelf -n /usr/lib/syslog-ng/libafsmtp.so and emerge --info.
Rebuilding syslog-ng-3.4.8 with only syslog-ng-3.4.8 on the system does result in a correctly-linked library: $ sudo ldd /usr/lib/syslog-ng/libafsmtp.so linux-gate.so.1 (0xa7726000) libesmtp.so.6 => /usr/lib/libesmtp.so.6 (0xa76f5000) libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0 (0xa7698000) libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0xa7507000) libdl.so.2 => /lib/libdl.so.2 (0xa7502000) libsyslog-ng-crypto.so => /usr/lib/syslog-ng/libsyslog-ng-crypto.so (0xa74fa000) libsyslog-ng-3.4.8.so => /usr/lib/libsyslog-ng-3.4.8.so (0xa747f000) libpthread.so.0 => /lib/libpthread.so.0 (0xa7464000) libc.so.6 => /lib/libc.so.6 (0xa72bd000) libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0xa720b000) libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0xa71db000) libz.so.1 => /lib/libz.so.1 (0xa71c7000) /lib/ld-linux.so.2 (0xa7727000) libuuid.so.1 => /lib/libuuid.so.1 (0xa71c2000) librt.so.1 => /lib/librt.so.1 (0xa71b9000) libnsl.so.1 => /lib/libnsl.so.1 (0xa71a0000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xa719a000) libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xa7197000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xa7082000) libevtlog.so.0 => /usr/lib/libevtlog.so.0 (0xa707d000) libcap.so.2 => /lib/libcap.so.2 (0xa7077000) libpcre.so.1 => /lib/libpcre.so.1 (0xa7019000) libcom_err.so.2 => /lib/libcom_err.so.2 (0xa7014000) libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0xa7008000) libkeyutils.so.1 => /lib/libkeyutils.so.1 (0xa7003000) libresolv.so.2 => /lib/libresolv.so.2 (0xa6fec000) libattr.so.1 => /lib/libattr.so.1 (0xa6fe6000) $ sudo emerge --info syslog-ng Portage 2.2.8-r1 (default/linux/x86/13.0, gcc-4.7.3, glibc-2.17, 3.12.18-gentoo i686) ================================================================= System Settings ================================================================= System uname: Linux-3.12.18-gentoo-i686-Intel-R-_Pentium-R-_4_CPU_2.80GHz-with-gentoo-2.2 KiB Mem: 1033540 total, 124436 free KiB Swap: 6201396 total, 5834048 free Timestamp of tree: Tue, 05 Aug 2014 05:30:01 +0000 ld GNU ld (GNU Binutils) 2.23.2 app-shells/bash: 4.2_p45 dev-java/java-config: 2.2.0 dev-lang/python: 2.7.7, 3.3.5-r1 dev-util/cmake: 2.8.12.2-r1 dev-util/pkgconfig: 0.28-r1 sys-apps/baselayout: 2.2 sys-apps/openrc: 0.12.4 sys-apps/sandbox: 2.6-r1 sys-devel/autoconf: 2.69 sys-devel/automake: 1.11.6, 1.12.6, 1.13.4 sys-devel/binutils: 2.23.2 sys-devel/gcc: 4.7.3-r1 sys-devel/gcc-config: 1.7.3 sys-devel/libtool: 2.4.2-r1 sys-devel/make: 3.82-r4 sys-kernel/linux-headers: 3.13 (virtual/os-headers) sys-libs/glibc: 2.17 app-admin/syslog-ng-3.4.8 was built with the following: USE="caps dbi geoip ipv6 pcre smtp spoof-source ssl tcpd -amqp -json -mongodb -pacct -systemd"
(In reply to Alex Xu (Hello71) from comment #1) > please paste the outputs of scanelf -n /usr/lib/syslog-ng/libafsmtp.so and > emerge --info. Sorry, rebuilt before I saw your comment - although this resolves the issue for me. Abbreviated 'emerge --info' provided in that comment - if you need everything please let me know and I'll add it in as an attachment. I'll see whether I have another system with the same issue to run scanelf on...
fixed in syslog-ng-3.6.1
