Thanks for the reply, Fabian. I have now resolved the problem. It was an incorrect file entry in rsyslog.d where I was trying to suppress messages; I though I had deleted it but found it was still there.

Thanks for the suggestion.

Philip.

On 5 Jan 2018, at 18:14, Fabian Arrotin arrfab@centos.org wrote:

...

On 05/01/18 18:50, Philip Taylor wrote: Is anyone else having problems with logging? rsyslog fails for me as follows :

[root@centos-rpi3 log]# systemctl status rsyslog *●*rsyslog.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: *failed*(Result: start-limit) since Fri 2018-01-05 17:48:19 UTC; 6s ago Docs: man:rsyslogd(8) http://www.rsyslog.com/doc/ Process: 862 ExecStart=/usr/sbin/rsyslogd -n $SYSLOGD_OPTIONS *(code=killed, signal=SEGV)* Main PID: 862 (code=killed, signal=SEGV)

Jan 05 17:48:19 centos-rpi3 systemd[1]: rsyslog.service holdoff time over, scheduling restart. Jan 05 17:48:19 centos-rpi3 systemd[1]: *start request repeated too quickly for rsyslog.service* Jan 05 17:48:19 centos-rpi3 systemd[1]: *Failed to start System Logging Service.* Jan 05 17:48:19 centos-rpi3 systemd[1]: *Unit rsyslog.service entered failed state.* Jan 05 17:48:19 centos-rpi3 systemd[1]: *rsyslog.service failed.*

*Thanks!*

*Philip.*

Works on my rpi3, so have you changed the default config to allow remote logging or anything else ? The only thing is that it shows the service started a looooong time ago, but because chronyd is started after :

● rsyslog.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: active (running) since Thu 1970-01-01 00:00:07 UTC; 48 years 0 months ago

-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

---

Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev