Bug 1508588 - Latest rsyslog fails to start with undefined symbol: fjson_global_do_case_sensitive_comparison
Summary: Latest rsyslog fails to start with undefined symbol: fjson_global_do_case_sen...
Keywords:
Status: CLOSED DUPLICATE of bug 1508359
Alias: None
Product: Fedora
Classification: Fedora
Component: rsyslog
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Radovan Sroka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-01 18:08 UTC by Salvador Ortiz
Modified: 2017-11-01 21:49 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-11-01 21:49:14 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Salvador Ortiz 2017-11-01 18:08:56 UTC 
Description of problem:

After updating to latest rsyslog-8.30.0-3 it fails to start.

Version-Release number of selected component (if applicable):

8.30.0-3

How reproducible:

Always at system startup

Steps to Reproduce:
1. Run
# systemctl start rsyslog.service

Actual results:

Job for rsyslog.service failed because the control process exited with error code.

Expected results:

The daemon should start

Additional info:

Manually starting it as "rsyslogd -n -d" results in
rsyslogd: symbol lookup error: rsyslogd: undefined symbol: fjson_global_do_case_sensitive_comparison

Googling the case I found: https://github.com/rsyslog/rsyslog/issues/1853

I have installed libfastjson-0.99.6-1.fc26.x86_64
Comment 1 Peter Bieringer 2017-11-01 20:41:15 UTC 
Looks like a dependeny was not released fast enough:

Try:

# yum update --enablerepo updates-testing libfastjson

this installs: libfastjson-0.99.7-1.fc26

and now rsyslogd will start again
Comment 2 Frank Ch. Eigler 2017-11-01 21:49:14 UTC 

*** This bug has been marked as a duplicate of bug 1508359 ***
Note You need to log in before you can comment on or make changes to this bug.