Thanks Mario! I'm cutting this down a bit for readability ... > root@ilzlnx4:~# sudo logrotate --force --verbose /etc/logrotate.conf > ... > rotating pattern: /var/log/syslog > considering log /var/log/syslog > log does not need rotating (log is empty)
This seems to happen at a time the process is already broken and the logging dead. Any chance to catch the logrotate that switches it from working to failing if that shows anything different? > ... > root@ilzlnx4:~# logger -e "Test Error" > ... > root@ilzlnx4:~# tail /var/log/syslog > ... > Note that after the journal command also the syslog file was check and it > still empty Yeah that really means it is active but not taking up messages it should take :-/ > - Enable the syslog debugger with the env variables and restarted the service > ... > After reboot and activate the syslog debug mode, the syslog crashed again. > > root@ilzlnx4:~# tail /var/log/syslog > root@ilzlnx4:~# logger "Test Error" > root@ilzlnx4:~# tail /var/log/syslog > > Attaching the debug log file generated: rsyslog.debug The file did not get mirrored/attached in case that was a mail attachment. Could someone get that attached to the bug on launchpad? Also since this again was called a "crash" (I doubt since in the logs before it seemed the PID stayed the same, but if there is a chance) is there a crash file in /var/crash for it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896575 Title: [UBUNTU 20.04] syslog daemon stop running unexpectedly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896575/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
