Koozali.org: home of the SME Server

Obsolete Releases => SME Server 9.x => Topic started by: morpheus on November 02, 2017, 05:35:26 AM

Title: Problems with log rotation after server crash due to full drive
Post by: morpheus on November 02, 2017, 05:35:26 AM

On fully updated 9.2, getting the following error report after disk full problem due to failed usb backup drive:

/etc/cron.daily/logrotate:

error: failed to open config file clamav-unofficial-sigs-logrotate: No such file or directory
error: found error in file clamav-unofficial-sigs-logrotate, skipping
error: stat of /var/log/cron failed: No such file or directory
error: stat of /var/log/maillog failed: No such file or directory
error: stat of /var/log/messages failed: No such file or directory
error: stat of /var/log/secure failed: No such file or directory
error: stat of /var/log/spooler failed: No such file or directory

The files do exist

Title: Re: Problems with log rotation after server crash due to full drive
Post by: Jean-Philippe Pialasse on November 02, 2017, 10:52:14 PM

those files are links pointing to target files that might be missing.

you got it once ? or every days since ?

Title: Re: Problems with log rotation after server crash due to full drive
Post by: morpheus on November 13, 2017, 07:05:08 AM

Every day since

Title: Re: Problems with log rotation after server crash due to full drive
Post by: mab974 on November 17, 2017, 06:18:05 AM

i have a similar problem from time to time when i update one of my server (9.2 with dummy NIC).
every /var/log/messages, ... point to inexisting files and generally awstats send me a ton of messages.

i have to reboot the server to fix the problem. I do not know the reason yet ... but i saved a set of logfiles the last time

Title: Re: Problems with log rotation after server crash due to full drive
Post by: CharlieBrady on November 21, 2017, 08:16:00 PM

Quote from: mab974 on November 17, 2017, 06:18:05 AM

i have a similar problem from time to time when i update one of my server (9.2 with dummy NIC).
every /var/log/messages, ... point to inexisting files and generally awstats send me a ton of messages.

This is a clear indication that log rotation has run, but syslog has not been restarted/sighuped.