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

Also available in: Atom PDF