Syslog doesn't rotate

Hi, OMV WebGUI today says that my syslog is 680 pages, 34000 records, and the last and only time he did logrotate was 9 days ago. I reinstalled the system recently.

All the files in /etc/logrotate.d have the date of today boot.

if I have a look into the files many of them (but not all) seem corrupt, here are some:

rsyslog
# see "man logrotate" for details
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log f^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^$

nginx
# see "man logrotate" for details
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
#^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$

salt-common
 see "man logrotate" for details
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4Is there a way to bypass this strange situation and allow to rotate the logs correctly, a time a week and storing them in a compressed way ? 
# create new (empty) log files after rotati^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$

samba
# see "man logrotate" for details
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
#^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$

It seems there are strange characters (00 in hexadecimal) inside the files that truncate the scripts. Some file starting with "{" don't have the ending "}".

I don't know why, because the syslog management is completely in charge to Armbian that define the base rules.

Is there a way to bypass this strange situation and allow to rotate the logs correctly, once a week and storing them in a compressed way ?

I hope it is not necessary to rebuilt the system from scratch, I have done this too many times already.

I tried to get by on my own trying to understand a little more:

systemctl status logrotate.service
● logrotate.service - Rotate log files
   Loaded: loaded (/etc/systemd/system/logrotate.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-09-07 23:37:34 CEST; 30s ago
     Docs: man:logrotate(8)
           man:logrotate.conf(5)
  Process: 7145 ExecStartPre=/usr/lib/armbian/armbian-ramlog write (code=exited, status=0/SUCCESS)
  Process: 7146 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE)
 Main PID: 7146 (code=exited, status=1/FAILURE)

Sep 07 23:37:34 arxiv systemd[1]: Starting Rotate log files...
Sep 07 23:37:34 arxiv logrotate[7146]: error: /etc/logrotate.conf:1 missing '{' after log files definition
Sep 07 23:37:34 arxiv systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 23:37:34 arxiv systemd[1]: logrotate.service: Failed with result 'exit-code'.
Sep 07 23:37:34 arxiv systemd[1]: Failed to start Rotate log files.

So logrotate doesn't work because the scripts and the configuration files are corrupted and this was what I suspected.

But if I try to uninstall logrotate, to reinstall it again hoping it rebuilts those files, I get the warning:

"The following packages will be REMOVED:

logrotate openmediavault openmediavault-flashmemory openmediavault-omvextrasorg openmediavault-resetperms openmediavault-usbbackup"

So logrotate is strictly connected to OMV modules.

This makes me think who may have changed those scripts and configuration files ....

I think that the only solution to my problem is to start over by installing Armbian, OMV and Nextcloud.

I am certainly not very skilled, but a software that constantly forces me to reinstall the whole system is not the best !!

Probably thousands of users will disagree because they are completely satisfied, but after more than 2 months of "beta testing" I still haven't been able to put the services into "production". I just keep reinstalling everything all over again, until to meet the next problem...

Zitat von gderf

A harmless thing to try before doing drastic things is:

apt-get install --reinstall openmediavault

Good advice. Thanks.