That actually sounds correct. I have locally built another version of json-c for application development purposes. This sounds like the issue.
On Wed, Sep 3, 2014 at 11:31 AM, Rainer Gerhards <[email protected]> wrote: > 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. > > Rainer > > > On Wed, Sep 3, 2014 at 5:25 PM, Michael Biebl <[email protected]> wrote: > >> Am 03.09.2014 17:18, schrieb Daniel Bruce: >> > Package: rsyslog >> > Version: 8.4.0-2 >> > Severity: important >> > >> > rsyslogd fails to start with the following error: >> > root@dbruce-desktop:~# /usr/sbin/rsyslogd -c3 -f /etc/rsyslog.alt.conf >> -i /var/run/rsyslog.alt.pid -4 >> > /usr/sbin/rsyslogd: symbol lookup error: /usr/sbin/rsyslogd: undefined >> symbol: json_tokener_errors >> >> Can you send me the output of >> ldd /usr/sbin/rsyslogd >> >> >> Thanks, >> Michael >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> >> >
