Topic: Rsyslog crash on weekly logrotate iRedMail 0.9.9 and Ubuntu 18.04
New install (not upgraded from 0.9.8)
Similar to https://forum.iredmail.org/topic15256-s … ian-9.html
Every week the files in /var/log are rotated and new empty files created, but the rsyslog service fails to start.
root@moroni:/var/log# service rsyslog status
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Sun 2019-05-26 06:25:27 UTC; 4 days ago
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Process: 12854 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=0/SUCCESS)
Main PID: 12854 (code=exited, status=0/SUCCESS)May 26 06:25:26 moroni rsyslogd[12854]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.32.0]
May 26 06:25:26 moroni rsyslogd[12854]: rsyslogd's groupid changed to 106
May 26 06:25:26 moroni rsyslogd[12854]: rsyslogd's userid changed to 102
May 26 06:25:26 moroni rsyslogd[12854]: [origin software="rsyslogd" swVersion="8.32.0" x-pid="12854" x-info="http://www.rsyslog.com"] start
May 26 06:25:27 moroni systemd[1]: Stopping System Logging Service...
May 26 06:25:27 moroni rsyslogd[12854]: [origin software="rsyslogd" swVersion="8.32.0" x-pid="12854" x-info="http://www.rsyslog.com"] exiting on signal 15.
May 26 06:25:27 moroni systemd[1]: Stopped System Logging Service.
May 26 06:25:27 moroni systemd[1]: rsyslog.service: Start request repeated too quickly.
May 26 06:25:27 moroni systemd[1]: rsyslog.service: Failed with result 'start-limit-hit'.
May 26 06:25:27 moroni systemd[1]: Failed to start System Logging Service.
Manually executing service rsyslog start restarts it just fine.
Ideas?
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.