Project

General

Profile

Actions

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 about 10 years ago. Updated about 10 years ago.

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

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


Related issues 3 (0 open3 closed)

Related to Rudder - Bug #4604: Typo in the deletion of lock file if the promises are not updatedReleasedJonathan CLARKE2014-03-12Actions
Related to Rudder - Bug #4752: cf_lock.tcdb is not cleaned by check-rudder-agent script when update file is older than 10 minutesReleasedJonathan CLARKE2014-04-11Actions
Related to Rudder - Bug #4769: rudder-agent may be stucked by tokyo cabinet database bloatingReleasedJonathan CLARKE2014-04-23Actions
Actions

Also available in: Atom PDF