You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Very rarely, during config reload or reboot, below error is observed:
ERR memory_checker: [memory_checker] cgroup memory usage file '/sys/fs/cgroup/memory/docker/3d4452045e8e85223825a45a913eb9ae041494be5702fa5b4c9059cd7d0b8b0b/memory.usage_in_bytes' of container '3d4452045e8e85223825a45a913eb9ae041494be5702fa5b4c9059cd7d0b8b0b' does not exist on device! Exiting ...
It happens on shutdown and it is not harmful in any way except just error in syslog.
It looks like race condition between memory_checker and docker shutdown flow.
memory_checker is running periodically and checks memory usage.
It checks memory for containers using this file '/sys/fs/cgroup/memory/docker/.../memory.usage_in_bytes'.
It could happen that container is already down which means 'memory.usage_in_bytes' file does not exist anymore.
But memory_checker was executed in parallel so it didn't know yet container is down, so still checked the file and printed an error that there is no such file.
Steps to reproduce the issue:
Execute config reload or reboot (please note, as mentioned above reproduce rate is low)
Describe the results you received:
Very rarely, during config reload or reboot, below error is observed:
ERR memory_checker: [memory_checker] cgroup memory usage file '/sys/fs/cgroup/memory/docker/3d4452045e8e85223825a45a913eb9ae041494be5702fa5b4c9059cd7d0b8b0b/memory.usage_in_bytes' of container '3d4452045e8e85223825a45a913eb9ae041494be5702fa5b4c9059cd7d0b8b0b' does not exist on device! Exiting ...
Describe the results you expected:
No memory_checker related error during config reload and reboot.
The text was updated successfully, but these errors were encountered:
Description
Very rarely, during config reload or reboot, below error is observed:
It happens on shutdown and it is not harmful in any way except just error in syslog.
It looks like race condition between memory_checker and docker shutdown flow.
memory_checker is running periodically and checks memory usage.
It checks memory for containers using this file '/sys/fs/cgroup/memory/docker/.../memory.usage_in_bytes'.
It could happen that container is already down which means 'memory.usage_in_bytes' file does not exist anymore.
But memory_checker was executed in parallel so it didn't know yet container is down, so still checked the file and printed an error that there is no such file.
Steps to reproduce the issue:
Describe the results you received:
Very rarely, during config reload or reboot, below error is observed:
Describe the results you expected:
No memory_checker related error during config reload and reboot.
The text was updated successfully, but these errors were encountered: