James Lay <jlay@slave-tothe-box.net> writes:
/usr/sbin/syslog-ng -t -d -v -F -f /usr/etc/syslog-ng.conf
open("/usr/lib/libsyslog-ng-3.3.11.so", O_RDONLY) = 10
This is the problematic bit. It is opening libsyslog-ng-3.3.11.so, while the running syslog-ng is 3.5.4.1, with modules linked against libsyslog-ng-3.5.4.1.so. The two shared objects conflict, and that causes an abort. Do you have an /usr/lib/libsyslog-ng.so? Is that a symlink to libsyslog-ng-3.3.11.so? If so, delete it, or make it point to -3.5.4.1.so instead. If you don't, then deleting libsyslog-ng-3.3.11.so, and recompiling 3.5 should make the problem go away too. One way around this problem, to avoid it in the future, is to use --libdir=/usr/lib/syslog-ng/3.5 for configure, so all shared objects are put into a private, version-specific directory. Or, you can remove the older version of syslog-ng from the system, before upgrading. (The whys and hows of this bug is a long, and sad story, longer than I can explain before falling asleep. Sorry!) -- |8]