Project

General

Profile

Actions
Copy link

Bug #4582

closed

Last update detection is broken, causing cron remove cf_lock database and flood with emails every 5 minutes

Bug #4582: Last update detection is broken, causing cron remove cf_lock database and flood with emails every 5 minutes

Added by Nicolas CHARLES almost 12 years ago. Updated almost 12 years ago.

Status:
Released
Priority:
2
Assignee:
Jonathan CLARKE
Category:
System techniques
Target version:
2.6.12
Pull Request:
https://github.com/Normation/rudder-t...
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 open — 3 closed)

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

Updated by Nicolas CHARLES almost 12 years ago Actions
Copy link
 #2

  • 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

Updated by Jonathan CLARKE almost 12 years ago Actions
Copy link
 #3

  • Target version changed from 2.8.4 to 2.6.12

This also needs fixing in 2.6.

Updated by Nicolas CHARLES almost 12 years ago Actions
Copy link
 #4

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

Updated by Jonathan CLARKE almost 12 years ago Actions
Copy link
 #5

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

Updated by Nicolas CHARLES almost 12 years ago Actions
Copy link
 #6

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

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

Updated by Jonathan CLARKE almost 12 years ago Actions
Copy link
 #7

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

Updated by Jonathan CLARKE almost 12 years ago Actions
Copy link
 #8

  • 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

Updated by Alex Tkachenko almost 12 years ago Actions
Copy link
 #9

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

Updated by Alex Tkachenko almost 12 years ago Actions
Copy link
 #10

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

Updated by Nicolas CHARLES almost 12 years ago Actions
Copy link
 #11

good catch Alex !

Updated by Nicolas CHARLES almost 12 years ago Actions
Copy link
 #12

Bug #4604 has been created to track this

Updated by Vincent MEMBRÉ almost 12 years ago Actions
Copy link
 #13

  • Status changed from Pending release to Released

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

Actions
Copy link

Also available in: PDF Atom