Syscheck error with leaky bucket cache file
GOAL:
Found issue during a syscheck on MP on 5.0.0-50.21.0:
ERROR: Syscheck::LBucket::getBucketFilehandle()
ERROR: Failed locking leaky bucket cache file
ERROR: FILE: /var/TKLC/log/syscheck/hardware_temp.cache
ERROR: SYS ERR: Resource temporarily unavailable
One or more module in class "hardware" FAILED
* temp: FAILURE:: MINOR::5000000000040000 -- Platform Health Check Failure
* temp: FAILURE:: The hardware temp cache bucket was locked.
* temp: FAILURE:: MINOR::5000000000040000 -- Platform Health Check Failure
* temp: FAILURE:: ...skipping test.
ERROR: Syscheck::LBucket::getBucketFilehandle()
ERROR: Failed locking leaky bucket cache file
ERROR: FILE: /var/TKLC/log/syscheck/hardware_temp.cache
ERROR: SYS ERR: Resource temporarily unavailable
One or more module in class "hardware" FAILED
* temp: FAILURE:: MINOR::5000000000040000 -- Platform Health Check Failure
* temp: FAILURE:: The hardware temp cache bucket was locked.
* temp: FAILURE:: MINOR::5000000000040000 -- Platform Health Check Failure
* temp: FAILURE:: ...skipping test.
Solution:
The error message seen is related to a race condition that can occur when syscheck is
run manually and repeatedly which can conflict with the existing syscheck daemon that is running
on the system all the time.
This race condition can occur with the following files.
/var/TKLC/log/syscheck/hardware_fan.cache
/var/TKLC/log/syscheck/hardware_psu.cache
/var/TKLC/log/syscheck/hardware_temp.cache
You can also use "alarmMgr --alarmStatus" to see alarms on the system as this would not conflict with existing daemon. This is typically a temporary error.
run manually and repeatedly which can conflict with the existing syscheck daemon that is running
on the system all the time.
This race condition can occur with the following files.
/var/TKLC/log/syscheck/hardware_fan.cache
/var/TKLC/log/syscheck/hardware_psu.cache
/var/TKLC/log/syscheck/hardware_temp.cache
You can also use "alarmMgr --alarmStatus" to see alarms on the system as this would not conflict with existing daemon. This is typically a temporary error.