Hardware thread seems to have ended unexpectedly

Please use template to report bugs and problems. Post here your questions when not sure where else to post
Only for bugs in the Domoticz application! other problems go in different subforums!
Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.

Use the following template when posting here:

Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....

If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly

If you are replying, please do not quote images/code from the first post

Please mark your topic as Solved when the problem is solved.
Post Reply
dextm80
Posts: 140
Joined: Tuesday 24 October 2017 18:32
Target OS: Linux
Domoticz version: 4.10159
Contact:

Hardware thread seems to have ended unexpectedly

Post by dextm80 » Tuesday 04 December 2018 9:20

Hi guys,hi @gysmo,
latests beta give me an hardware (most) error:

(name of hardware) hardware (number) thread seems to have ended unexpectedly

Anyone that has this errors?
Domoticz on AsRock j3455-ITX 8gb ram - Aeotec ZWave Usb Stick - RFLink 433Mhz
1x Fibaro Wall Plug
1x Fibaro Motion Sensor
x NeoCoolcam Wall Plug
Netatmo Weather Station - Netatmo Thermostat
Philips Hue Bridge

User avatar
heggink
Posts: 622
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi
Domoticz version: V4.9999
Location: NL
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by heggink » Tuesday 04 December 2018 10:02

Yup. Many of them. The more python plugins I use, the more of these I get. Haven't had the time to fully dig into it but my suspicion is that domoticz does a regular heartbeat on the various device threads. If one takes too much time then a bunch of them all time out causing these entries. Doesn't mean that the HW thread has ended (they mostly function fine) but the error is annoying...
And, there are a bunch of threads on this already.
Pi3, latest beta
RFXCOM, z-wave (AEOTEC, switches, temhum, pir, contacts),
Plugwise2py, P1 'smart'meter & solar panel
Alexa, Wifi Cams motion detection
ESP: relays, PIR & Temp/TempHum
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest

dextm80
Posts: 140
Joined: Tuesday 24 October 2017 18:32
Target OS: Linux
Domoticz version: 4.10159
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by dextm80 » Wednesday 05 December 2018 21:34

it's a big problem...
Domoticz on AsRock j3455-ITX 8gb ram - Aeotec ZWave Usb Stick - RFLink 433Mhz
1x Fibaro Wall Plug
1x Fibaro Motion Sensor
x NeoCoolcam Wall Plug
Netatmo Weather Station - Netatmo Thermostat
Philips Hue Bridge

User avatar
heggink
Posts: 622
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi
Domoticz version: V4.9999
Location: NL
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by heggink » Thursday 06 December 2018 1:12

Why? Nothing really crashes. Just annoying messages. Do you see anything different?
Pi3, latest beta
RFXCOM, z-wave (AEOTEC, switches, temhum, pir, contacts),
Plugwise2py, P1 'smart'meter & solar panel
Alexa, Wifi Cams motion detection
ESP: relays, PIR & Temp/TempHum
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest

dextm80
Posts: 140
Joined: Tuesday 24 October 2017 18:32
Target OS: Linux
Domoticz version: 4.10159
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by dextm80 » Thursday 06 December 2018 9:33

Yes, my plugins seems to be crazy, for ex: false detection and very lag upgrade.
Domoticz on AsRock j3455-ITX 8gb ram - Aeotec ZWave Usb Stick - RFLink 433Mhz
1x Fibaro Wall Plug
1x Fibaro Motion Sensor
x NeoCoolcam Wall Plug
Netatmo Weather Station - Netatmo Thermostat
Philips Hue Bridge

User avatar
heggink
Posts: 622
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi
Domoticz version: V4.9999
Location: NL
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by heggink » Thursday 06 December 2018 12:13

which plugins do you use?
Pi3, latest beta
RFXCOM, z-wave (AEOTEC, switches, temhum, pir, contacts),
Plugwise2py, P1 'smart'meter & solar panel
Alexa, Wifi Cams motion detection
ESP: relays, PIR & Temp/TempHum
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest

