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 over 8 years ago. Updated over 8 years ago.

Status:
Released
Priority:
2
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
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 #2

Updated by Nicolas CHARLES over 8 years ago

  • 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
Actions #3

Updated by Jonathan CLARKE over 8 years ago

  • Target version changed from 2.8.4 to 2.6.12

This also needs fixing in 2.6.

Actions #4

Updated by Nicolas CHARLES over 8 years ago

  • Pull Request changed from https://github.com/Normation/rudder-techniques/pull/314 to https://github.com/Normation/rudder-techniques/pull/315
Actions #5

Updated by Jonathan CLARKE over 8 years ago

  • Subject changed from Cron floods with mail to Last update detection is broken, causing cron to flood with emails
Actions #6

Updated by Nicolas CHARLES over 8 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset policy-templates:commit:24db47ff98e209cc4255a5a053465d6063b030b4.

Actions #7

Updated by Jonathan CLARKE over 8 years ago

Applied in changeset policy-templates:commit:3b157e44859ae84a264cbf6803f280fca0f2dc3b.

Actions #8

Updated by Jonathan CLARKE over 8 years ago

  • 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
Actions #9

Updated by Alex Tkachenko over 8 years ago

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

Actions #10

Updated by Alex Tkachenko over 8 years ago

To be clear - the above typos are not in the policies but in the check-rudder-agent script.

Actions #11

Updated by Nicolas CHARLES over 8 years ago

good catch Alex !

Actions #12

Updated by Nicolas CHARLES over 8 years ago

Bug #4604 has been created to track this

Actions #13

Updated by Vincent MEMBRÉ over 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.12, which was released today.
Check out:

Actions

Also available in: Atom PDF