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

  • Hi professionals

    Powering up my system is bring back a logrotate.service error... (Not the first time)...

    No idea for any reason... shutting down and booting up again... Everything is fine...


    ....

    Apr 20 17:45:31 pr-srv-01 anacron[798]: Anacron 2.3 started on 2025-04-20

    Apr 20 17:45:31 pr-srv-01 systemd[1]: Started cpufrequtils.service - LSB: set CPUFreq kernel parameters.

    Apr 20 17:45:31 pr-srv-01 systemd[1]: Started php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager.

    Apr 20 17:45:31 pr-srv-01 anacron[798]: Will run job `cron.daily' in 5 min.

    Apr 20 17:45:31 pr-srv-01 anacron[798]: Jobs will be executed sequentially

    Apr 20 17:45:31 pr-srv-01 systemd[1]: Starting phpsessionclean.service - Clean php session files...

    Apr 20 17:45:31 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

    Apr 20 17:45:31 pr-srv-01 folder2ram[441]: start /var/spool

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: System Journal (/var/log/journal/21bdaa7233734a9491a6b4852adf96b0) is 111.6M, max >

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Received client request to rotate journal, rotating.

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Deleted archived journal /var/log/journal/21bdaa7233734a9491a6b4852adf96b0/system@>

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Vacuuming done, freed 8.0M of archived journals from /var/log/journal/21bdaa723373>

    Apr 20 17:45:32 pr-srv-01 logrotate[807]: error: state file /var/lib/logrotate/status is already locked

    Apr 20 17:45:32 pr-srv-01 logrotate[807]: logrotate does not support parallel execution on the same set of logfiles.

    Apr 20 17:45:32 pr-srv-01 systemd[1]: logrotate.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED

    Apr 20 17:45:32 pr-srv-01 systemd[1]: logrotate.service: Failed with result 'exit-code'.

    Apr 20 17:45:32 pr-srv-01 systemd[1]: Failed to start logrotate.service - Rotate log files.

    Apr 20 17:45:32 pr-srv-01 folder2ram[441]: start /var/lib/rrdcached

    Apr 20 17:45:32 pr-srv-01 systemd[1]: eth-network-optimization.service: Deactivated successfully.

    Apr 20 17:45:32 pr-srv-01 systemd[1]: Finished eth-network-optimization.service - Set enp2s0+enp3s0 network optimizations.

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: System Journal (/var/log/journal/21bdaa7233734a9491a6b4852adf96b0) is 109.4M, max >

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Received client request to rotate journal, rotating.

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Deleted archived journal /var/log/journal/21bdaa7233734a9491a6b4852adf96b0/system@>

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Vacuuming done, freed 3.5M of archived journals from /var/log/journal/21bdaa723373>

    Apr 20 17:45:32 pr-srv-01 systemd[1]: phpsessionclean.service: Deactivated successfully.

    Apr 20 17:45:32 pr-srv-01 systemd[1]: Finished phpsessionclean.service - Clean php session files.

    Apr 20 17:45:32 pr-srv-01 folder2ram[441]: start /var/lib/monit

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: System Journal (/var/log/journal/21bdaa7233734a9491a6b4852adf96b0) is 105.0M, max >

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Received client request to rotate journal, rotating.

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Deleted archived journal /var/log/journal/21bdaa7233734a9491a6b4852adf96b0/system@>

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Deleted archived journal /var/log/journal/21bdaa7233734a9491a6b4852adf96b0/system@>

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Vacuuming done, freed 7.1M of archived journals from /var/log/journal/21bdaa723373>

    Apr 20 17:45:32 pr-srv-01 folder2ram[441]: start /var/cache/samba

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: System Journal (/var/log/journal/21bdaa7233734a9491a6b4852adf96b0) is 101.4M, max >

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Received client request to rotate journal, rotating.

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Deleted archived journal /var/log/journal/21bdaa7233734a9491a6b4852adf96b0/system@>

    Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Vacuuming done, freed 3.5M of archived journals from /var/log/journal/21bdaa723373>

    Apr 20 17:45:33 pr-srv-01 systemd-networkd[334]: enp2s0: Gained carrier

    Apr 20 17:45:33 pr-srv-01 kernel: e1000e 0000:02:00.0 enp2s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

    ...


    Any suggestions?


    Best regards

    prtigger

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro Sata DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB Sata (Btrfs Raid1) | OMV 7.x services: SSH, SMB, NFS, DLNA, Flashmemory

    • Official Post

    Apr 20 17:45:32 pr-srv-01 logrotate[807]: error: state file /var/lib/logrotate/status is already locked

    Apr 20 17:45:32 pr-srv-01 logrotate[807]: logrotate does not support parallel execution on the same set of logfiles.

    What is the output of

    journalctl -u logrotate.service

  • macom


    Here it is:

    root@pr-srv-01:~# journalctl -u logrotate.service

    Apr 20 17:45:31 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

    Apr 20 17:45:32 pr-srv-01 logrotate[807]: error: state file /var/lib/logrotate/status is already locked

    Apr 20 17:45:32 pr-srv-01 logrotate[807]: logrotate does not support parallel execution on the same set of logfiles.

    Apr 20 17:45:32 pr-srv-01 systemd[1]: logrotate.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED

    Apr 20 17:45:32 pr-srv-01 systemd[1]: logrotate.service: Failed with result 'exit-code'.

    Apr 20 17:45:32 pr-srv-01 systemd[1]: Failed to start logrotate.service - Rotate log files.

    root@pr-srv-01:~#


    Best regards

    prtigger

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro Sata DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB Sata (Btrfs Raid1) | OMV 7.x services: SSH, SMB, NFS, DLNA, Flashmemory

  • In addition:

    Just a cold power on of my system!

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro Sata DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB Sata (Btrfs Raid1) | OMV 7.x services: SSH, SMB, NFS, DLNA, Flashmemory

  • macom

    Good morning

    Just power up my server (Hanging on switchable powerplug! Over night system is powerfree)... The same problem:


    root@pr-srv-01:~# journalctl -u logrotate.service

    Apr 21 08:03:41 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

    Apr 21 08:03:42 pr-srv-01 logrotate[759]: error: state file /var/lib/logrotate/status is already locked

    Apr 21 08:03:42 pr-srv-01 logrotate[759]: logrotate does not support parallel execution on the same set of logfiles.

    Apr 21 08:03:42 pr-srv-01 systemd[1]: logrotate.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED

    Apr 21 08:03:42 pr-srv-01 systemd[1]: logrotate.service: Failed with result 'exit-code'.

    Apr 21 08:03:42 pr-srv-01 systemd[1]: Failed to start logrotate.service - Rotate log files.

    root@pr-srv-01:~#


    Shutdown system.., start again:

    No failure again...


    OMV is uptodate!


    Best regards

    prtigger

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro Sata DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB Sata (Btrfs Raid1) | OMV 7.x services: SSH, SMB, NFS, DLNA, Flashmemory

  • Buy the way:

    I can clear up journal with:


    sudo journalctl --flush --rotate --vacuum-time=30s

    sudo journalctl --user --flush --rotate --vacuum-time=30s


    This may help for a while...

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro Sata DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB Sata (Btrfs Raid1) | OMV 7.x services: SSH, SMB, NFS, DLNA, Flashmemory

    • Official Post

    logrotate.service is triggered by logrotate.timer on a daily basis


    post the output of

    Code
    systemctl start logrotate.service
    systemctl status logrotate.service
    journalctl -u logrotate.service
  • How do you shutdown the server?

    Hi macom


    Shutdown:

    'shutdown' at console or with putty... After that logout with <strg>-d... And wait for power-off...


    Startup:

    I switch on the power-distribution where the server power cord is plugged in....

    Waiting till network light is beginning to flash (Mainboard has power good signal)...

    Press power on button at the server...


    Nothing special! My system is only running when i need it. The other time it is power free...


    Here the actual output:


    root@pr-srv-01:~# systemctl start logrotate.service

    root@pr-srv-01:~# systemctl status logrotate.service

    ○ logrotate.service - Rotate log files

    Loaded: loaded (/lib/systemd/system/logrotate.service; static)

    Active: inactive (dead) since Mon 2025-04-21 11:56:09 CEST; 14s ago

    TriggeredBy: ● logrotate.timer

    Docs: man:logrotate(8)

    man:logrotate.conf(5)

    Process: 3296 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=0/SUCCESS)

    Main PID: 3296 (code=exited, status=0/SUCCESS)

    CPU: 301ms


    Apr 21 11:56:09 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

    Apr 21 11:56:09 pr-srv-01 systemd[1]: logrotate.service: Deactivated successfully.

    Apr 21 11:56:09 pr-srv-01 systemd[1]: Finished logrotate.service - Rotate log files.

    root@pr-srv-01:~# journalctl -u logrotate.service

    Apr 21 08:03:41 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

    Apr 21 08:03:42 pr-srv-01 logrotate[759]: error: state file /var/lib/logrotate/status is already locked

    Apr 21 08:03:42 pr-srv-01 logrotate[759]: logrotate does not support parallel execution on the same set of logfiles.

    Apr 21 08:03:42 pr-srv-01 systemd[1]: logrotate.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED

    Apr 21 08:03:42 pr-srv-01 systemd[1]: logrotate.service: Failed with result 'exit-code'.

    Apr 21 08:03:42 pr-srv-01 systemd[1]: Failed to start logrotate.service - Rotate log files.

    -- Boot 751038e34e674b07a474e75dab3bb80d --

    Apr 21 11:56:09 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

    Apr 21 11:56:09 pr-srv-01 systemd[1]: logrotate.service: Deactivated successfully.

    Apr 21 11:56:09 pr-srv-01 systemd[1]: Finished logrotate.service - Rotate log files.

    root@pr-srv-01:~#


    Best regards

    prtigger

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro Sata DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB Sata (Btrfs Raid1) | OMV 7.x services: SSH, SMB, NFS, DLNA, Flashmemory

    • Official Post

    Apr 21 11:56:09 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

    Apr 21 11:56:09 pr-srv-01 systemd[1]: logrotate.service: Deactivated successfully.

    Apr 21 11:56:09 pr-srv-01 systemd[1]: Finished logrotate.service - Rotate log files.

    Seems you just have to wait for the next time that logrotate is executed. As you don't run your server 24/7 you might add a scheduled job that runs at reboot and add this as command:


    sleep 60 && systemctl start logrotate.service

    • Official Post

    I can clear up journal with:


    sudo journalctl --flush --rotate --vacuum-time=30s

    sudo journalctl --user --flush --rotate --vacuum-time=30s


    This may help for a while...

    Be aware that this clears up the journal, but it does not rotate the *.log files.

  • Seems you just have to wait for the next time that logrotate is executed. As you don't run your server 24/7 you might add a scheduled job that runs at reboot and add this as command:


    sleep 60 && systemctl start logrotate.service

    Hi macom

    I'm wondering about this, because i think this bootup fail is new with the reinstall of OMV.

    Do you have a small explanation how to create such a job?


    Be aware that this clears up the journal, but it does not rotate the *.log files.

    Is there any better way or command to get rid of all the old journal files?


    Thanks for your help and best regards

    prtigger

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro Sata DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB Sata (Btrfs Raid1) | OMV 7.x services: SSH, SMB, NFS, DLNA, Flashmemory

  • For me it's looking like a timing problem during boot...???

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro Sata DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB Sata (Btrfs Raid1) | OMV 7.x services: SSH, SMB, NFS, DLNA, Flashmemory

    • Official Post

    Is there any better way or command to get rid of all the old journal files?

    journal and log are two different things (with the same purpose)


    The journal is collection most of the logs in one place.

    Are you concerned about the journal or the logs?

  • Hi macom

    I'm not a pro... The only thing i know is, that all the logs like messages, syslog.. are concentrated in the journal, like a database... I want to cleanup this because

    it's getting bigger and bigger....

    You can correct me if i'm wrong.. My Linux knowledge is really old from 1991-1995 with kernel 0.99... I have to learn a lot of the actual stuff...


    Best regards

    prtigger

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro Sata DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB Sata (Btrfs Raid1) | OMV 7.x services: SSH, SMB, NFS, DLNA, Flashmemory

  • It´s not long ago i done the commands from #6


    Here the output:

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro Sata DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB Sata (Btrfs Raid1) | OMV 7.x services: SSH, SMB, NFS, DLNA, Flashmemory

    Edited once, last by prtigger1 ().

    • Official Post

    ok, /var/log is quite small.


    Did you check if there are repeating messages in the journal indicating an issue?


    journalctl -e and scroll up to see if the same message occurs over and over again.


    That command opens the journal and shows the most current info.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!