Project

General

Profile

Actions
Copy link

Bug #10771

closed

check-rudder-agent doesn't purge the lmdb file when run via cron

Added by Nicolas CHARLES over 7 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Agent
Target version:
3.1.21
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Sometimes, the check-rudder-agent task does not clean the lmdb lock file when run in cron

We've seen it twice, once on RedHat 6, once in SLESS11

There is no explanation on why however.
When ran manually, we get:

check_and_fix_cf_lock
+ MAX_CF_LOCK_SIZE=10485760
+ '[' -e /var/rudder/cfengine-community/state/cf_lock.lmdb ']'
+ '[' zLinux = zAIX ']'
++ stat -c%s /var/rudder/cfengine-community/state/cf_lock.lmdb
+ CF_LOCK_SIZE=104853504
+ '[' 104853504 -ge 10485760 ']'
+ echo_n 'WARNING: The file /var/rudder/cfengine-community/state/cf_lock.lmdb is too big (104853504 bytes), purging it...'
+ '[' zLinux = zAIX ']'
+ echo -n WARNING: The file /var/rudder/cfengine-community/state/cf_lock.lmdb is too big '(104853504' 'bytes),' purging it...
WARNING: The file /var/rudder/cfengine-community/state/cf_lock.lmdb is too big (104853504 bytes), purging it...+ clean_cf_lock_files
+ rm -f /var/rudder/cfengine-community/state/cf_lock.lmdb
+ rm -f /var/rudder/cfengine-community/state/cf_lock.lmdb.lock

lock is 10 times bigger than the maximum size !

Related issues 2 (0 open — 2 closed)

Related to Rudder - User story #8438: Log check-rudder-agent cron job outputReleasedAlexis MoussetActions
Related to Rudder - Bug #10856: Cron service is not correctly managed by technique commonResolvedActions
Actions
Copy link
 #1

Updated by François ARMAND over 7 years ago

  • Translation missing: en.field_tag_list set to Sponsored
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 61

We at least need more log in rudder-agent to try to understand what is happening.

Actions
Copy link
 #2

Updated by Benoît PECCATTE over 7 years ago

Actions
Copy link
 #3

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from New to Rejected

We cannot reproduce, with #8438 we should have more info next time.
Feel free to reopen if you have more information.

Actions
Copy link
 #4

Updated by Nicolas CHARLES over 7 years ago

  • Related to Bug #10856: Cron service is not correctly managed by technique common added
Actions
Copy link
 #5

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from Rejected to New

Reopening, we found the bug

Actions
Copy link
 #6

Updated by Benoît PECCATTE over 7 years ago

This is because the check is set -e, if the check fails (for example when restarting cfengine), it stops.

Actions
Copy link
 #7

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from New to In progress
  • Assignee set to Benoît PECCATTE
Actions
Copy link
 #8

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1353
Actions
Copy link
 #9

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #10

Updated by Alexis Mousset over 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.21 which was released today.

Actions
Copy link
 #11

Updated by Alexis Mousset over 2 years ago

  • Priority changed from 61 to 0
Actions
Copy link

Also available in: Atom PDF