-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
monit errors in the logs "ERR memory_checker: [memory_checker] Failed to execute the command" #10088
Comments
nazariig
changed the title
[202111] monit errors in the logs "ERR memory_checker: [memory_checker] Failed to execute the command"
monit errors in the logs "ERR memory_checker: [memory_checker] Failed to execute the command"
May 10, 2022
What is the severity of this issue? Does it have any impact other than syslog ERR message? |
1 task
yozhao101
added a commit
that referenced
this issue
Jun 17, 2022
…t created (#11129) Signed-off-by: Yong Zhao yozhao@microsoft.com Why I did it This PR aims to fix an issue (#10088) by enhancing the script memory_checker. Specifically, if container is not created successfully during device is booted/rebooted, then memory_checker do not need check its memory usage. How I did it In the script memory_checker, a function is added to get names of running containers. If the specified container name is not in current running container list, then this script will exit without checking its memory usage. How to verify it I tested on a lab device by following the steps: Stops telemetry container with command sudo systemctl stop telemetry.service Removes telemetry container with command docker rm telemetry Checks whether the script memory_checker ran by Monit will generate the syslog message saying it will exit without checking memory usage of telemetry.
yxieca
pushed a commit
that referenced
this issue
Jun 19, 2022
…t created (#11129) Signed-off-by: Yong Zhao yozhao@microsoft.com Why I did it This PR aims to fix an issue (#10088) by enhancing the script memory_checker. Specifically, if container is not created successfully during device is booted/rebooted, then memory_checker do not need check its memory usage. How I did it In the script memory_checker, a function is added to get names of running containers. If the specified container name is not in current running container list, then this script will exit without checking its memory usage. How to verify it I tested on a lab device by following the steps: Stops telemetry container with command sudo systemctl stop telemetry.service Removes telemetry container with command docker rm telemetry Checks whether the script memory_checker ran by Monit will generate the syslog message saying it will exit without checking memory usage of telemetry.
qiluo-msft
pushed a commit
that referenced
this issue
Jul 5, 2022
…t created (#11129) Signed-off-by: Yong Zhao yozhao@microsoft.com Why I did it This PR aims to fix an issue (#10088) by enhancing the script memory_checker. Specifically, if container is not created successfully during device is booted/rebooted, then memory_checker do not need check its memory usage. How I did it In the script memory_checker, a function is added to get names of running containers. If the specified container name is not in current running container list, then this script will exit without checking its memory usage. How to verify it I tested on a lab device by following the steps: Stops telemetry container with command sudo systemctl stop telemetry.service Removes telemetry container with command docker rm telemetry Checks whether the script memory_checker ran by Monit will generate the syslog message saying it will exit without checking memory usage of telemetry.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The issue is caused by a missing
telemetry
container.The situation may take place on a system start when
docker
container is not created yet.The root cause is
monit
async service health state check.Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
No error messages are expected when docker doesn't exist
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
Monit summary:
Monit configuration:
Monit memory checker:
The text was updated successfully, but these errors were encountered: