Project

General

Profile

Actions

Bug #3730

closed

Cron on RHEL/CentOS and Ubuntu nodes was not checked with initial promises

Added by Jonathan CLARKE about 11 years ago. Updated about 11 years ago.

Status:
Released
Priority:
3
Assignee:
Jonathan CLARKE
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Similar to #3609, cf-agent tries to check that cron is running when the initial promises are run (this happens when a node just got rudder-agent installed, but has not yet been accepted by the Rudder server). On RHEL/CentOS systems, this fails as follows:

 -> Making a one-time restart promise for /usr/sbin/cron$
Proposed executable file "/etc/init.d/cron" doesn't exist
/etc/init.d/cron restart promises to be executable but isn't
I: Report relates to a promise with handle "" 
I: Made in version 'not specified' of '/var/rudder/cfengine-community/inputs/promises.cf' near line 372
I: Comment: Restarting crond

Note: this may also happen on ubuntu systems.

I will "port" the fix from #3609 to initial promises.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #3609: Cron on RHEL/CentOS nodes was restarted at every execution of CFEngineReleasedNicolas PERRON2013-05-24Actions
Actions

Also available in: Atom PDF