On Fri, 3 Nov 2017 12:02:06 +
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
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 ver
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 proble
After updating F26:
syslog does not start!
This fixed it for me:
dnf --enablerepo=updates-testing upgrade libfastjson.x86_64
- Mike
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproj
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.
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)
Ac
