Hi,

I've been using rsyslog v8.4.0 on Opensuse 13.1, with pkgs sourced from

        
https://build.opensuse.org/package/show?project=security%3Alogging%3Aelma&package=rsyslog

Currently, rsyslog service restart FAILs

        systemctl restart rsyslog
                Job for rsyslog.service failed. See "systemctl status 
rsyslog.service" and "journalctl -xn" for details.

Checking status,

        systemctl status rsyslog.service
                rsyslog.service - System Logging Service
                   Loaded: loaded (/etc/systemd/system/rsyslog.service; enabled)
                   Active: failed (Result: start-limit) since Sun 2014-09-21 
20:25:30 PDT; 7s ago
                  Process: 7280 ExecStart=/usr/sbin/rsyslogd -n (code=exited, 
status=127)
                 Main PID: 7280 (code=exited, status=127)

                Sep 21 20:25:30 test rsyslogd[7280]: /usr/sbin/rsyslogd: symbol 
lookup error: /usr/sbin/rsyslogd: undefined symbol: json_tokener_errors
                Sep 21 20:25:30 test systemd[1]: rsyslog.service: main process 
exited, code=exited, status=127/n/a
                Sep 21 20:25:30 test systemd[1]: Failed to start System Logging 
Service.
                Sep 21 20:25:30 test systemd[1]: Unit rsyslog.service entered 
failed state.
                Sep 21 20:25:30 test systemd[1]: Starting System Logging 
Service...
                Sep 21 20:25:30 test systemd[1]: rsyslog.service start request 
repeated too quickly, refusing to start.
                Sep 21 20:25:30 test systemd[1]: Failed to start System Logging 
Service.

blames

        symbol lookup error: /usr/sbin/rsyslogd: undefined symbol: 
json_tokener_errors

reading

        Bug#760390: rsyslogd fails to start
        
https://www.mail-archive.com/[email protected]/msg1253559.html

suggests

        >> FYI: json-c has broken it's API in recent versions. rsyslog does a
        >> configure check and uses the proper API, e.g. here:
        >> 
        >> https://github.com/rsyslog/rsyslog/blob/master/runtime/msg.c#L4077
        >>
        >> So this sounds to me like the version of json-c used for compilation 
does
        >> not match the version that's present on the system.

checking

        rpm -qa | egrep -i "rsyslog|json-c" | sort
                libjson-c2-0.12-43.1.x86_64
                rsyslog-8.4.0-213.1.x86_64
                rsyslog-diag-tools-8.4.0-213.1.x86_64
                rsyslog-doc-8.4.0-213.1.x86_64
                rsyslog-module-dbi-8.4.0-213.1.x86_64
                rsyslog-module-gssapi-8.4.0-213.1.x86_64
                rsyslog-module-gtls-8.4.0-213.1.x86_64
                rsyslog-module-mmnormalize-8.4.0-213.1.x86_64
                rsyslog-module-mysql-8.4.0-213.1.x86_64
                rsyslog-module-pgsql-8.4.0-213.1.x86_64
                rsyslog-module-relp-8.4.0-213.1.x86_64
                rsyslog-module-snmp-8.4.0-213.1.x86_64
                rsyslog-module-udpspoof-8.4.0-213.1.x86_64

Not clear WHAT version of libjson-c2 IS compatible with the 8.4.0-213 rsyslog 
packages

Coincidentally, the current pkg build @

        
https://build.opensuse.org/package/live_build_log/security:logging:elma/rsyslog/openSUSE_13.1/x86_64

is failing @ json-related errors

Not sure exactly where the problem lies -- in packaging, or upstream sources.

Grant
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to