dextm80
Posts: 140
Joined: Tuesday 24 October 2017 18:32
Target OS: Linux
Domoticz version: 4.10159
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by dextm80 » Thursday 06 December 2018 13:38

samsungctl , mac presence
Domoticz on AsRock j3455-ITX 8gb ram - Aeotec ZWave Usb Stick - RFLink 433Mhz
1x Fibaro Wall Plug
1x Fibaro Motion Sensor
x NeoCoolcam Wall Plug
Netatmo Weather Station - Netatmo Thermostat
Philips Hue Bridge

Thelion
Posts: 47
Joined: Saturday 08 October 2016 12:15
Target OS: Raspberry Pi
Domoticz version: Beta
Location: The Netherlands
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by Thelion » Thursday 06 December 2018 16:01

I have, kind of, the same issue, it sems to start when http requests are not possible any more and finally Domoticz crashes all together.

Code: Select all

Dec  6 14:33:28 domoticz domoticz: DarkSky: Error getting http data!.
Dec  6 14:33:32 domoticz domoticz: Nest: Error getting current state!
Dec  6 14:34:12 domoticz domoticz: Nest: Error login!
Dec  6 14:34:23 domoticz domoticz: P1 Wifi Gateway hardware (12) thread seems to have ended unexpectedly
Dec  6 14:34:23 domoticz domoticz: P1 Wifi Gateway hardware (12) nothing received for more than 1 Minute!....
Dec  6 14:34:24 domoticz domoticz: Restarting: P1 Wifi Gateway
Dec  6 14:34:24 domoticz domoticz: Domoticz(pid:484, tid:498('MainWorker')) received fatal signal 6 (Aborted)
Dec  6 14:34:24 domoticz domoticz: siginfo address=0x1e4, address=0xffffffff
Dec  6 14:34:29 domoticz domoticz: P1 Smart Meter: TCP/IP Worker stopped...
Dec  6 14:34:29 domoticz domoticz: Thread 11 (Thread 0x707ff430 (LWP 498)):
Dec  6 14:34:29 domoticz domoticz: #0  0x76e964cc in __waitpid (pid=17828, stat_loc=0x707fe130, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29
Dec  6 14:34:29 domoticz domoticz: #1  0x002bddd8 in dumpstack_gdb(bool) ()
Dec  6 14:34:29 domoticz domoticz: #2  0x002be3c8 in signal_handler(int, siginfo_t*, void*) ()
Dec  6 14:34:29 domoticz domoticz: #3  <signal handler called>[/b]
Dec  6 14:34:29 domoticz domoticz: #4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
Dec  6 14:34:29 domoticz domoticz: #5  0x76c3f824 in __GI_abort () at abort.c:89
Dec  6 14:34:29 domoticz domoticz: #6  0x009b9240 in __gnu_cxx::__verbose_terminate_handler() ()
Dec  6 14:34:29 domoticz domoticz: #7  0x00919ae4 in __cxxabiv1::__terminate(void (*)()) ()
Dec  6 14:34:29 domoticz domoticz: #8  0x00919b58 in std::terminate() ()
Dec  6 14:34:29 domoticz domoticz: #9  0x00254e18 in std::_Sp_counted_ptr_inplace<std::thread, std::allocator<std::thread>, (__gnu_cxx::_Lock_policy)1>::_M_dispose() ()
I have Monit running and in 6 out of 10 cases, Monit is able to get Domoticz running again, but in those other 4 cases, manual intervention is required and in most of those cases a reboot of the RPi is required.

I haven't found how to reproduce this. One day it doesn't happen, another day (like today) it happens 10 times

Already completely reinstalled Domoticz from scratch on a brandnew SD card a couple of months ago because of this issue, but that didn't result in less errors unfortunately.

Really hope there will be a solution for this....

dextm80
Posts: 140
Joined: Tuesday 24 October 2017 18:32
Target OS: Linux
Domoticz version: 4.10159
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by dextm80 » Monday 10 December 2018 10:47

