1508359 – rsyslog fails to start about:reader?url=https://bugzilla.redhat.com/show_bug.cgi?

id=1508359

bugzilla.redhat.com

1508359 – rsyslog fails to start

10-13 minutes

Description Panos Kavalagios 2017-11-01 09:56:52 UTC

Description of problem:
rsyslog fails to start.

Version-Release number of selected component (if

applicable):
rsyslog-8.30.0-3.fc26.x86_64

How reproducible:
Start rsyslog

Steps to Reproduce:
1. systemctl enable rsyslog
2. systemctl start rsyslog
3.

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

Expected results:
The daemon should have started.

Additional info:
# systemctl status rsyslog
● rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system
/rsyslog.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed
2017-11-01 11:56:05 EET; 23s ago
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Process: 3797 ExecStart=/usr/sbin/rsyslogd -n
$SYSLOGD_OPTIONS (code=exited, status=127)
Main PID: 3797 (code=exited, status=127)
CPU: 982us

Νοέ 01 11:56:05 bb229 systemd[1]: rsyslog.service:

Unit entered failed state.
Νοέ 01 11:56:05 bb229 systemd[1]: rsyslog.service:
Failed with result 'exit-code'.
Νοέ 01 11:56:05 bb229 systemd[1]: rsyslog.service:
Service hold-off time over, scheduling restart.
Νοέ 01 11:56:05 bb229 systemd[1]: Stopped System

1 of 6 3/11/2021, 3:07 PM
1508359 – rsyslog fails to start about:reader?url=https://bugzilla.redhat.com/show_bug.cgi?id=1508359

Logging Service.
Νοέ 01 11:56:05 bb229 systemd[1]: rsyslog.service:
Start request repeated too quickly.
Νοέ 01 11:56:05 bb229 systemd[1]: Failed to start
System Logging Service.
Νοέ 01 11:56:05 bb229 systemd[1]: rsyslog.service:
Unit entered failed state.
Νοέ 01 11:56:05 bb229 systemd[1]: rsyslog.service:
Failed with result 'exit-code'.

Comment 1 Radovan Sroka 2017-11-01 11:00:23 UTC

What version of libfastjson do you have? (rpm -qa

libfastjson)
Try to install latest library from testing. (dnf
install libfastjson --enablerepo=updates-testing)

Comment 2 Mace Moneta 2017-11-01 11:23:13 UTC

Updating libfastjson from updates-testing allows

rsyslog to start. Missing requisite for the
rsyslog package?

Comment 3 Panos Kavalagios 2017-11-01 11:24:10 UTC

I can verify that the update from testing repo

resolves the issue:

# rpm -qa libfastjson

libfastjson-0.99.6-1.fc26.x86_64

# dnf update libfastjson --enablerepo=updates-

testing
Fedora 26 - x86_64 - Test Updates
30 kB/s | 4.9 MB 02:47
Failed to synchronize cache for repo 'pharmefem',
disabling.
Last metadata expiration check: 0:02:17 ago on Τετ
01 Νοέ 2017 01:13:43 μμ EET.
Dependencies resolved.
================================================================================
Package Arch Version
Repository Size
================================================================================
Upgrading:
libfastjson x86_64 0.99.7-1.fc26
updates-testing 34 k

Transaction Summary
================================================================================
Upgrade 1 Package

Total download size: 34 k

Is this ok [y/N]: y
Downloading Packages:
[MIRROR] libfastjson-0.99.7-1.fc26.x86_64.rpm:

2 of 6 3/11/2021, 3:07 PM
1508359 – rsyslog fails to start about:reader?url=https://bugzilla.redhat.com/show_bug.cgi?id=1508359

Downloading successful, but checksum doesn't

match. Calculated:
1193739ef9928919d9c851f04ba82bcffa5edeef74a38eb408da64688aba18db(sha256)
Expected:
fdc64b0fc13cfcb3907805b90910d9a6e5c4cd68951317af8c9ce9d9c3f969bc(sha256)
libfastjson-0.99.7-1145%
[=============================] 2.0 MB/s | 49 kB
-libfastjson-0.99.7-1.fc26.x86_64.rpm
85 kB/s | 34 kB 00:00
--------------------------------------------------------------------------------
Total
16 kB/s | 34 kB 00:02
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing :
1/1
Upgrading : libfastjson-
0.99.7-1.fc26.x86_64 1/2
Running scriptlet: libfastjson-
0.99.7-1.fc26.x86_64 1/2
Cleanup : libfastjson-
0.99.6-1.fc26.x86_64 2/2
Running scriptlet: libfastjson-
0.99.6-1.fc26.x86_64 2/2
Verifying : libfastjson-
0.99.7-1.fc26.x86_64 1/2
Verifying : libfastjson-
0.99.6-1.fc26.x86_64 2/2

