Page 1 of 2
Latest update crashes domoticz
Posted: Tuesday 24 May 2022 13:16
by gerard1
Gents,
Updated today Domoticz, what was not very successful.
System Ubuntu 20.04.
I get the message that domoticz is offline.
When I check the status: everting should be running.
I have made a fresh install, which was OK, but after importing my settings, the system is offline again.
● domoticz.service - LSB: Home Automation System
Loaded: loaded (/etc/init.d/domoticz.sh; generated)
Active: active (exited) since Tue 2022-05-24 13:04:40 CEST; 10min ago
Docs: man:systemd-sysv-generator(8)
Process: 38452 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/SUCCESS)
mei 24 13:04:40 ServerZima-M systemd[1]: Starting LSB: Home Automation System...
mei 24 13:04:40 ServerZima-M domoticz.sh[38458]: 2022-05-24 13:04:40.327 Status: Domoticz V2022.1 (bu…zMoCuz
mei 24 13:04:40 ServerZima-M domoticz.sh[38458]: 2022-05-24 13:04:40.327 Status: Build Hash: d479d6cb…:01:38
mei 24 13:04:40 ServerZima-M domoticz.sh[38458]: 2022-05-24 13:04:40.327 Status: Startup Path: /home/…oticz/
mei 24 13:04:40 ServerZima-M domoticz.sh[38458]: domoticz: Domoticz is starting up....
mei 24 13:04:40 ServerZima-M domoticz[38458]: Domoticz is starting up....
mei 24 13:04:40 ServerZima-M domoticz[38459]: Domoticz running...
mei 24 13:04:40 ServerZima-M systemd[1]: Started LSB: Home Automation System.
Hint: Some lines were ellipsized, use -l to show in full.
P.S. I am running the deConz plugin as well. Has been running well for years.
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 15:51
by Huntback
Same here:
Domoticz (Latest) on Docker/Synology:
This afternoon after auto-update (Portainer) from 2022.1-build:14338 to 2022.1-build:14341 Domoticz is crashing just after startup, see below.
When i remove the mentioned plugin Domoticz is not crashing.
All versions of Domoticz before 2022.1-build:14341 had no problem with loading and/or using the mentioned plugin.
Part of logging:
2022-05-24 14:54:52.239 Status: Notification: Docker DS411: Domoticz (Latest) has just been (re)started
2022-05-24 14:54:52.366 Status: PluginSystem: 1 plugins started.
2022-05-24 14:54:52.997 Status: Domo_DS411: Connecting to 192.168.1.16:1883
2022-05-24 14:54:52.158 Error: Woonkamer: (YamahaPlug) failed to load 'plugin.py', Python Path used was ':/usr/lib/python37.zip:/usr/lib/python3.7:/usr/lib/python3.7/lib-dynload:/usr/local/lib/python3.7/dist-packages:/usr/lib/python3/dist-packages:/usr/lib/python3.7/dist-packages'.
2022-05-24 14:54:52.285 Error: Woonkamer: Exception: 'ModuleNotFoundError'. No traceback available.
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 17:53
by Joep123
Same here...
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 19:43
by kiddigital
So all 3 reports here have a crash when loading a Python plugin?
Please disable the plugin and let us know it Domoticz still crashes.
And which plugin(s) do let Domoticz crash.
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 19:53
by Joep123
I already reverted back to an earlier version of Domoticz...
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 21:00
by waltervl
I just updated to beta build 14341 on Ubuntu 20.04 on an x86 system and have no crashing environment.
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 21:08
by DAVIZINHO
same here.
Docker version 2022.1.14341
Crashes with plugin: Denon/Marantz Amplifier
I disabled it and crashes with the nextplugin: Xiaomi Mi Robot Vacuum
In this moment i need to roolback to a previous version, because i need that all works again.
I will try this night again with this version and try to tell here more plugins that crash
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 21:24
by Huntback
hello,
As stated before: When i remove the mentioned plugin Domoticz is not crashing.
Plugin name:
https://github.com/thomas-villagers/domoticz-yamaha
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 21:39
by waltervl
From what beta version did you update? This to indicate where the issue could be introduced.
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 22:17
by plugge
waltervl wrote: ↑Tuesday 24 May 2022 21:39
From what beta version did you update? This to indicate where the issue could be introduced.
Huntback wrote:
from 2022.1-build:14338 to 2022.1-build:14341
It might be build 14339 introducing the problem, for some:
Code: Select all
14339 20220520 Python Plugin BugFix: WebSocket messages handled incorrectly when split across TCP/IP buffers
No problems with Python plugins on Win10.
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 22:43
by DAVIZINHO
DAVIZINHO wrote: ↑Tuesday 24 May 2022 21:08
same here.
Docker version 2022.1.14341
Crashes with plugin: Denon/Marantz Amplifier
I disabled it and crashes with the nextplugin: Xiaomi Mi Robot Vacuum
In this moment i need to roolback to a previous version, because i need that all works again.
I will try this night again with this version and try to tell here more plugins that crash
the previous version that works for me was docker 2022.1.14338
Re: Latest update crashes domoticz
Posted: Tuesday 24 May 2022 22:51
by DoMoAD
How do you all stop the plug-ins? My installation crashes even before i get to the hardware page.
Re: Latest update crashes domoticz
Posted: Wednesday 25 May 2022 0:18
by waltervl
If you updated with webui or script then you can revert back to the previous version see wiki
https://www.domoticz.com/wiki/Raspberry ... eta_update
When using docker you could return to a previous docker build version. I do not think there were database changes in the latest beta releases.
Re: Latest update crashes domoticz
Posted: Wednesday 25 May 2022 0:37
by Dnpwwo
Unlikely that the WebSocket fix impacted this because it was contained to that protocol but there was a more general change in the last week around returning data to plgins that may have an issue.
If you are impacted please post the domoticz_crash.log file (from you Domoticz folder) and I can look.
Re: Latest update crashes domoticz
Posted: Wednesday 25 May 2022 1:21
by DoMoAD
Dnpwwo wrote: ↑Wednesday 25 May 2022 0:37
Unlikely that the WebSocket fix impacted this because it was contained to that protocol but there was a more general change in the last week around returning data to plgins that may have an issue.
If you are impacted please post the domoticz_crash.log file (from you Domoticz folder) and I can look.
see closed issue:
https://github.com/domoticz/domoticz/issues/5243
update: i have localized the plugin with the problem. it was the deconz plugin. There was an update for the plugin but it didn't resolve the problem.
Re: Latest update crashes domoticz
Posted: Wednesday 25 May 2022 4:30
by Dnpwwo
I've had a look at the deConz plugin and it does use WebSockets so it could be impacted.
If anyone has a test machine that can use this plugin it would be helpful to see the output from running with the plugin debug level set to include 'Messages'.
There is also a WebSocket Client example plugin that ships with Domoticz and the Wiki page has been updated with more information (
https://www.domoticz.com/wiki/Developin ... ol_Details) because the plugin currently only handles best case scenarios.
Re: Latest update crashes domoticz
Posted: Wednesday 25 May 2022 9:39
by kofec
In my case I also have to back to build 14337 to have below plugin running fine:
https://github.com/guillaumezin/DomoticzEbusd
Some logs but rather not helpful:
Code: Select all
Tue May 24 20:58:42 2022 daemon.info domoticz: VailantPiec: Debug set to 1
Tue May 24 20:58:42 2022 daemon.info domoticz: VailantPiec: findDevices() create connection to 127.0.0.1:8889
Tue May 24 20:58:42 2022 daemon.info domoticz: VailantPiec: Connect
Tue May 24 20:58:42 2022 daemon.info domoticz: VailantPiec: onConnect for json called
Tue May 24 20:58:42 2022 daemon.info domoticz: VailantPiec: Find
Tue May 24 20:58:42 2022 daemon.info domoticz: VailantPiec: CConnection_send, send request from 'VailantPiec' ignored. Plugin is stopping.
second case
Code: Select all
Wed May 25 00:04:32 2022 daemon.info domoticz: VailantPiec: handleFifo() create connection to 127.0.0.1:8888
Wed May 25 00:04:32 2022 daemon.info domoticz: VailantPiec: Connect
Wed May 25 00:04:32 2022 daemon.info domoticz: VailantPiec: onConnect for telnet called
Wed May 25 00:04:32 2022 daemon.info domoticz: VailantPiec: Handle
Wed May 25 00:04:32 2022 daemon.info domoticz: VailantPiec: Telnet write: read -v -c broadcast outsidetemp
Re: Latest update crashes domoticz
Posted: Wednesday 25 May 2022 11:38
by superelch
+1
fallback to latest backup.
hope it can be fixed soon.
thanks to all for your work and lifetime you spend......
Re: Latest update crashes domoticz
Posted: Wednesday 25 May 2022 11:59
by heggink
Here's what happens to my test plugin (from the memory leak issue on GitHub) when using "None" as protocol:
Code: Select all
2022-05-25 10:56:48.419 Status: T: Started.
2022-05-25 10:56:48.419 Status: NotificationSystem: thread started...
2022-05-25 10:56:48.420 Status: T: Entering work loop.
2022-05-25 10:56:48.420 Status: EventSystem: reset all events...
2022-05-25 10:56:48.422 Status: EventSystem: reset all device statuses...
2022-05-25 10:56:48.565 Status: Python EventSystem: Initializing event module.
2022-05-25 10:56:48.566 Status: EventSystem: Started
2022-05-25 10:56:48.567 Status: EventSystem: Queue thread started...
2022-05-25 10:56:48.588 Status: T: Initialized version 1.0.1, author 'heggink'
2022-05-25 10:56:48.591 T: Debug logging mask set to: PYTHON PLUGIN QUEUE IMAGE DEVICE CONNECTION MESSAGE ALL
2022-05-25 10:56:48.591 T: Pushing 'ListenDirective' on to queue
2022-05-25 10:56:48.591 T: Acquiring GIL for 'onStartCallback'
2022-05-25 10:56:48.591 T: Processing 'ListenDirective' message
2022-05-25 10:56:48.591 T: Acquiring GIL for 'ListenDirective'
2022-05-25 10:56:48.591 T: Protocol for 'Server Connection' not specified, 'None' assumed.
2022-05-25 10:56:48.591 T: Transport set to: 'TCP/IP', :8765.
2022-05-25 10:56:48.591 T: Listen directive received, action initiated successfully.
2022-05-25 10:56:48.591 T: Acquiring GIL for 'ListenDirective'
2022-05-25 10:56:48.796 Status: PluginSystem: 1 plugins started.
2022-05-25 10:56:50.440 M: Temp (Internal Temperature)
2022-05-25 10:56:58.009 T: Pushing 'onHeartbeatCallback' on to queue
2022-05-25 10:56:58.059 T: Processing 'onHeartbeatCallback' message
2022-05-25 10:56:58.059 T: Acquiring GIL for 'onHeartbeatCallback'
2022-05-25 10:56:58.060 T: Calling message handler 'onHeartbeat' on 'module' type object.
2022-05-25 10:56:58.060 T: onHeartbeat called
2022-05-25 10:56:58.060 T: Acquiring GIL for 'onHeartbeatCallback'
2022-05-25 10:56:59.480 T: Acquiring GIL for 'CPluginTransportTCP::handleAsyncAccept'
2022-05-25 10:56:59.481 T: Pushing 'ProtocolDirective' on to queue
2022-05-25 10:56:59.481 T: Pushing 'onConnectCallback' on to queue
2022-05-25 10:56:59.481 T: Acquiring GIL for 'CPluginTransportTCP::handleRead'
2022-05-25 10:56:59.481 T: Pushing 'ReadEvent' on to queue
2022-05-25 10:56:59.482 T: Acquiring GIL for 'CPluginTransportTCP::handleRead'
2022-05-25 10:56:59.482 Queued asynchronous read aborted (127.0.0.1:59256), [2] End of file.
2022-05-25 10:56:59.482 T: Pushing 'DisconnectedEvent' on to queue
2022-05-25 10:56:59.513 T: Processing 'ProtocolDirective' message
2022-05-25 10:56:59.513 T: Acquiring GIL for 'ProtocolDirective'
2022-05-25 10:56:59.513 T: Protocol set to: 'None'.
2022-05-25 10:56:59.513 T: Acquiring GIL for 'ProtocolDirective'
2022-05-25 10:56:59.513 T: Processing 'onConnectCallback' message
2022-05-25 10:56:59.513 T: Acquiring GIL for 'onConnectCallback'
2022-05-25 10:56:59.513 T: Calling message handler 'onConnect' on 'module' type object.
2022-05-25 10:56:59.513 T: onConnect called
2022-05-25 10:56:59.513 T: Connected successfully to: 127.0.0.1:59256
2022-05-25 10:56:59.514 T: Name: '127.0.0.1:59256', Transport: 'TCP/IP', Protocol: 'None', Address: '127.0.0.1', Port: '59256', Baud: -1, Timeout: 0, Bytes: 12, Connected: True, Last Seen: 2022-05-25 10:56:59, Parent: 'Server Connection'
2022-05-25 10:56:59.514 T: onConnect saving child connection for 127.0.0.1:59256
2022-05-25 10:56:59.514 T: Acquiring GIL for 'onConnectCallback'
2022-05-25 10:56:59.514 T: Processing 'ReadEvent' message
2022-05-25 10:56:59.514 T: Acquiring GIL for 'ReadEvent'
2022-05-25 10:56:59.514 T: Received 12 bytes of data
2022-05-25 10:56:59.514 T: 68 65 6c 6c 6f 20 77 6f 72 6c 64 0a .. .. .. .. .. .. .. .. hello.world.
2022-05-25 10:56:59.514 T: Pushing 'onMessageCallback' on to queue
2022-05-25 10:56:59.514 T: Acquiring GIL for 'ReadEvent'
2022-05-25 10:56:59.514 T: Processing 'DisconnectedEvent' message
2022-05-25 10:56:59.514 T: Acquiring GIL for 'DisconnectedEvent'
2022-05-25 10:56:59.515 T: Disconnect event received for '127.0.0.1:59256'.
2022-05-25 10:56:59.515 T: Pushing 'onDisconnectCallback' on to queue
2022-05-25 10:56:59.515 T: Acquiring GIL for 'DisconnectedEvent'
2022-05-25 10:56:59.515 T: Processing 'onMessageCallback' message
2022-05-25 10:56:59.515 T: Acquiring GIL for 'onMessageCallback'
2022-05-25 10:56:59.515 T: Calling message handler 'onMessage' on 'module' type object.
2022-05-25 10:56:59.515 T: onMessage called for connection: 127.0.0.1:59256
Fatal Python error: Segmentation fault
Current thread 0x6eaff220 (most recent call first):
File "/home/pi/domoticz/plugins/test/plugin.py", line 40 in onMessage
File "/home/pi/domoticz/plugins/test/plugin.py", line 66 in onMessage
2022-05-25 10:56:59.517 Error: Domoticz(pid:302, tid:321('T')) received fatal signal 11 (Segmentation fault)
2022-05-25 10:56:59.517 Error: siginfo address=0x12e, address=(nil)
2022-05-25 10:56:59.534 T: Acquiring GIL for 'CPluginTransportTCP::handleAsyncAccept'
2022-05-25 10:57:00.455 M: General/Custom Sensor (Arm Clock Speed)
2022-05-25 10:57:00.469 M: General/Custom Sensor (V3D Clock Speed)
2022-05-25 10:57:00.480 M: General/Custom Sensor (Core Clock Speed)
2022-05-25 10:57:03.149 Error: Thread 14 (Thread 0x6eaff220 (LWP 321)):
2022-05-25 10:57:03.149 Error: #0 __waitpid (options=0, stat_loc=0x6eafdcf0, pid=341) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2022-05-25 10:57:03.149 Error: #1 __waitpid (pid=341, stat_loc=0x6eafdcf0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
2022-05-25 10:57:03.149 Error: #2 0x0022b35c in dumpstack_gdb(bool) ()
2022-05-25 10:57:03.149 Error: #3 0x0022b928 in signal_handler(int, siginfo_t*, void*) ()
2022-05-25 10:57:03.149 Error: #4 <signal handler called>
2022-05-25 10:57:03.149 Error: #5 raise (sig=11) at ../sysdeps/unix/sysv/linux/raise.c:50
2022-05-25 10:57:03.149 Error: #6 <signal handler called>
2022-05-25 10:57:03.149 Error: #7 0x69746f70 in ?? ()
2022-05-25 10:57:03.149 Error: #8 0x75d37198 in _PyObject_GetMethod () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2022-05-25 10:57:03.149 Error: #9 0x75b6f440 in _PyEval_EvalFrameDefault () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2022-05-25 10:57:03.149 Error: #10 0x75b77dd4 in ?? () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
Re: Latest update crashes domoticz
Posted: Wednesday 25 May 2022 13:47
by DoMoAD
Dnpwwo wrote: ↑Wednesday 25 May 2022 4:30
If anyone has a test machine that can use this plugin it would be helpful to see the output from running with the plugin debug level set to include 'Messages'.
Debug is on the setting "basic + messages" when i restart the service i get the following error:
Code: Select all
2022-05-25 13:45:56.390 Error: Domoticz(pid:6577, tid:6602('deCONZ')) received fatal signal 11 (Segmentation fault)
2022-05-25 13:45:56.390 Error: siginfo address=0x19b1, address=(nil)
Version: 2022.1 (build 14341)
Build Hash: d479d6cb8
Compile Date: 2022-05-23 01:01:38
dzVents Version: 3.1.8
Python Version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]
Rasbian Buster
(it's not really a test machine it's my daily used domoticz install )