Anacron job 'cron.daily' errors on OMV4 (NanoPi NEO) after firmware update

  • After running system firmware update from Armbian-Config utility with OMV4 installation running on NanoPi NEO we are receiving the following notifications each day.


    Armbian 5.90 stable

    OMV 4.1.36-1 (Arrakis) installed from Armbian Softy Utility



    /etc/cron.daily/logrotate:

    error: apt:8 lines must begin with a keyword or a filename (possibly in double quotes)

    error: aptitude:5 unknown option 'missi' -- ignoring line

    error: armbian-hardware-monitor:8 unknown option 'sh' -- ignoring line

    error: cron-apt:10 missing '{' after log files definition

    error: found error in file cron-apt, skipping

    error: dpkg:prerotate, postrotate or preremove without endscript

    error: found error in file dpkg, skipping

    error: monit:9 lines must begin with a keyword or a filename (possibly in double quotes)

    error: netatalk:9 unknown option 'sha' -- ignoring line

    error: nginx:9 lines must begin with a keyword or a filename (possibly in double quotes)

    error: openmediavault-rsync:prerotate, postrotate or preremove without endscript

    error: found error in file openmediavault-rsync, skipping

    error: pm-utils:9 unknown option 'shared' -- ignoring line

    error: proftpd-basic:25 lines must begin with a keyword or a filename (possibly in double quotes)

    error: rsyslog:prerotate, postrotate or preremove without endscript

    error: found error in file rsyslog, skipping

    error: samba:8 lines must begin with a keyword or a filename (possibly in double quotes)

    error: unattended-upgrades:12 unknown option 'compre' -- ignoring line

    error: stat of /var/log/netatalk.log failed: No such file or directory

    run-parts: /etc/cron.daily/logrotate exited with return code 1


    Please may we ask for step-by-step instructions to resolve. Forgive me but our linux skills are limited so the simpler the instructions the better!


    If any more information is required then please feel free to ask and we will happily provide.


    Thanks in advance for any help.

  • After running system firmware update from Armbian-Config utility

    Did you create a backup before this update was applied? if non was made, chances are low to repair it and OMV is long end-of-life(EOL) but the data would be accessible by a new OMV5 installation.


    to assess if a repair can made, please post output of command cat /etc/cron.daily/logrotate

    omv 6.1.4-2 (Shaitan) on RPi CM4/4GB with 64bit Kernel 5.15.84-v8+

    2x 6TB 3.5'' HDDs (CMR) formatted with ext4 via 2port PCIe SATA card with ASM1061R chipset providing hardware supported RAID1


    omv 5.6.21-1 (usul) on RPi4/4GB with 32bit Kernel 5.10.63 and WittyPi 3 V2 RTC HAT

    2x 3TB 3.5'' HDDs (CMR) formatted with ext4 in Icy Box IB-RD3662-C31 / hardware supported RAID1

    For Read/Write performance of SMB shares hosted on this hardware see forum here

  • Hi mi-hol,

    Thanks for the prompt reply. Sorry that I did not acknowledge sooner.

    I think that I will try a rebuild of the system using OMV5 (if it can be installed OK on NanoPi NEO) and go from there since OMV4 is EOL.

    All the best.

    Protek

Participate now!

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