Forum Domoticz en français

Bonjour,

Je viens de réaliser une nouvelle installation de domoticz et du plugin sur raspberry pi,
malheureusement lors du démarrage du plugin celui-ci fait crasher domoticz. (Error: Domoticz(pid:3795, tid:5243('Zigate')) received fatal signal 11 (Segmentation fault))

Voici les infos :

Version Domoticz / Python

Code : Tout sélectionner

Version: 2023.1
Build Hash: f9b9ac774
Compile Date: 2023-02-14 15:06:40
dzVents Version: 3.1.8
Python Version: 3.9.2 (default, Mar 12 2021, 04:06:34) [GCC 10.2.1 20210110]

Système sur lequel tourne DomoticZ avec le plugin
Raspberry PI 2 Model B Rev 1.1 (raspbian Bullseye)

Modèle de coordinateur / Version de coordinateur
PiZigate+

Version du plugin / Branche du plugin
Stable6

Config du plugin

: config plugin; r9OV0t.png (237.85 Kio) Consulté 768 fois

Voici les logs domoticz du crash lors du démarrage

Code : Tout sélectionner

2023-05-10 11:41:42.609 Zigate: Worker thread started.
2023-05-10 11:41:42.609 Status: Zigate: Entering work loop.
2023-05-10 11:41:42.609 Status: Zigate: Started.
2023-05-10 11:41:52.206 Status: Zigate: Initialized version 6.3, author 'pipiche38'
2023-05-10 11:41:52.211 Status: Zigate: Zigbee for Domoticz plugin started!
2023-05-10 11:41:52.211 Status: Zigate: Python3 requires 3.8 or above and you are running 3.9
2023-05-10 11:41:52.212 Status: Zigate: Checking Python modules /home/pi/domoticz/plugins/Domoticz-Zigbee/requirements.txt
2023-05-10 11:41:54.431 Status: Zigate: Checking Python modules /home/pi/domoticz/plugins/Domoticz-Zigbee/requirements.txt
2023-05-10 11:41:55.912 Zigate: Set PiZigate Channels 11 and 17
2023-05-10 11:41:55.913 Zigate: + GPIO(RUN) OK
2023-05-10 11:41:55.913 Zigate: + GPIO(FLASH) OK
2023-05-10 11:41:55.630 Status: Zigate: DeviceConf loaded - 439 confs loaded
2023-05-10 11:41:55.633 Status: Zigate: load ListOfDevice
2023-05-10 11:41:55.671 Status: Zigate: Transport mode: V2-PI
2023-05-10 11:41:55.913 Status: Zigate: Switch PiZigate in RUN mode
2023-05-10 11:41:55.902 Error: Zigate: switchPiZigate_mode - unable to find distribution: Assuming debian, Error: module 'platform' has no attribute 'dist'
2023-05-10 11:41:56.430 Status: Zigate: ZigateTransport: Serial Connection open: Serial<id=0x69933b50, open=True>(port='/dev/serial0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=None, xonxoff=False, rtscts=False, dsrdtr=False)
2023-05-10 11:41:56.440 Status: Zigate: ZigateTransport: writer_thread Thread start.
2023-05-10 11:41:56.454 Status: Zigate: ZigateTransport: thread_processing_and_sending Thread start.
2023-05-10 11:41:56.465 Status: Zigate: Start Web Server connection
2023-05-10 11:41:56.588 Status: Zigate: Web backend for Web User Interface started on port: 9440
2023-05-10 11:41:56.589 Status: Zigate: Domoticz Widgets usage is at 1.2 % (252 units free)
2023-05-10 11:42:05.173 Status: Zigate: ==> Transport Mode switch to full mode
2023-05-10 11:42:05.177 Status: Zigate: ZiGate+ (V2)
2023-05-10 11:42:05.178 Status: Zigate: Installer Version Number: 03a0
2023-05-10 11:42:05.179 Status: Zigate: Branch Version: ==> Production <==
2023-05-10 11:42:10.091 Status: Zigate: Erase coordinator PDM
2023-05-10 11:42:10.479 Status: Zigate: ZiGate PDM loaded
2023-05-10 11:42:10.485 Status: Zigate: 'Factory new' Restart status: STARTUP
2023-05-10 11:42:15.227 Status: Zigate: ZiGate+ (V2)
2023-05-10 11:42:15.229 Status: Zigate: Installer Version Number: 03a0
2023-05-10 11:42:15.231 Status: Zigate: Branch Version: ==> Production <==
2023-05-10 11:42:25.110 Status: Zigate: ZigateConf - Setting extPANID : 0x0000000000000000
2023-05-10 11:42:25.113 Status: Zigate: ZigateConf setting Channel(s) to: 0
2023-05-10 11:42:25.136 Status: Zigate: setChannel - Channel set to : 00000000
2023-05-10 11:42:25.141 Status: Zigate: Force ZiGate to Normal mode
2023-05-10 11:42:25.144 Status: Zigate: Start network
2023-05-10 11:42:25.145 Status: Zigate: Set Zigate as a TimeServer
2023-05-10 11:42:29.996 Status: Zigate: Accepting new Hardware: Disable (Off)
2023-05-10 11:42:30.126 Error: Zigate: Coordinator not correctly initialized
2023-05-10 11:42:30.235 Error: Zigate: Coordinator not correctly initialized
2023-05-10 11:42:34.268 Zigate: Decode8024: Status: 01
2023-05-10 11:42:34.268 Status: Zigate: Updating Channel in Plugin Configuration from: 0 to: 12
2023-05-10 11:42:34.278 Status: Zigate: Start Network - Formed new network
2023-05-10 11:42:34.281 Status: Zigate: Coordinator details IEEE: 00158d000966ccdb, NetworkID: 0000, Channel: 12, Status: 01: Success
2023-05-10 11:42:35.115 Status: Zigate: Request Disabling Accepting new Hardware
2023-05-10 11:42:35.739 Status: Zigate: Accepting new Hardware: Disable (Off)
2023-05-10 11:42:40.083 Zigate: URL INFOS {'type': 'command', 'param': 'updatehardware', 'htype': '94', 'idx': 4, 'name': 'Zigate', 'address': '0.0.0.0', 'port': '9999', 'serialport': '/dev/serial0', 'Mode1': 'V2', 'Mode2': 'PI', 'Mode3': 'False', 'Mode4': '9440', 'Mode5': 'http://127.0.0.1:8080', 'Mode6': '2', 'extra': 'Zigate', 'enabled': 'true', 'datatimeout': '0', 'loglevel': 7}
2023-05-10 11:42:40.872 Zigate: onStop()
2023-05-10 11:42:40.886 Zigate: Connection closed
2023-05-10 11:42:40.085 Status: Zigate: Plugin Restart command : http://127.0.0.1:8080/json.htm?type=command&param=updatehardware&htype=94&idx=4&name=Zigate&address=0.0.0.0&port=9999&serialport=%2Fdev%2Fserial0&Mode1=V2&Mode2=PI&Mode3=False&Mode4=9440&Mode5=http%3A%2F%2F127.0.0.1%3A8080&Mode6=2&extra=Zigate&enabled=true&datatimeout=0&loglevel=7
2023-05-10 11:42:40.115 Status: Zigate: coordinator set to Certification : 1/CE -> CE
2023-05-10 11:42:40.179 Status: Zigate: Stop directive received.
2023-05-10 11:42:40.868 Status: Zigate: ota_scan_folder Following Firmware have been loaded
2023-05-10 11:42:40.872 Status: Zigate: Plugin with Zigate+, firmware 03a0 correctly initialized
2023-05-10 11:42:40.909 Status: Zigate: ZigateTransport: ZiGateSerialListen Thread stop.
2023-05-10 11:42:40.911 Status: Zigate: ZigateTransport: writer_thread Thread stop.
2023-05-10 11:42:40.913 Status: Zigate: ZigateTransport: thread_processing_and_sending Thread stop.
2023-05-10 11:42:41.912 Zigate: logging_thread - ended
2023-05-10 11:42:41.915 Zigate: Logging Thread shutdown
2023-05-10 11:42:41.915 Zigate: onStop called (6) Close Logging Management
2023-05-10 11:42:41.900 Status: Zigate: Statistics on message
2023-05-10 11:42:41.901 Status: Zigate: PDM load(s) : 1
2023-05-10 11:42:41.901 Status: Zigate: ZiGate reacting time
2023-05-10 11:42:41.901 Status: Zigate: Max : 0 sec
2023-05-10 11:42:41.901 Status: Zigate: Average : 0 sec
2023-05-10 11:42:41.901 Status: Zigate: ZiGate processing time on Rx
2023-05-10 11:42:41.901 Status: Zigate: Max : 0 sec
2023-05-10 11:42:41.901 Status: Zigate: Average : 0 sec
2023-05-10 11:42:41.901 Status: Zigate: Sent:
2023-05-10 11:42:41.901 Status: Zigate: TX commands : 20
2023-05-10 11:42:41.901 Status: Zigate: Max Load (Queue) : 6
2023-05-10 11:42:41.901 Status: Zigate: Max aPDU (Queue) : 0
2023-05-10 11:42:41.901 Status: Zigate: Max nPDU (Queue) : 1
2023-05-10 11:42:41.902 Status: Zigate: TX failed : 0 (0.0%)
2023-05-10 11:42:41.902 Status: Zigate: TX timeout : 0 (0.0%)
2023-05-10 11:42:41.902 Status: Zigate: TX data timeout : 0 (0.0%)
2023-05-10 11:42:41.902 Status: Zigate: TX reTransmit : 0 (0.0%)
2023-05-10 11:42:41.902 Status: Zigate: TX APS Failure : 0 (0.0%)
2023-05-10 11:42:41.902 Status: Zigate: TX APS Ack : 0 (0.0%)
2023-05-10 11:42:41.902 Status: Zigate: TX APS Nck : 0 (0.0%)
2023-05-10 11:42:41.902 Status: Zigate: Received:
2023-05-10 11:42:41.902 Status: Zigate: RX frame : 33
2023-05-10 11:42:41.903 Status: Zigate: RX crc errors : 0 (0.0%)
2023-05-10 11:42:41.903 Status: Zigate: RX lentgh errors : 0 (0.0%)
2023-05-10 11:42:41.903 Status: Zigate: RX clusters : 0
2023-05-10 11:42:41.903 Status: Zigate: RX clusters KO : 0
2023-05-10 11:42:41.903 Status: Zigate: Operating time : 0 Hours 0 Mins 46 Secs
2023-05-10 11:42:42.282 Zigate: Worker thread started.
2023-05-10 11:42:42.236 Status: Zigate: Exiting work loop.
2023-05-10 11:42:42.281 Status: Zigate: Stopping threads.
2023-05-10 11:42:42.281 Status: Zigate: Stopped.
2023-05-10 11:42:42.282 Status: Zigate: Entering work loop.
2023-05-10 11:42:42.282 Status: Zigate: Started.
2023-05-10 11:42:46.695 Status: Zigate: Initialized version 6.3, author 'pipiche38'
2023-05-10 11:42:46.696 Error: Domoticz(pid:3795, tid:5243('Zigate')) received fatal signal 11 (Segmentation fault)
2023-05-10 11:42:46.696 Error: siginfo address=0xed3, address=(nil)

Log du plugin

Code : Tout sélectionner

2023-05-10 11:41:54,761 INFO    : [  MainThread 5182] Zigbee for Domoticz (z4d) plugin stable6-6.3.012 started
2023-05-10 11:41:54,838 INFO    : [  MainThread 5182] Plugin Database: DeviceList-4.txt
2023-05-10 11:41:54,851 INFO    : [  MainThread 5182] DeviceConf loaded - 17 confs loaded
2023-05-10 11:41:55,627 INFO    : [  MainThread 5182] DeviceConf loaded - 439 confs loaded
2023-05-10 11:41:55,631 INFO    : [  MainThread 5182] load ListOfDevice
2023-05-10 11:41:55,636 INFO    : [  MainThread 5182] Transport mode: V2-PI
2023-05-10 11:41:56,425 INFO    : [  MainThread 5182] ZigateTransport: Serial Connection open: Serial<id=0x69933b50, open=True>(port='/dev/serial0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=None, xonxoff=False, rtsct>
2023-05-10 11:41:56,437 INFO    : [ZiGateWriter_4 5197] ZigateTransport: writer_thread Thread start.
2023-05-10 11:41:56,452 INFO    : [ZiGateForwarder_4 5198] ZigateTransport: thread_processing_and_sending Thread start.
2023-05-10 11:41:56,456 INFO    : [  MainThread 5182] Connection open: Serial<id=0x69933b50, open=True>(port='/dev/serial0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=None, xonxoff=False, rtscts=False, dsrdtr=False)
2023-05-10 11:41:56,459 INFO    : [  MainThread 5182] Start Web Server connection
2023-05-10 11:41:56,586 INFO    : [  MainThread 5182] Web backend for Web User Interface started on port: 9440
2023-05-10 11:41:56,589 INFO    : [  MainThread 5182] Domoticz Widgets usage is at 1.2 % (252 units free)
2023-05-10 11:42:05,172 INFO    : [ZiGateSerial_4 5196] ==> Transport Mode switch to full mode
2023-05-10 11:42:05,177 INFO    : [ZiGateForwarder_4 5198] ZiGate+ (V2)
2023-05-10 11:42:05,178 INFO    : [ZiGateForwarder_4 5198] Installer Version Number: 03a0
2023-05-10 11:42:05,179 INFO    : [ZiGateForwarder_4 5198] Branch Version: ==> Production <==
2023-05-10 11:42:10,089 INFO    : [  MainThread 5182] Erase coordinator PDM
2023-05-10 11:42:10,475 INFO    : [ZiGateSerial_4 5196] ZiGate PDM loaded
2023-05-10 11:42:10,484 INFO    : [ZiGateForwarder_4 5198] 'Factory new' Restart status: STARTUP
2023-05-10 11:42:15,218 INFO    : [ZiGateForwarder_4 5198] ZiGate+ (V2)
2023-05-10 11:42:15,228 INFO    : [ZiGateForwarder_4 5198] Installer Version Number: 03a0
2023-05-10 11:42:15,230 INFO    : [ZiGateForwarder_4 5198] Branch Version: ==> Production <==
2023-05-10 11:42:25,106 INFO    : [  MainThread 5182] ZigateConf - Setting extPANID : 0x0000000000000000
2023-05-10 11:42:25,111 INFO    : [  MainThread 5182] ZigateConf setting Channel(s) to: 0
2023-05-10 11:42:25,114 INFO    : [  MainThread 5182] setChannel - Channel set to : 00000000
2023-05-10 11:42:25,140 INFO    : [  MainThread 5182] Force ZiGate to Normal mode
2023-05-10 11:42:25,143 INFO    : [  MainThread 5182] Start network
2023-05-10 11:42:25,145 INFO    : [  MainThread 5182] Set Zigate as a TimeServer
2023-05-10 11:42:26,312 INFO    : [ZiGateForwarder_4 5198] Start Network statusSuccess
2023-05-10 11:42:29,995 INFO    : [ZiGateForwarder_4 5198] Accepting new Hardware: Disable (Off)
2023-05-10 11:42:30,126 ERROR   : [ZiGateForwarder_4] Coordinator not correctly initialized
2023-05-10 11:42:30,235 ERROR   : [ZiGateForwarder_4] Coordinator not correctly initialized
2023-05-10 11:42:34,277 INFO    : [ZiGateForwarder_4 5198] Start Network - Formed new network
2023-05-10 11:42:34,280 INFO    : [ZiGateForwarder_4 5198] Coordinator details IEEE: 00158d000966ccdb, NetworkID: 0000, Channel: 12, Status: 01: Success
2023-05-10 11:42:35,109 INFO    : [  MainThread 5182] Request Disabling Accepting new Hardware
2023-05-10 11:42:35,738 INFO    : [ZiGateForwarder_4 5198] Accepting new Hardware: Disable (Off)
2023-05-10 11:42:40,111 INFO    : [  MainThread 5182] Switch Blue Led On
2023-05-10 11:42:40,114 INFO    : [  MainThread 5182] coordinator set to Certification : 1/CE -> CE
2023-05-10 11:42:40,867 INFO    : [  MainThread 5182] ota_scan_folder Following Firmware have been loaded
2023-05-10 11:42:40,870 INFO    : [  MainThread 5182] Plugin with Zigate+, firmware 03a0 correctly initialized
2023-05-10 11:42:40,874 INFO    : [  MainThread 5182] onDisconnect - Closing Name: 'Zigate Server Connection', Transport: 'TCP/IP', Protocol: 'HTTP', Address: '', Port: '9440', Baud: -1, Timeout: 0, Connected: False, Parent: 'None'
2023-05-10 11:42:40,878 INFO    : [  MainThread 5182] onStop called
2023-05-10 11:42:40,880 INFO    : [  MainThread 5182] onStop calling (1) domoticzDb DeviceStatus closed
2023-05-10 11:42:40,881 INFO    : [  MainThread 5182] onStop calling (3) Transport off
2023-05-10 11:42:40,882 INFO    : [  MainThread 5182] Request closing connection: Serial<id=0x69933b50, open=True>(port='/dev/serial0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=None, xonxoff=False, rtscts=False, dsrd>
2023-05-10 11:42:40,884 INFO    : [  MainThread 5182] -- shutdown reader thread
2023-05-10 11:42:40,885 INFO    : [  MainThread 5182] Flush and cancel_read
2023-05-10 11:42:40,888 INFO    : [  MainThread 5182] close connection
2023-05-10 11:42:40,908 INFO    : [ZiGateSerial_4 5196] ZigateTransport: ZiGateSerialListen Thread stop.
2023-05-10 11:42:40,910 INFO    : [ZiGateWriter_4 5197] ZigateTransport: writer_thread Thread stop.
2023-05-10 11:42:40,912 INFO    : [ZiGateForwarder_4 5198] ZigateTransport: thread_processing_and_sending Thread stop.
2023-05-10 11:42:41,892 INFO    : [  MainThread 5182] -- waiting for end of thread
2023-05-10 11:42:41,894 INFO    : [  MainThread 5182] waiting_for_end_thread - release semaphore
2023-05-10 11:42:41,897 INFO    : [  MainThread 5182] waiting_for_end_thread - wait for readThread
2023-05-10 11:42:41,899 INFO    : [  MainThread 5182] waiting_for_end_thread - readThread done
2023-05-10 11:42:41,904 INFO    : [  MainThread 5182] waiting_for_end_thread - wait for forwardedThread
2023-05-10 11:42:41,906 INFO    : [  MainThread 5182] waiting_for_end_thread - forwardedThread done
2023-05-10 11:42:41,910 INFO    : [  MainThread 5182] waiting_for_end_thread - writerThread done

Pour pouvoir ensuite redémarrer Domoticz sans qu'il crash je suis obligé de désactiver le hardware via cette commande :

Code : Tout sélectionner

sudo sqlite3 -header -list domoticz.db "UPDATE Hardware set Enabled = 0 WHERE ID = 4"

Je n'ai plus de solution, merci pour votre aide

Bonjour Max71 et bienvenu sur le forum

Tu as mis une image hébergée à l'extérieur du forum : il y a de fort risques qu'elles ne soient plus disponibles dans quelques temps comme ici, là ou encore là. Est-ce que tu peux éditer ton message et utiliser l'onglet Fichiers joints en dessous de la zone d'écriture des messages pour enregistrer les éléments sur le serveur du forum. Merci

Le plugin se lance correctement et ça plante après. Je ne sais pas si le firmware 3.A0 a été testé sur la ZiGate+.
Attends le retour de Pipiche.

est-ce systématique ?

peut-on avoir les fichiers de logs en pièces jointes

as-tu regarder les logs systèmes ? qui pourrait par exemple expliquer pourquoi le plugin est arreté, car c'est ce qu'il se passe d'après log. As-tu configuré un espace de SWAP , car j'ai vu que c'est un PI2 et pas beaucoup de memoire.

Bonjour,
Oui c'est systématique,

je viens de réactiver le plugin et j'ai directement ca :

Code : Tout sélectionner

2023-05-10 14:06:29.855 Status: Zigate: Entering work loop.
2023-05-10 14:06:29.855 Status: Zigate: Started.
2023-05-10 14:06:34.326 Status: Zigate: Initialized version 6.3, author 'pipiche38'
2023-05-10 14:06:34.327 Error: Domoticz(pid:5328, tid:13255('Zigate')) received fatal signal 11 (Segmentation fault)
2023-05-10 14:06:34.327 Error: siginfo address=0x14d0, address=(nil)

Pour les logs domoticz je les copie depuis la fenêtre domoticz, ca me les affiche avant de crasher.

Pour les logs du plugin les voici en pj

logs.zip: logs plugin; (1.82 Kio) Téléchargé 75 fois

Pour les syslog je ne vois rien de probant dedans.

Pour le SWAP, il y a 100 Mo, mais la ram est peu utilisée de ce que je vois.

Donc désolé, mais j'ai peur de pas pouvoir aider. C'est Domoticz qui décide de tuer le plugin, il faudrait pouvoir faire une analyse du dump, mais ca c'est pas de ma compétence.
Donc si il y a quelqu'un qui sait faire ca ... faudrait mettre ici à disposition la stack du crash domoticz

Tu me suggère de déposer ici le fichier domoticz_crash.log ?

Voici le contenu fichier :

Code : Tout sélectionner

gdb: warning: Couldn't determine a path for the index cache directory.
[New LWP 13434]
[New LWP 13435]
[New LWP 13436]
[New LWP 13437]
[New LWP 13438]
[New LWP 13439]
[New LWP 13440]
[New LWP 13441]
[New LWP 13442]
[New LWP 13443]
[New LWP 13444]
[New LWP 13445]
[New LWP 13448]
[New LWP 13449]
[New LWP 13450]
[New LWP 13451]
[New LWP 13452]
[New LWP 13502]
[New LWP 21268]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
0x7692df8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7eb79988, req@entry=0x7eb79980, rem=0x7eb79998, rem@entry=0x7eb79990) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
52	../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory.
  Id   Target Id                                       Frame 
* 1    Thread 0x75e33010 (LWP 13433) "domoticz"        0x7692df8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7eb79988, req@entry=0x7eb79980, rem=0x7eb79998, rem@entry=0x7eb79990) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
  2    Thread 0x75925220 (LWP 13434) "Watchdog"        0x7692df8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x75924b90, req@entry=0x75924b88, rem=0x75924ba0, rem@entry=0x75924b98) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
  3    Thread 0x75124220 (LWP 13435) "SQLHelper"       syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  4    Thread 0x74923220 (LWP 13436) "PluginMgr"       syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  5    Thread 0x73ab8220 (LWP 13437) "InfluxPush"      syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  6    Thread 0x732b7220 (LWP 13438) "Webem_ssncleane" 0x7696d63c in epoll_wait (epfd=13, events=0x732b6270, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
  7    Thread 0x72ab6220 (LWP 13439) "WebServer_8080"  0x7696d63c in epoll_wait (epfd=9, events=0x72ab5320, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
  8    Thread 0x720ff220 (LWP 13440) "Webem_ssncleane" 0x7696d63c in epoll_wait (epfd=20, events=0x720fe270, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
  9    Thread 0x718fe220 (LWP 13441) "WebServer_30443" 0x7696d63c in epoll_wait (epfd=16, events=0x718fd320, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
  10   Thread 0x70eff220 (LWP 13442) "Scheduler"       syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  11   Thread 0x706fe220 (LWP 13443) "TCPServer"       0x7696d63c in epoll_wait (epfd=23, events=0x706fd350, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
  12   Thread 0x6fcff220 (LWP 13444) "MainWorker"      syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  13   Thread 0x6f4fe220 (LWP 13445) "MainWorkerRxMsg" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6f4fdba0, clockid=<optimized out>, expected=0, futex_word=0xa6d030 <m_mainworker+4104>) at ../sysdeps/nptl/futex-internal.h:323
  14   Thread 0x6e0ff220 (LWP 13448) "Virtual Devices" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  15   Thread 0x6d6ff220 (LWP 13449) "NotificationSys" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6d6febd0, clockid=<optimized out>, expected=0, futex_word=0xa6ca84 <m_mainworker+2652>) at ../sysdeps/nptl/futex-internal.h:323
  16   Thread 0x6ccff220 (LWP 13450) "Plugin_ASIO"     futex_wait_cancelable (private=0, expected=0, futex_word=0x1daab70) at ../sysdeps/nptl/futex-internal.h:186
  17   Thread 0x6c4fe220 (LWP 13451) "EventSystem"     syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  18   Thread 0x6bcfd220 (LWP 13452) "EventSystemQueu" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6bcfcae0, clockid=<optimized out>, expected=0, futex_word=0xa6c180 <m_mainworker+344>) at ../sysdeps/nptl/futex-internal.h:323
  19   Thread 0x6eaff220 (LWP 13502) "WebServer_8080"  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  20   Thread 0x6b4fc220 (LWP 21268) "Zigate"          0x769344d4 in __GI___wait4 (pid=21273, stat_loc=0x6eb2c0f0, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27

Thread 20 (Thread 0x6b4fc220 (LWP 21268) "Zigate"):
#0  0x769344d4 in __GI___wait4 (pid=21273, stat_loc=0x6eb2c0f0, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#1  0x002868cc in dumpstack_gdb(bool) ()
#2  0x00286e98 in signal_handler(int, siginfo_t*, void*) ()
#3  <signal handler called>
#4  raise (sig=11) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  <signal handler called>
#6  0x75a2ef34 in PyDict_GetItem () from /lib/arm-linux-gnueabihf/libpython3.9.so
#7  0x0065fddc in Plugins::CPlugin::onDeviceModified(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int) ()
#8  0x0066e1ec in Plugins::onDeviceModifiedCallback::ProcessLocked(Plugins::CPlugin*) ()
#9  0x00210370 in Plugins::CPluginMessageBase::Process(Plugins::CPlugin*) ()
#10 0x0066c980 in Plugins::CPlugin::Do_Work() ()
#11 0x008db9cc in execute_native_thread_routine ()
#12 0x76aa9300 in start_thread (arg=0x6b4fc220) at pthread_create.c:477
#13 0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 19 (Thread 0x6eaff220 (LWP 13502) "WebServer_8080"):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x008b943c in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2  0x0070d1b4 in http::server::CWebsocketHandler::Do_Work() ()
#3  0x008db9cc in execute_native_thread_routine ()
#4  0x76aa9300 in start_thread (arg=0x6eaff220) at pthread_create.c:477
#5  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 18 (Thread 0x6bcfd220 (LWP 13452) "EventSystemQueu"):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6bcfcae0, clockid=<optimized out>, expected=0, futex_word=0xa6c180 <m_mainworker+344>) at ../sysdeps/nptl/futex-internal.h:323
#1  __pthread_cond_wait_common (abstime=0x6bcfcae0, clockid=<optimized out>, mutex=0xffffff, cond=0xa6c158 <m_mainworker+304>) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0xa6c158 <m_mainworker+304>, mutex=0xffffff, abstime=0x6bcfcae0) at pthread_cond_wait.c:656
#3  0x0020ac2c in CEventSystem::EventQueueThread() ()
#4  0x008db9cc in execute_native_thread_routine ()
#5  0x76aa9300 in start_thread (arg=0x6bcfd220) at pthread_create.c:477
#6  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 17 (Thread 0x6c4fe220 (LWP 13451) "EventSystem"):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x008b943c in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2  0x00201ba0 in CEventSystem::Do_Work() ()
#3  0x008db9cc in execute_native_thread_routine ()
#4  0x76aa9300 in start_thread (arg=0x6c4fe220) at pthread_create.c:477
#5  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 16 (Thread 0x6ccff220 (LWP 13450) "Plugin_ASIO"):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x1daab70) at ../sysdeps/nptl/futex-internal.h:186
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x0, cond=0x1daab48) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x1daab48, mutex=0x0) at pthread_cond_wait.c:638
#3  0x003ce52c in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#4  0x0066f904 in Plugins::BoostWorkers() ()
#5  0x00754c38 in thread_proxy ()
#6  0x76aa9300 in start_thread (arg=0x6ccff220) at pthread_create.c:477
#7  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 15 (Thread 0x6d6ff220 (LWP 13449) "NotificationSys"):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6d6febd0, clockid=<optimized out>, expected=0, futex_word=0xa6ca84 <m_mainworker+2652>) at ../sysdeps/nptl/futex-internal.h:323
#1  __pthread_cond_wait_common (abstime=0x6d6febd0, clockid=<optimized out>, mutex=0xffffff, cond=0xa6ca58 <m_mainworker+2608>) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0xa6ca58 <m_mainworker+2608>, mutex=0xffffff, abstime=0x6d6febd0) at pthread_cond_wait.c:656
#3  0x0026e198 in CNotificationSystem::QueueThread() ()
#4  0x008db9cc in execute_native_thread_routine ()
#5  0x76aa9300 in start_thread (arg=0x6d6ff220) at pthread_create.c:477
#6  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 14 (Thread 0x6e0ff220 (LWP 13448) "Virtual Devices"):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x008b943c in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2  0x00536938 in CHttpPoller::Do_Work() ()
#3  0x008db9cc in execute_native_thread_routine ()
#4  0x76aa9300 in start_thread (arg=0x6e0ff220) at pthread_create.c:477
#5  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 13 (Thread 0x6f4fe220 (LWP 13445) "MainWorkerRxMsg"):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6f4fdba0, clockid=<optimized out>, expected=0, futex_word=0xa6d030 <m_mainworker+4104>) at ../sysdeps/nptl/futex-internal.h:323
#1  __pthread_cond_wait_common (abstime=0x6f4fdba0, clockid=<optimized out>, mutex=0xffffff, cond=0xa6d008 <m_mainworker+4064>) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0xa6d008 <m_mainworker+4064>, mutex=0xffffff, abstime=0x6f4fdba0) at pthread_cond_wait.c:656
#3  0x0025c758 in MainWorker::Do_Work_On_Rx_Messages() ()
#4  0x008db9cc in execute_native_thread_routine ()
#5  0x76aa9300 in start_thread (arg=0x6f4fe220) at pthread_create.c:477
#6  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 12 (Thread 0x6fcff220 (LWP 13444) "MainWorker"):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x008b943c in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2  0x00258754 in MainWorker::Do_Work() ()
#3  0x008db9cc in execute_native_thread_routine ()
#4  0x76aa9300 in start_thread (arg=0x6fcff220) at pthread_create.c:477
#5  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 11 (Thread 0x706fe220 (LWP 13443) "TCPServer"):
#0  0x7696d63c in epoll_wait (epfd=23, events=0x706fd350, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x003cc8c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2  0x003ce444 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3  0x006c1768 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<tcp::server::CTCPServer::StartServer(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda()#1}> > >::_M_run() ()
#4  0x008db9cc in execute_native_thread_routine ()
#5  0x76aa9300 in start_thread (arg=0x706fe220) at pthread_create.c:477
#6  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 10 (Thread 0x70eff220 (LWP 13442) "Scheduler"):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x008b943c in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2  0x0027e5b0 in CScheduler::Do_Work() ()
#3  0x008db9cc in execute_native_thread_routine ()
#4  0x76aa9300 in start_thread (arg=0x70eff220) at pthread_create.c:477
#5  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 9 (Thread 0x718fe220 (LWP 13441) "WebServer_30443"):
#0  0x7696d63c in epoll_wait (epfd=16, events=0x718fd320, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x003cc8c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2  0x003ce444 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3  0x00705e50 in http::server::server_base::run() ()
#4  0x002cf3a8 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<http::server::CWebServer::StartServer(http::server::server_settings&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool)::{lambda()#294}> > >::_M_run() ()
#5  0x008db9cc in execute_native_thread_routine ()
#6  0x76aa9300 in start_thread (arg=0x718fe220) at pthread_create.c:477
#7  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 8 (Thread 0x720ff220 (LWP 13440) "Webem_ssncleane"):
#0  0x7696d63c in epoll_wait (epfd=20, events=0x720fe270, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x003cc8c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2  0x003ce444 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3  0x006dc290 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<http::server::cWebem::cWebem(http::server::server_settings const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda()#2}> > >::_M_run() ()
#4  0x008db9cc in execute_native_thread_routine ()
#5  0x76aa9300 in start_thread (arg=0x720ff220) at pthread_create.c:477
#6  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 7 (Thread 0x72ab6220 (LWP 13439) "WebServer_8080"):
#0  0x7696d63c in epoll_wait (epfd=9, events=0x72ab5320, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x003cc8c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2  0x003ce444 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3  0x00705e50 in http::server::server_base::run() ()
#4  0x002cf3a8 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<http::server::CWebServer::StartServer(http::server::server_settings&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool)::{lambda()#294}> > >::_M_run() ()
#5  0x008db9cc in execute_native_thread_routine ()
#6  0x76aa9300 in start_thread (arg=0x72ab6220) at pthread_create.c:477
#7  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 6 (Thread 0x732b7220 (LWP 13438) "Webem_ssncleane"):
#0  0x7696d63c in epoll_wait (epfd=13, events=0x732b6270, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x003cc8c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2  0x003ce444 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3  0x006dc290 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<http::server::cWebem::cWebem(http::server::server_settings const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda()#2}> > >::_M_run() ()
#4  0x008db9cc in execute_native_thread_routine ()
#5  0x76aa9300 in start_thread (arg=0x732b7220) at pthread_create.c:477
#6  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 5 (Thread 0x73ab8220 (LWP 13437) "InfluxPush"):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x008b943c in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2  0x0038ab9c in CInfluxPush::Do_Work() ()
#3  0x008db9cc in execute_native_thread_routine ()
#4  0x76aa9300 in start_thread (arg=0x73ab8220) at pthread_create.c:477
#5  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 4 (Thread 0x74923220 (LWP 13436) "PluginMgr"):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x008b943c in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2  0x00670014 in Plugins::CPluginSystem::Do_Work() ()
#3  0x008db9cc in execute_native_thread_routine ()
#4  0x76aa9300 in start_thread (arg=0x74923220) at pthread_create.c:477
#5  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0x75124220 (LWP 13435) "SQLHelper"):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x008b943c in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2  0x0029c820 in CSQLHelper::Do_Work() ()
#3  0x008db9cc in execute_native_thread_routine ()
#4  0x76aa9300 in start_thread (arg=0x75124220) at pthread_create.c:477
#5  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0x75925220 (LWP 13434) "Watchdog"):
#0  0x7692df8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x75924b90, req@entry=0x75924b88, rem=0x75924ba0, rem@entry=0x75924b98) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
#1  0x7692e080 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=<optimized out>, rem=0x75924bd0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:92
#2  0x76934830 in __GI___nanosleep (requested_time=<optimized out>, remaining=<optimized out>) at nanosleep.c:27
#3  0x0021cf5c in sleep_milliseconds(long) ()
#4  0x00287034 in Do_Watchdog_Work() ()
#5  0x008db9cc in execute_native_thread_routine ()
#6  0x76aa9300 in start_thread (arg=0x75925220) at pthread_create.c:477
#7  0x7696d208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x75e33010 (LWP 13433) "domoticz"):
#0  0x7692df8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7eb79988, req@entry=0x7eb79980, rem=0x7eb79998, rem@entry=0x7eb79990) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
#1  0x7692e080 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=<optimized out>, rem=0x7eb799c8) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:92
#2  0x76934830 in __GI___nanosleep (requested_time=<optimized out>, remaining=<optimized out>) at nanosleep.c:27
#3  0x0021cec8 in sleep_seconds(long) ()
#4  0x001ae8c4 in main ()

Main thread:
#0  0x7692df8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7eb79988, req@entry=0x7eb79980, rem=0x7eb79998, rem@entry=0x7eb79990) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
#1  0x7692e080 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=<optimized out>, rem=0x7eb799c8) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:92
#2  0x76934830 in __GI___nanosleep (requested_time=<optimized out>, remaining=<optimized out>) at nanosleep.c:27
#3  0x0021cec8 in sleep_seconds(long) ()
#4  0x001ae8c4 in main ()
[Inferior 1 (process 13433) detached]

Il y a peu être un souci quand on voit cette ligne "/sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory"

ca ressemble a ca : https://github.com/domoticz/domoticz/is ... 1044811705

Ce qui est étrange c'est que ca fait ca uniquement quand j'active le plugin.

pipiche a écrit : Donc désolé, mais j'ai peur de pas pouvoir aider. C'est Domoticz qui décide de tuer le plugin, il faudrait pouvoir faire une analyse du dump, mais ca c'est pas de ma compétence.

Moui, enfin un segmentation fault, ce n'est pas domoticz qui tue le plugin. C'est le thread du plugin qui tape n'importe où en mémoire et qui fait s'écrouler le processus comme les tours du WTC.

Code : Tout sélectionner

Thread 20 (Thread 0x6b4fc220 (LWP 21268) "Zigate"):
#0  0x769344d4 in __GI___wait4 (pid=21273, stat_loc=0x6eb2c0f0, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#1  0x002868cc in dumpstack_gdb(bool) ()
#2  0x00286e98 in signal_handler(int, siginfo_t*, void*) ()
#3  <signal handler called>
#4  raise (sig=11) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  <signal handler called>
#6  0x75a2ef34 in PyDict_GetItem () from /lib/arm-linux-gnueabihf/libpython3.9.so
#7  0x0065fddc in Plugins::CPlugin::onDeviceModified(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int) ()

Après, je ne peux pas aller plus loin, ne connaissant ni le code de domoticz et de son architecture de plugins python. Mais on peut supposer qu'il y a un problème avec un dictionnaire. Pas forcément la faute du plugin, domoticz ne vérifie peut-être pas comme il faut les données qu'on lui fournit.

Merci pour l'info et l'analyse.
A ce stade on est pas dans le plugin python, mais dans le Python Framework qu'embarque Domoticz

As-tu bien activer la creation des Devices coté Domoticz ?

Tu veux dire ce settings là ?

: device; domo_bug.PNG (14.82 Kio) Consulté 735 fois

oui c'est ca.

as-tu essayé de supprimer le plugin et ajouter un autre.

Forum Domoticz en français

[Fermé] Le plugin fait crasher domoticz (sur une installation toute fraiche)

[Fermé] Le plugin fait crasher domoticz (sur une installation toute fraiche)

Re: Le plugin fait crasher domoticz (sur une installation toute fraiche)

Re: Le plugin fait crasher domoticz (sur une installation toute fraiche)

Re: Le plugin fait crasher domoticz (sur une installation toute fraiche)

Re: Le plugin fait crasher domoticz (sur une installation toute fraiche)

Re: Le plugin fait crasher domoticz (sur une installation toute fraiche)

Re: Le plugin fait crasher domoticz (sur une installation toute fraiche)

Re: Le plugin fait crasher domoticz (sur une installation toute fraiche)

Re: Le plugin fait crasher domoticz (sur une installation toute fraiche)

Re: Le plugin fait crasher domoticz (sur une installation toute fraiche)