CTRL+C about mqtt2sql HOT 7 CLOSED

which version, which OS
pls provide output using --verbose and/or --debug

from mqtt2sql.

Hi, is a debian 8 lastest version 1.5.0022

Output:

^CDEBUG:__main__:Sending CONNECT (u1, p1, wr0, wq0, wf0, c1, k60) client_id=mqtt2sql.py-4116
DEBUG:__main__:Received CONNACK (0, 0)
DEBUG:__main__:Sending SUBSCRIBE (d0, m3) [('#', 0)]
DEBUG:__main__:Received SUBACK
DEBUG:__main__:Received PUBLISH (d0, q0, r1, m0), 'tele/SONOFF_ICT/LWT', ...  (6 bytes)
DEBUG:__main__:Received PUBLISH (d0, q0, r1, m0), 'cmnd/SONOFF_ICT/POWER', ...  (3 bytes)

from mqtt2sql.

That's currently a restriction of the mqtt library loop() function

Workaround is to kill the PID which runs the process (e.g. kill -9 $(pgrep -f "python.*mqtt2sql.py")) or using the suggested systemd daemon

from mqtt2sql.

ok thank you!

from mqtt2sql.

I used kill9 as well, but isnt posible to catch the break and call sys.exit(0) inside python?

from mqtt2sql.

btw systemd restart is hanging for me as well, I have to force kill also at systemd

from mqtt2sql.

I used kill9 as well, but isnt posible to catch the break and call sys.exit(0) inside python?

catch KILL and TERMINATE signal already in, sys.exit(0) is not enough, mqtt2sql uses multithreading for SQL

btw systemd restart is hanging for me as well, I have to force kill also at systemd

should all be fixed using latest version (v2.1.0031) - I rewrote also thread handling on exit

from mqtt2sql.