F26 rsyslog does not start after update

[Cristian Sava]

Hi all,

After updating F26:
 rsyslog  
 systemd  
 systemd-libs 
 systemd-pam 
 systemd-udev

syslog does not start!

[root@*** ~]# systemctl status syslog
● rsyslog.service - System Logging Service
   Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled;
vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2017-11-03 11:26:08
EET; 2min 1s ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
 Main PID: 26414 (code=exited, status=127)

Nov 03 11:26:08 ***.ucv.ro systemd[1]: rsyslog.service: Failed with
result 'exit-code'.
Nov 03 11:26:08 ***.ucv.ro systemd[1]: rsyslog.service: Service hold-
off time over, scheduling r
Nov 03 11:26:08 ***.ucv.ro systemd[1]: Stopped System Logging Service.
Nov 03 11:26:08 ***.ucv.ro systemd[1]: rsyslog.service: Start request
repeated too quickly.
Nov 03 11:26:08 ***.ucv.ro systemd[1]: Failed to start System Logging
Service.
Nov 03 11:26:08 ***.ucv.ro systemd[1]: rsyslog.service: Unit entered
failed state.
Nov 03 11:26:08 ***.ucv.ro systemd[1]: rsyslog.service: Failed with
result 'exit-code'.

C.S.

[Cristian Sava]

On Fri, 2017-11-03 at 13:43 +0200, Cristian Sava wrote:
> Hi all,
>
> After updating F26:
>  rsyslog  
>  systemd  
>  systemd-libs 
>  systemd-pam 
>  systemd-udev
>
> syslog does not start!

Upgrading to F27 solve this but we saw that on many boxes so it's not
random.

C.S.

[Dr. Michael J. Chudobiak]

> After updating F26:
>
> syslog does not start!

This fixed it for me:

dnf --enablerepo=updates-testing upgrade libfastjson.x86_64

- Mike

[Cristian Sava]

On Fri, 2017-11-03 at 07:55 -0400, Dr. Michael J. Chudobiak wrote:
> > After updating F26:
> >
> > syslog does not start!
>
> This fixed it for me:
>
> dnf --enablerepo=updates-testing upgrade libfastjson.x86_64
> Mike

Thanks Mike, good to know,
but for now I think it's a security problem

C.S.

[Andy Blanchard]

On 3 November 2017 at 11:43, Cristian Sava  wrote:
> Hi all,
>
> After updating F26:
>  rsyslog
>  systemd
>  systemd-libs
>  systemd-pam
>  systemd-udev
>
> syslog does not start!

I spotted this problem too.  Apparently the latest version of rsyslog
(v8.30.0-3.fc26) is dependant on the latest version of libfastjson
(v0.99.7-1.fc26) which wasn't initially pushed at the same time as the
rsyslog update.  This was corrected later on in the day, so you can
either re-run an update and ensure you have the correct version of
libfastjson included, or manually pull the update from the build
archive (I got it from Koji just before it was pushed to updates) and
install it.  Once you have the correct version of libfastjson
installed you should be able to manually restart rsyslog without
issue.

Andy

[Tom Horsley]

On Fri, 3 Nov 2017 12:02:06 +0000
Andy Blanchard wrote:
> Apparently the latest version of rsyslog
> (v8.30.0-3.fc26) is dependant on the latest version of libfastjson
> (v0.99.7-1.fc26) which wasn't initially pushed at the same time as the
> rsyslog update.  This was corrected later on in the day

I just updated this morning (about an hour before sending this
mail) and those are the versions I have and syslog is running fine,
so the repos (at least the one I saw) do indeed seem to be
up to date now.