Bug #4582
closed
Last update detection is broken, causing cron remove cf_lock database and flood with emails every 5 minutes
Added by Nicolas CHARLES over 10 years ago.
Updated over 10 years ago.
Category:
System techniques
Description
Cron now floods with mail, saying
WARNING: The file /var/rudder/cfengine-community/last_successful_inputs_update is older than 10 minutes, the agent are probably stuck. Purging the TokyoCabinet lock file... Done
Indeed du to a logical error, the file /var/rudder/cfengine-community/last_successful_inputs_update is updated only if the promises have actually been updated (and not only if the node could correctly connect to the node), resulting to a very often old /var/rudder/cfengine-community/last_successful_inputs_update file
- Status changed from New to Pending technical review
- Assignee set to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/314
- Target version changed from 2.8.4 to 2.6.12
This also needs fixing in 2.6.
- Pull Request changed from https://github.com/Normation/rudder-techniques/pull/314 to https://github.com/Normation/rudder-techniques/pull/315
- Subject changed from Cron floods with mail to Last update detection is broken, causing cron to flood with emails
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:24db47ff98e209cc4255a5a053465d6063b030b4.
Applied in changeset policy-templates:commit:3b157e44859ae84a264cbf6803f280fca0f2dc3b.
- Subject changed from Last update detection is broken, causing cron to flood with emails to Last update detection is broken, causing cron remove cf_lock database and flood with emails every 5 minutes
In addition it tries to delete the wrong file: ${CFE_DIR}/state/cf_lock.tdcb.lock (typo in the extension).
I would also change the message to read the agent is probably stuck
To be clear - the above typos are not in the policies but in the check-rudder-agent script.
Bug #4604 has been created to track this
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.12, which was released today.
Check out:
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE 
Updated by 
Updated by