Bug 487545 – jobs aren't getting run.

Bug 487545 - jobs aren't getting run.

Summary:	jobs aren't getting run.

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	selinux-policy-targeted (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Daniel Walsh
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2009-02-26 11:42 EST by Dave Jones
Modified:	2015-01-04 17:30 EST (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2009-02-26 13:07:59 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Dave Jones 2009-02-26 11:42:08 EST

The mrtg package creates /etc/cron.d/mrtg
which is..

MAILTO=root
* * * * * root LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg --lock-file /var/lock/mrtg/mrtg_l --confcache-file /var/lib/mrtg/mrtg.ok

This seems to not be getting run.

iirc, this happened a while ago too, but I can't remember what happened to fix it.

stracing the crond process shows it sleeping for 60s, waking up, and then doing nothing.

Comment 1 Dave Jones 2009-02-26 11:44:50 EST

466018 was the last time, that turned out to be selinux related.

But I'm not seeing selinux denials, and the labelling on the file looks ok.

Comment 2 Dave Jones 2009-02-26 11:47:01 EST

ah, there's the problem.. (I forgot cron had its own log, and was looking in syslog)

Feb 26 09:52:01 firewall crond[7644]: (*system*) ERROR (Could not set exec or keycreate context to system_u:system_r:system_cronjob_t:SystemLow-SystemHigh for user)
Feb 26 09:52:01 firewall crond[7644]: (root) ERROR (failed to change SELinux context)

Comment 3 Dave Jones 2009-02-26 13:07:59 EST

did a yum update to todays bits, and it seems to work again.

Note You need to log in before you can comment on or make changes to this bug.