my log is too many confused, there is no way to resolve this problem?
Domoticz on AsRock j3455-ITX 8gb ram - Aeotec ZWave Usb Stick - RFLink 433Mhz
1x Fibaro Wall Plug
1x Fibaro Motion Sensor
x NeoCoolcam Wall Plug
Netatmo Weather Station - Netatmo Thermostat
Philips Hue Bridge

gordonb3
Posts: 195
Joined: Saturday 31 March 2018 22:24
Target OS: Linux
Domoticz version: Custom
Location: Delft, NL
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by gordonb3 » Monday 10 December 2018 11:30

Thelion wrote:
Thursday 06 December 2018 16:01
I have, kind of, the same issue, it sems to start when http requests are not possible any more and finally Domoticz crashes all together.

<code>
That 1 minute timeout warning and subsequent restart of the P1 hardware is something you set yourself on the hardware page. The crash on shutdown of that hardware appears similar to a bug that was solved several months ago, so my guess would be that although your profile says you're running beta that will not be the latest one.

As far as the cause is concerned: yes some hardware types can lock up the system while waiting for the other side to respond. If you suspect that to be `Nest` you could try disable that for at least as long as it would normally take for the error to occur.

vervoto1
Posts: 21
Joined: Wednesday 24 December 2014 1:03
Target OS: Linux
Domoticz version: lastbeta
Location: NL
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by vervoto1 » Friday 14 December 2018 22:30

That 1 minute timeout warning and subsequent restart of the P1 hardware is something you set yourself on the hardware page. The crash on shutdown of that hardware appears similar to a bug that was solved several months ago, so my guess would be that although your profile says you're running beta that will not be the latest one.

As far as the cause is concerned: yes some hardware types can lock up the system while waiting for the other side to respond. If you suspect that to be `Nest` you could try disable that for at least as long as it would normally take for the error to occur.
Even with no warning and restart it displays the same behavior here.. thread seems to have ended unexpectedly

2018-12-14 21:16:17.031 Error: Office Air-Conditioning hardware (6) thread seems to have ended unexpectedly
2018-12-14 21:16:17.031 Error: RFXCOM hardware (10) thread seems to have ended unexpectedly
2018-12-14 21:16:17.031 Error: Nest hardware (11) thread seems to have ended unexpectedly
2018-12-14 22:17:12.428 Error: OpenZwave hardware (2) thread seems to have ended unexpectedly
2018-12-14 22:17:12.428 Error: Office Air-Conditioning hardware (6) thread seems to have ended unexpectedly
2018-12-14 22:17:12.428 Error: Harmony Hub hardware (7) thread seems to have ended unexpectedly
2018-12-14 22:17:12.428 Error: RFXCOM hardware (10) thread seems to have ended unexpectedly
2018-12-14 22:17:12.428 Error: Nest hardware (11) thread seems to have ended unexpectedly

It took me hours to prevent it from crashing every five minutes.. apparently the Smart meter that updates every 15 secs causes this.. it's now slightly more stable but still not stable. Tried pretty much everything.. downgrade, older kernel, reverse the last updates.. nothing helped.
Last edited by vervoto1 on Friday 14 December 2018 23:29, edited 1 time in total.

gordonb3
Posts: 195
Joined: Saturday 31 March 2018 22:24
Target OS: Linux
Domoticz version: Custom
Location: Delft, NL
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by gordonb3 » Friday 14 December 2018 22:55

???

Smart meter updates either every 10 seconds or if it is DSMR 5+ every second. Did you set rate limit to 15 seconds?

vervoto1
Posts: 21
Joined: Wednesday 24 December 2014 1:03
Target OS: Linux
Domoticz version: lastbeta
Location: NL
Contact:

Re: Hardware thread seems to have ended unexpectedly

Post by vervoto1 » Friday 14 December 2018 23:30

no didnt rate limit it.. so could be every 10 seconds as well.. P1 Smart meter USB, version 2.2 smart meter, updates whenever it wants which is a number of times per minute over serial --> usb. Works that way since 2014 so would be surprised if the settings suddenly cause this issue.

Post Reply

Who is online

Users browsing this forum: al300kr and 2 guests