qubesd doesn't stop on SIGTERM #9429
Labels
affects-4.3
This issue affects Qubes OS 4.3.
C: core
diagnosed
Technical diagnosis has been performed (see issue comments).
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
pr submitted
A pull request has been submitted for this issue.
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Comments
marmarek
added
T: bug
andrewdavidwong
added
diagnosed
fepitre
pushed a commit
to fepitre/qubes-core-qrexec
that referenced
this issue
Sep 4, 2024
Previously, if a service with exit-on-client-eof=true received EOF on stdin while stdout was still open, no EOF would be sent on stdout. This is a (currently harmless) violation of the qrexec protocol. Fix this by sending an empty MSG_DATA_STDOUT to indicate EOF on stdout. Fixes: QubesOS/qubes-issues#9429
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to file a helpful issue
Qubes OS release
R4.3
Brief summary
When sending SIGTERM to qubesd, it doesn't stop. Sending a second SIGTERM does stop it, but not cleanly (
RuntimeError: Event loop stopped before Future completed).Steps to reproduce
systemctl stop qubesdor send SIGTERM to qubesd manuallyExpected behavior
It stops cleanly
Actual behavior
It appears to do some cleanup, at least strace says it stops listening on sockets and unlinks them. But the process doesn't terminate.
When stopping qubesd service via systemd, it will get SIGABRT after a timeout and it will terminate then. This also delays system shutdown.
I guess it may be related to update from Python 3.11 to 3.13.
The text was updated successfully, but these errors were encountered: