Still logrotate.service failed during boot with my clean reinstall and old flashmemory plugin (6.1.133-1 kernel)

I just checked the whole output of

journalctl (3500 lines). There are no errors or warnings i had never seen before, after boot.

Only the part i described here in this case.

May be a stupid question:

What about the logs outside of the journal?

What is happening with them?

Thanks for your help

prtigger

What i still not understand is:

What is running parallel when logrotate.service tries to startup during the first boot (reading the log i posted, status is locked)?

And why is everything fine when i shutdown the system after this and boot again??

Why should a start of logrotate.service every boot help (just more compressed files)?

Best regards

prtigger

Ok, thanks..

I'll keeping my eyes on!

macom

ryecoaaron

Hi pro´s

After uninstalling the stable flashmemory plugin, the problem with failed starting of 'logrotate.service', from server

powerless bootup state, is solved...

It may depend on a timing or race condition, because a shutdown and reboot of the system after failed

'logrotate.service' start message, is showing no failure anymore...

root@pr-srv-01:~# journalctl -u logrotate.service
Apr 28 18:35:20 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...
Apr 28 18:35:21 pr-srv-01 systemd[1]: logrotate.service: Deactivated successfully.
Apr 28 18:35:21 pr-srv-01 systemd[1]: Finished logrotate.service - Rotate log files.
-- Boot 24a45e54cf5445f7ade617c9cb22aba9 --
Apr 29 20:44:07 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...
Apr 29 20:44:07 pr-srv-01 systemd[1]: logrotate.service: Deactivated successfully.
Apr 29 20:44:07 pr-srv-01 systemd[1]: Finished logrotate.service - Rotate log files.
root@pr-srv-01:~#

A solution could be:

Starting 'logrotate.service' when OMV system is full up.... (later, than configured now!)

Best regards

prtigger