search

blumzi / LAST_next_generation

Design and implementation of a new LAST architecture
GNU General Public License v3.0
0 stars 0 forks source link

How to terminate `last-unit-server` #19

Closed EastEriq closed 5 months ago

EastEriq commented 5 months ago

Revival of #6, in a new issue since things have evolved in the meantime This is the process tree of the server launched from shell with ~/python/LAST_next_generation/bin/last-unit-server start

image

In another shell I now call ~/python/LAST_next_generation/bin/last-unit-server stop. The stdout log of the first reports quitting the various subprocesses and finally

INFO:     Application shutdown complete.
INFO:     Finished server process [134424]

but the top python process doesn't quit: image I have to Ctrl-C to complete. What is missing for python to end? I'm reporting it because I presume that it needs to be fixed in order to make a system service of it.

Btw, this time after Ctrl-C I get

^CException ignored in: <module 'threading' from '/usr/lib/python3.8/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.8/threading.py", line 1388, in _shutdown
    lock.acquire()
KeyboardInterrupt:

I don't remember if I saw messages like that other times.

blumzi commented 5 months ago

Fixed. No need to kill stuff, it dies by itself :-)