-
Notifications
You must be signed in to change notification settings - Fork 128
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
podman with systemd+healthcheck results conmon error #438
Comments
change the write_sync_fd function to handle broken pipes. When a broken pipe is detected, the file descriptor is closed and conmon continues gracefully instead of exiting. Closes: containers#438 Signed-off-by: Giuseppe Scrivano <[email protected]>
change the write_sync_fd function to handle broken pipes. When a broken pipe is detected, the file descriptor is closed and conmon continues gracefully instead of exiting. Closes: containers#438 Signed-off-by: Giuseppe Scrivano <[email protected]>
I think it is better to handle it in conmon and not fail when the sync pipe is broken: #439 That could happen because Podman exited earlier |
change the write_sync_fd function to handle broken pipes. When a broken pipe is detected, the file descriptor is closed and conmon continues gracefully instead of exiting. Closes: #438 Signed-off-by: Giuseppe Scrivano <[email protected]>
Hello @flyingfishflash You comment apparently got a fix. it also affected me, so I turned into issue as requested in your question. |
Hey thank you for transferring to issues from discussion, and the subsequent fix! |
containers/podman#19426 (comment) I've posted in the discussion above, but there was no reply. My journal gets filled with |
That seems like a separate issue; please file a fresh bug report. |
I'm having the same issue. Please link to the bug report you open on it from here so people can find it when googling. |
Here you go: #454 |
conmon 402de34b31388b5a2e1c <error>: Unable to send container stderr message to parent Broken pipe containers/conmon#438
conmon 402de34b31388b5a2e1c <error>: Unable to send container stderr message to parent Broken pipe containers/conmon#438 (cherry picked from commit 6c84ff4)
As reported at containers/podman#19426 and asked for by @mheon, refilling this as a Podman issue.
This error happens when a container running by systemd - generated by
podman generate systemd --new
with healthcheck starts, leading to conman erros when healthcheck runs as the log above and the original discussion points.Infos:
Excerpt of
journalctl --boot=0 | grep -E '(conmon|podman)'
:podman info
:screenfetch -d 'distro;+cpu;+kernel;+gpu;+mem'
:Originally posted by @leleobhz in containers/podman#19426 (comment)
The text was updated successfully, but these errors were encountered: