Issuing the command 'qvm-run --user=user some-dom kill -9 some-pid' on dom0 returns a message...

11 views
Skip to first unread message

Boryeu Mao

unread,
Jul 21, 2023, 8:44:29 PM7/21/23
to qubes-users
of ``some-dom: command failed with code: 137``, which I have been ignoring since the job with ``some-pid`` did get killed.  What could be the meaning of the code 137 and its significance?

Thanks in advance.

Rusty Bird

unread,
Jul 22, 2023, 9:55:10 AM7/22/23
to Boryeu Mao, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Boryeu Mao:
> of ``some-dom: command failed with code: 137``, which I have been ignoring
> since the job with ``some-pid`` did get killed. What could be the meaning
> of the code 137 and its significance?

137 == 128 + (signal) 9
https://www.gnu.org/software/bash/manual/bash.html#Exit-Status

If you add --pass-io to the failing qvm-run invocation, it will show
any error messages from the VM.

Rusty
-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEhLWbz8YrEp/hsG0ERp149HqvKt8FAmS73iJfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg0
QjU5QkNGQzYyQjEyOUZFMUIwNkQwNDQ2OUQ3OEY0N0FBRjJBREYACgkQRp149Hqv
Kt9q+g/+NY/PHFREA0xHudV3Ldr7/Qbl3ISrFS75c2hTpZFLGb8TwYx8PF9V2kwV
p38vtXrFfwfN77auPKchQMjNRxdaz8JI4HZzW9I82ovu7J6tHJHgJsKYe9vVMLD5
EnecANWtDs/RSqKL0M6IdfpAADOdkw5EyTr/9fu44ckZZ+TYt0ZbMoN9UUk1LfGH
6a2l27k24Cmgfq6dSeAMl9fAfbNPA5webFDniSY5GJmD7k25wA+Y0/xWZ/A4w8RP
et2oh67nRdGXBplvZtX/F+J+WMUZZU3AXlwp2ml6Rm5RS19a8FLsGTxa0o8r1eaJ
j+d+Ns8DoHwuHdePgHg8eOmbdm8TdUL2wshqPhRt72fNqK1RBEHWfBQJhbfWNor6
eT18+UhuaoLInuF2A3oRh1SDBi2Y3MAELpcldIBsMsA17E9QNph6pU0XkMsuVqgm
niDCY1Tr8AkCGuflgKegeN0GmP1VI6XNz0u/SilrSC+HfEgvcAYdsG721r4t5N1k
osoeRRllOmQJwFtNG3I0NAtSTW8gGsq2uCiDpWcCDnkhHPn+UXI5B0aXNlYia0/+
Sm4MOXN9lNG0JM3DKHa7QyWt8/AnwMkx2vMhT1z6cHp/5PcV3+40WcNaOhwvZLTb
G0DAjmeyn6X8UFwsrvlEejSwlRq/799p186wusAoqgXdjgHnwv4=
=63wE
-----END PGP SIGNATURE-----

Boryeu Mao

unread,
Jul 22, 2023, 2:33:00 PM7/22/23
to Boryeu Mao, qubes-users
Thanks for the info.  With --pass-io no error messages were returned from qvm-run and kill.  I am now inclined to think that the process (being one from command firefox-esr running on some-dom) returns a exit code of 9 when kill'ed with SIGKILL, which is caught by qvm-run, which issues the message some-dom: command failed with code: 137When SIGTERM is used to kill the process, the code 143 (128+15) is returned instead of 137.
Reply all
Reply to author
Forward
0 new messages