Upgraded:
libfastjson.x86_64 0.99.7-1.fc26

Complete!

# systemctl restart rsyslog

# systemctl status rsyslog

● rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system
/rsyslog.service; enabled; vendor pres
Active: active (running) since Wed 2017-11-01
13:21:41 EET; 4s ago
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Main PID: 11258 (rsyslogd)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/rsyslog.service
└─11258 /usr/sbin/rsyslogd -n

Νοέ 01 13:21:41 bb229 systemd[1]: Starting System

Logging Service...
Νοέ 01 13:21:41 bb229 rsyslogd[11258]: [origin

3 of 6 3/11/2021, 3:07 PM
1508359 – rsyslog fails to start about:reader?url=https://bugzilla.redhat.com/show_bug.cgi?id=1508359

software="rsyslogd" swVersion="8
Νοέ 01 13:21:41 bb229 systemd[1]: Started System
Logging Service.

WIN! Thank you!

Comment 4 Radovan Sroka 2017-11-01 12:12:12 UTC

This library should arrive to stable in few hours

I hope.

Comment 5 Radovan Sroka 2017-11-01 12:28:11 UTC

(In reply to Mace Moneta from comment #2)

> Updating libfastjson from updates-testing allows
rsyslog to start. Missing
> requisite for the rsyslog package?

No that is not necessary.

This requirement is enforced on library versioning
level. So when condition doesn't meet .so library
can't be linked.

The problem is that update of rsyslog and

libfastjson wasn't grouped. Wasn't atomic. So I
pushed libfastjson to stable today. Problem
resolves right after library becomes available. It
can take few hours.

Comment 6 Radovan Sroka 2017-11-01 12:38:39 UTC

*** Bug 1508439 has been marked as a duplicate of

this bug. ***

Comment 7 Andrew Haveland-Robinson 2017-11-01 14:25:37 UTC

Thanks Radovan,

dnf update libfastjson --enablerepo=updates-

testing

did indeed fix the problem. Logging is being

replicated to my syslog server using my old
rsyslog.conf

(I tried to use rsyslog.conf.rpmnew, but got no

output and no forwarding, so this is something
else I'll have to look into, but the old conf at
least works).

After spending some time upgrading and downgrading

rsyslog from about 10 servers, it would have been
good if this could have been caught earlier before
publishing to the stable repo!

Comment 8 Radovan Sroka 2017-11-01 14:47:41 UTC

4 of 6 3/11/2021, 3:07 PM
1508359 – rsyslog fails to start about:reader?url=https://bugzilla.redhat.com/show_bug.cgi?id=1508359

*** Bug 1508487 has been marked as a duplicate of

this bug. ***

Comment 9 Radovan Sroka 2017-11-01 16:02:17 UTC

*** Bug 1508534 has been marked as a duplicate of

this bug. ***

Thanks, libfastjson indeed fixes the problem.

Comment 11 Frank Ch. Eigler 2017-11-01 21:49:14 UTC

*** Bug 1508588 has been marked as a duplicate of

this bug. ***

Comment 12 Frank Ch. Eigler 2017-11-01 21:49:19 UTC

*** Bug 1508646 has been marked as a duplicate of

this bug. ***

Comment 13 Radovan Sroka 2017-11-02 07:56:21 UTC

I can verify that libfastjson is now in stable

repository.

~ » sudo dnf install libfastjson

Repository beaker-client is listed more than once
in the configuration
Repository beaker-client-testing is listed more
than once in the configuration
Last metadata expiration check: 0:20:02 ago on Thu
02 Nov 2017 08:33:35 AM CET.
Dependencies resolved.
========================================================================================
Package Arch
Version Repository
Size
========================================================================================
Installing:
libfastjson x86_64
0.99.7-1.fc26 updates
34 k

Transaction Summary
========================================================================================
Install 1 Package

Total download size: 34 k

Installed size: 64 k
Is this ok [y/N]:

Comment 14 Radovan Sroka 2017-11-02 08:30:43 UTC

*** Bug 1508771 has been marked as a duplicate of

this bug. ***

5 of 6 3/11/2021, 3:07 PM
1508359 – rsyslog fails to start about:reader?url=https://bugzilla.redhat.com/show_bug.cgi?id=1508359

Comment 15 Jiří Vymazal 2017-11-02 11:54:54 UTC

*** Bug 1508850 has been marked as a duplicate of

this bug. ***

6 of 6 3/11/2021, 3:07 PM