Skip to content
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.

cron error from logrotate #139

Closed
pjeby opened this issue Aug 20, 2017 · 7 comments
Closed

cron error from logrotate #139

pjeby opened this issue Aug 20, 2017 · 7 comments

Comments

@pjeby
Copy link
Contributor

pjeby commented Aug 20, 2017

Just got this email from the container:

etc/cron.daily/logrotate:
invoke-rc.d: action rotate is unknown, but proceeding anyway.
invoke-rc.d: policy-rc.d denied execution of rotate.

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. :)

@hardware
Copy link
Owner

I never had this error. Anyway, I will switch the master branch (1.0) to Debian Stretch, maybe this issue will be solved.

@hardware
Copy link
Owner

I think you can ignore this warning, this is probably nothing serious. If you have time, you can try the latest 1.1 version.

1.1-stable will be released this week-end #122

@vizv
Copy link
Contributor

vizv commented Sep 3, 2017

I got the error from time to time... (I have a catch-all email account setup).

I got this today:

...
Received: by ****.****.com (Postfix, from userid 0)
	id *************; Sun,  3 Sep 2017 06:33:22 +0000 (UTC)
From: root@****.com (Cron Daemon)
To: root@****.com
Subject: Cron <root@****> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
Message-Id: <***>
Date: Sun,  3 Sep 2017 06:33:22 +0000 (UTC)

/etc/cron.daily/logrotate:
pkill: pidfile not valid
Try `pkill --help' for more information.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of rotate.

edit: It's nothing serious, but the problem do exists.

@hardware
Copy link
Owner

hardware commented Sep 3, 2017

I applied @sigmike's patch here : 160c222

@hardware hardware reopened this Sep 3, 2017
@vizv
Copy link
Contributor

vizv commented Sep 3, 2017

Thanks, this should fix the problem, it's not a serious issue, but quite annoying.

@ksylvan
Copy link
Contributor

ksylvan commented Sep 4, 2017

How risky is it to run 1.1-latest versus 1.1-stable? ;-) I'm tempted to switch one of my servers to run 1.1-latest.

@hardware
Copy link
Owner

hardware commented Sep 4, 2017

I run the 1.1-latest on 2 servers permanently, It's not very risky, all builds on this branch are validated through the CI automation system, so it's pretty safe. 1.1-stable is useful when you want a more tested build.

@hardware hardware closed this as completed Sep 5, 2017
hardware added a commit that referenced this issue Sep 12, 2017
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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants