Each night, in /var/log/syslog, I get : syslog-ng[13287]: Error opening plugin module; module='snmpdest', error='libsyslog-ng-3.22.so.0: cannot open shared object file: No such file or directory' But libsyslog-ng-3.22.so.0 doesn't exist on my system. emerge @preserved-rebuild gives nothing.
Looks like 3.26.1 linked against the older, installed libsyslog-ng during the build. Might be (tangentially) related to bug #686416.
Which version of syslog-ng do you have installed? 3.22 or 3.26? In either case, please try to recompile syslog-ng: emerge -v1 app-admin/syslog-ng Does it help?
I recompiled app-admin/syslog-ng-3.26.1-r1 And I haven't the error in the nightly logs anymore. But, I don't understand why logwatch continues to indicate : --------------------- Syslog-ng Begin ------------------------ Syslog-ng started: 1 Time(s) Syslog-ng stopped: 1 Time(s) Syslog-ng reloaded: 1 Time(s) **** Unmatched entries **** Configuration reload finished; : 1 Time(s) Error opening plugin module; module='snmpdest', error='libsyslog-ng-3.22.so.0: cannot open shared object file: No such file or directory' : 1 Time(s) ---------------------- Syslog-ng End ------------------------- (stop and start were after recompile)
(In reply to Christophe PEREZ from comment #3) > But, I don't understand why logwatch continues to indicate : Not anymore. Solved for me even if I think that portage should ask me to recompile syslog-ng after updates.
