Bug on latest domoticz -

[david31]

Hello

With the latest update beta, i have many errors same as:

Code: Select all

Error: Serveur hardware (3) thread seems to have ended unexpectedly

Over 10 per day

on the latest update realease, only 1 for week

[jannl]

No problem here, running on build 16787, downloaded the docker yesterday.

[gizmocuz]

Hello

With the latest update beta, i have many errors same as:

Code: Select all

Error: Serveur hardware (3) thread seems to have ended unexpectedly

Over 10 per day

on the latest update realease, only 1 for week

You should also mention the version you are using... your latest beta is not my latest beta

Try disabling all hardware/scripts and see what is causing this

[david31]

Version : 17523 and 17748
Plateforme : Linux / debian 13.1
Plugin/Matériel : CPU intel, motherboard ASROCK, USB zwave.me, Teleinfo, MQTT

Hello

I have tested the latest version realease., 17523.
It has been installed since the end of March.

Since April 14th, it has been crashing every 3 hours, sometimes as frequently as every 3 minutes.

No changes have been made to Domoticz.

Here is the list of updated packages.

Code: Select all

Start-Date: 2026-04-08  06:18:02
Commandline: /usr/bin/unattended-upgrade
Upgrade: openssl-provider-legacy:amd64 (3.5.5-1~deb13u1, 3.5.5-1~deb13u2), libssl-dev:amd64 (3.5.5-1~deb13u1, 3.5.5-1~deb13u2), libssl3t64:amd64 (3.5.5-1~deb13u1, 3.5.5-1~deb13u2), openssl:amd64 (3.5.5-1~deb13u1, 3.5.5-1~deb>
End-Date: 2026-04-08  06:18:05

Start-Date: 2026-04-09  06:14:01
Commandline: /usr/bin/unattended-upgrade
Upgrade: libtiff6:amd64 (4.7.0-3+deb13u1, 4.7.0-3+deb13u2)
End-Date: 2026-04-09  06:14:01

Start-Date: 2026-04-10  06:59:03
Commandline: /usr/bin/unattended-upgrade
Upgrade: openssh-client:amd64 (1:10.0p1-7+deb13u1, 1:10.0p1-7+deb13u2), ssh:amd64 (1:10.0p1-7+deb13u1, 1:10.0p1-7+deb13u2), openssh-server:amd64 (1:10.0p1-7+deb13u1, 1:10.0p1-7+deb13u2), openssh-sftp-server:amd64 (1:10.0p1-7>
End-Date: 2026-04-10  06:59:08

Start-Date: 2026-04-12  06:37:20
Commandline: /usr/bin/unattended-upgrade
Upgrade: libgdk-pixbuf-2.0-0:amd64 (2.42.12+dfsg-4, 2.42.12+dfsg-4+deb13u1), libgdk-pixbuf2.0-common:amd64 (2.42.12+dfsg-4, 2.42.12+dfsg-4+deb13u1)
End-Date: 2026-04-12  06:37:21

Start-Date: 2026-04-16  19:12:28
Commandline: apt remove linux-image-6.12.73+deb13-amd64 --purge
Purge: linux-image-6.12.73+deb13-amd64:amd64 (6.12.73-1)
End-Date: 2026-04-16  19:12:30

Start-Date: 2026-04-16  23:35:21
Commandline: apt upgrade
Upgrade: zerotier-one:amd64 (1.16.0-2, 1.16.1)
End-Date: 2026-04-16  23:35:25

The log from domoticz

Code: Select all

2026-04-17 17:46:29.770  Error: WebServer:464 thread seems to have ended unexpectedly (last update 67.000000 seconds ago)
2026-04-17 17:46:43.785  Error: WebServer:464 thread seems to have ended unexpectedly (last update 81.000000 seconds ago)
2026-04-17 17:46:57.801  Error: WebServer:464 thread seems to have ended unexpectedly (last update 95.000000 seconds ago)
2026-04-17 17:47:21.603  Status: Zwave.me: A DNS Error Occurred
2026-04-17 17:47:23.365  Status: Zwave.me: Value_Added: Warning: OpenZWave returned ValueLabel "Unknown" on Node: 8 (0x08), CommandClass: SENSOR MULTILEVEL, Label: Unknown, Instance: 1, Index: 0

Code: Select all

2026-04-17 16:44:11.921  Error: Serveur hardware (3) thread seems to have ended unexpectedly
2026-04-17 16:44:25.937  Error: Serveur hardware (3) thread seems to have ended unexpectedly
2026-04-17 16:44:39.953  Error: Serveur hardware (3) thread seems to have ended unexpectedly
2026-04-17 16:44:53.969  Error: Serveur hardware (3) thread seems to have ended unexpectedly
2026-04-17 16:45:08.041  Error: WebServer:464 thread seems to have ended unexpectedly (last update 72.000000 seconds ago)
2026-04-17 16:45:08.041  Error: Serveur hardware (3) thread seems to have ended unexpectedly

I disable hardware 3, and after:

Code: Select all

2026-04-17 17:26:38.203  Error: Weather hardware (5) thread seems to have ended unexpectedly
2026-04-17 17:26:52.219  Error: Weather hardware (5) thread seems to have ended unexpectedly
2026-04-17 17:27:06.235  Error: Weather hardware (5) thread seems to have ended unexpectedly

Since last night, I've switched to beta version 17748.
It no longer crashes, but these less serious messages remain...

Code: Select all

2026-04-18 08:05:06.771  Error: Serveur hardware (3) thread seems to have ended unexpectedly
2026-04-18 08:05:20.786  Error: Serveur hardware (3) thread seems to have ended unexpectedly
2026-04-18 08:05:34.802  Error: Serveur hardware (3) thread seems to have ended unexpectedly
2026-04-18 08:05:48.817  Error: Serveur hardware (3) thread seems to have ended unexpectedly
2026-04-18 08:06:02.833  Error: Serveur hardware (3) thread seems to have ended unexpectedly
2026-04-18 08:06:16.849  Error: Serveur hardware (3) thread seems to have ended unexpectedly

Lastest error previous bug and stop domoticz:

Code: Select all

2026-04-18 09:27:02.735  Debug: connection::handle_handshake Error: stream truncated
2026-04-18 09:27:02.742  Debug: connection::handle_handshake Error: stream truncated
2026-04-18 09:27:02.749  Debug: connection::handle_handshake Error: stream truncated
2026-04-18 09:27:02.752  Debug: connection::handle_handshake Error: stream truncated
2026-04-18 09:27:02.755  Debug: connection::handle_handshake Error: stream truncated

[gizmocuz]

Great it does not crash anymore for you.

But these log messages do not mean a lot... There are from a certain hardware or plugin, and you need to mention what hardware/plugin it is that is causing the issues

[david31]

In the old version release 2025.2, any problem.
All it workwd for over 6 month.

The hardware (3) is motherboard sensor. Need to disable this for stopping error.

But I have this all this day:

Code: Select all

2026-04-18 15:08:46.621 Error: WebServer:464 thread seems to have ended unexpectedly (last update 73.000000 seconds ago)
2026-04-18 15:26:56.659  Error: WebServer:464 thread seems to have ended unexpectedly (last update 79.000000 seconds ago)
2026-04-18 15:36:22.649  Error: WebServer:464 thread seems to have ended unexpectedly (last update 92.000000 seconds ago)

on average 3 per hour

This seems to happen only when I'm on the WLAN.

[gizmocuz]

It is probably caused by a certain hardware,plugin or script.
To debug, disable them all and enable them one by one to see which one is causing the issue

[david31]

Thanks for the tip, problem solved.

Here's an example for anyone who might have the same problem as me, with information gathered from the web.

add timeout curl with '-m 5'
add nil response and log

Code: Select all

--[[   
    json = (loadfile "/domoticz/scripts/lua/JSON.lua")()  -- For Linux
    local config=assert(io.popen('curl -m 5 -s "https://xxxxxxxxxxxxxx"', 'r'))
    local location = config:read('*all')
    config:close()
    local jsonLocation = json:decode(location)

    if jsonLocation ~= nil then
xx
xx
xx
xx
xx

    elseif (jsonLocation == nil) then
        print("Error script DOMOTICZ: xxxxxxx timeout")
    end

[waltervl]

Huh? What are you doing?
Use the asynchrounous OpenURL function for this!!!!

[david31]

I use LUA not dzevents....

[gizmocuz]

So let ChatGPT convert it to dzVents?

So you are facing a timeout issue polling a https website and it is solved with your script below.

So it is not a Domoticz issue, or any of it's default hardware related classes?

Good you solved it, but better use dzVents or let ChatGPT write you a simple python plugin?

[david31]

Maybe the next step, but I'm short on time.

I've been using Domoticz for a long time and it works very well.

No hardware problems.

Just a few scripts without a delay that were causing crashes.