check-rudder-agent doesn't purge the lmdb file when run via cron
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 !
#8 Updated by Benoît PECCATTE 9 months 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
#9 Updated by Benoît PECCATTE 9 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|157035bd2e2fd54f0fbbe9cecb2316e86854f0d9.