Bug 7679 - Traceback when trying to kill vsmagent
Summary: Traceback when trying to kill vsmagent
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Agent (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-12 13:24 CEST by Frida Flodin
Modified: 2021-06-08 13:21 CEST (History)
0 users

See Also:
Acceptance Criteria:


Attachments

Description Frida Flodin cendio 2021-04-12 13:24:12 CEST
Ran 4.12.1 server on SUSE 12 and got this traceback when trying to kill
a vsmagent that was running. The issue could be that systemctl had
cleaned the pidfile. Whatever caused it, we don't want a traceback.

What I did to reproduce: 
1. Stop any running vsmagent
>     systemctl stop vsmagent
2. Start vsmagent manually: 
>     /opt/thinlinc/sbin/vsmagent
3. Try to restart, it will fail
>     systemctl restart vsmagent.service
4. Try to kill
>     kill <pid>
5. Kill hard
>     kill -9 <pid>
6. Check log


> Unhandled exception on fd 3: <type 'exceptions.OSError'> [Errno 2] No such file or directory: '/var/run/vsmagent.pid' Traceback (most recent call last):
>   File "/opt/thinlinc/modules/thinlinc/vsm/async.py", line 103, in i1Iii
>     obj . handle_read_event ( fd )
>   File "/opt/thinlinc/modules/thinlinc/vsm/async.py", line 552, in handle_read_event
>     self . handle_control_pipe ( )
>   File "/opt/thinlinc/modules/thinlinc/vsm/async.py", line 584, in handle_control_pipe
>     self . control_commands [ IiI11i1IIiiI ] ( IiI11i1IIiiI )
>   File "/opt/thinlinc/modules/thinlinc/vsm/vsmagent.py", line 249, in terminate
>     os . unlink ( self . pidfile )
> OSError: [Errno 2] No such file or directory: '/var/run/vsmagent.pid'
> 
> 2021-04-12 12:46:06 INFO vsmagent: Got SIGTERM, signaling process to quit
> 2021-04-12 12:46:06 INFO vsmagent: Terminating. Have a nice day!

Note You need to log in before you can comment on or make changes to this bug.