-
Notifications
You must be signed in to change notification settings - Fork 324
cron error from logrotate #139
Comments
I never had this error. Anyway, I will switch the master branch (1.0) to Debian Stretch, maybe this issue will be solved. |
I think you can ignore this warning, this is probably nothing serious. If you have time, you can try the latest 1.1 version.
|
I got the error from time to time... (I have a catch-all email account setup). I got this today:
edit: It's nothing serious, but the problem do exists. |
Thanks, this should fix the problem, it's not a serious issue, but quite annoying. |
How risky is it to run |
I run the |
Error : "pkill: pidfile not valid" is triggered because /run/clamav/freshclam.pid doesn't exist when freshclam is disabled, so reload-log init task can't run properly. More info : /etc/init.d/clamav-freshclam
Just got this email from the container:
Googling it finds me this rsyslog fix committed in 2015, but which appears to not be applied in this container's
/etc/logrotate.d/rsyslog
. But the build doesn't generate that file, so it appears that it's an older rsyslog version installed. The file date in the container is December 2015, so perhaps the fix hadn't made it downstream to the debian package yet.I must confess I lack the debian-fu to investigate further. :)
The text was updated successfully, but these errors were encountered: