Error messages in log : ... thread seems to have ended unexp
Moderator: leecollings
-
- Posts: 6
- Joined: Sunday 06 December 2015 17:36
- Target OS: NAS (Synology & others)
- Domoticz version: 2.3771
- Contact:
Error messages in log : ... thread seems to have ended unexp
Hi All,
Since this evening, I have some strange messages in the domoticz log :
2015-12-10 22:57:04.042 Error: EventSystem thread seems to have ended unexpectedly
2015-12-10 22:57:04.042 Error: Scheduler thread seems to have ended unexpectedly
2015-12-10 22:57:04.042 Error: Motherboard hardware (1) thread seems to have ended unexpectedly
Additionnally, GUI freezes often, I have to wait for seconds to switch from tab to tab (for example to pass from #/log to #/dashboard). I haven't a lot of devices, just
* a teleinfo device,
* z-wave network with Aeotec Z-Stick S2 controller and 8 devices.
and 2 events.
Regards,
Since this evening, I have some strange messages in the domoticz log :
2015-12-10 22:57:04.042 Error: EventSystem thread seems to have ended unexpectedly
2015-12-10 22:57:04.042 Error: Scheduler thread seems to have ended unexpectedly
2015-12-10 22:57:04.042 Error: Motherboard hardware (1) thread seems to have ended unexpectedly
Additionnally, GUI freezes often, I have to wait for seconds to switch from tab to tab (for example to pass from #/log to #/dashboard). I haven't a lot of devices, just
* a teleinfo device,
* z-wave network with Aeotec Z-Stick S2 controller and 8 devices.
and 2 events.
Regards,
McSoda
Domoticz running on Synology 212j (main), Raspberry Pi B rev2 (remote)
Modules : z-wave, x10, teleinfo, karotz
Domoticz running on Synology 212j (main), Raspberry Pi B rev2 (remote)
Modules : z-wave, x10, teleinfo, karotz
-
- Posts: 2
- Joined: Friday 11 December 2015 15:07
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Error messages in log : ... thread seems to have ended u
Same issue here. Running latest stable version on a Raspberry Pi2.
Please advise
Please advise
-
- Posts: 25
- Joined: Sunday 16 August 2015 22:19
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Error messages in log : ... thread seems to have ended u
.. and for me as well. It occurs after 1-1.5 days of operation.
SevenW
SevenW
-
- Posts: 2
- Joined: Wednesday 03 June 2015 7:13
- Target OS: -
- Domoticz version:
- Contact:
Re: Error messages in log : ... thread seems to have ended u
I been having the same issue with my pi running the zwave domoticz server, my other 1 isn't have any issues which only has the piface board isn't having any issues. Only been happening since the latest update.
-
- Posts: 25
- Joined: Sunday 16 August 2015 22:19
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Error messages in log : ... thread seems to have ended u
On another thread with a similar issue a saw two suggestions.
1. out of memory: check with df -h on command line if a mount is full (not the case with me)
2. Two MQTT brokers in the hardware list. -> delete one.
I happened two have two brokers, listening to different MQTT servers, but I now deleted one to see whether it becomes stable.
SevenW
1. out of memory: check with df -h on command line if a mount is full (not the case with me)
2. Two MQTT brokers in the hardware list. -> delete one.
I happened two have two brokers, listening to different MQTT servers, but I now deleted one to see whether it becomes stable.
SevenW
-
- Posts: 6
- Joined: Sunday 06 December 2015 17:36
- Target OS: NAS (Synology & others)
- Domoticz version: 2.3771
- Contact:
Re: Error messages in log : ... thread seems to have ended u
No more troubles anymore. They disappeared.
May be linked to a faulty disk which slowed down my Syno ? :-/
Thanks,
May be linked to a faulty disk which slowed down my Syno ? :-/
Thanks,
McSoda
Domoticz running on Synology 212j (main), Raspberry Pi B rev2 (remote)
Modules : z-wave, x10, teleinfo, karotz
Domoticz running on Synology 212j (main), Raspberry Pi B rev2 (remote)
Modules : z-wave, x10, teleinfo, karotz
-
- Posts: 2
- Joined: Friday 11 December 2015 15:07
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Error messages in log : ... thread seems to have ended u
none of the 2 above options applies to me. None of my mounts is full and I have no MQTT brokers in the hardware listed at all.
-
- Posts: 25
- Joined: Sunday 16 August 2015 22:19
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Error messages in log : ... thread seems to have ended u
No, going back to one MQTT broker did not solve it. Next hang-up after 48 hours. This makes it pretty unworkable.
Maybe GizMoCuz can advise?
SevenW
Maybe GizMoCuz can advise?
SevenW
-
- Posts: 2
- Joined: Wednesday 03 June 2015 7:13
- Target OS: -
- Domoticz version:
- Contact:
Re: Error messages in log : ... thread seems to have ended unexp
I recently redone some changed, I've found if I used the pi with the zwave controller to run the script to turn off my lights I don't get the error/crash, but if I run the same script from my master.it give the error/crashes. Turning the lights on from the master doesn't cause any issues.
- Minglarn
- Posts: 214
- Joined: Friday 21 August 2015 19:27
- Target OS: Raspberry Pi / ODroid
- Domoticz version: v3.8153
- Location: Stockholm / Sweden
- Contact:
Re: Error messages in log : ... thread seems to have ended unexp
Hi!
Now my instande of Domoticz acts like this.
Every hour it spits out this in the log: EventSystem thread seems to have ended unexpectedly
And this keeps going on for every hour... Anyone who could help me solve this or give me some tip?
Latest beta installed... on RPI2.
Now my instande of Domoticz acts like this.
Every hour it spits out this in the log: EventSystem thread seems to have ended unexpectedly
Code: Select all
2016-12-09 18:02:23.727 Error: EventSystem thread seems to have ended unexpectedly
2016-12-09 19:02:08.517 Error: EventSystem thread seems to have ended unexpectedly
2016-12-09 21:02:18.358 Error: EventSystem thread seems to have ended unexpectedly
2016-12-09 23:02:04.875 Error: EventSystem thread seems to have ended unexpectedly
2016-12-09 23:02:04.875 Error: Scheduler thread seems to have ended unexpectedly
2016-12-10 00:04:16.783 Error: EventSystem thread seems to have ended unexpectedly
2016-12-10 00:04:16.783 Error: Scheduler thread seems to have ended unexpectedly
2016-12-10 02:01:58.678 Error: EventSystem thread seems to have ended unexpectedly
2016-12-10 08:02:03.316 Error: EventSystem thread seems to have ended unexpectedly
2016-12-10 08:02:03.316 Error: Scheduler thread seems to have ended unexpectedly
Latest beta installed... on RPI2.
“When you eliminate the impossible, whatever remains, however improbable, must be the truth.” -Spock in Star Trek VI
-
- Posts: 279
- Joined: Sunday 03 January 2016 14:55
- Target OS: -
- Domoticz version:
- Location: Sweden
- Contact:
Re: Error messages in log : ... thread seems to have ended unexp
It can be something that runs every hour.Minglarn wrote:Hi!
Now my instande of Domoticz acts like this.
Every hour it spits out this in the log: EventSystem thread seems to have ended unexpectedlyAnd this keeps going on for every hour... Anyone who could help me solve this or give me some tip?Code: Select all
2016-12-09 18:02:23.727 Error: EventSystem thread seems to have ended unexpectedly 2016-12-09 19:02:08.517 Error: EventSystem thread seems to have ended unexpectedly 2016-12-09 21:02:18.358 Error: EventSystem thread seems to have ended unexpectedly 2016-12-09 23:02:04.875 Error: EventSystem thread seems to have ended unexpectedly 2016-12-09 23:02:04.875 Error: Scheduler thread seems to have ended unexpectedly 2016-12-10 00:04:16.783 Error: EventSystem thread seems to have ended unexpectedly 2016-12-10 00:04:16.783 Error: Scheduler thread seems to have ended unexpectedly 2016-12-10 02:01:58.678 Error: EventSystem thread seems to have ended unexpectedly 2016-12-10 08:02:03.316 Error: EventSystem thread seems to have ended unexpectedly 2016-12-10 08:02:03.316 Error: Scheduler thread seems to have ended unexpectedly
Latest beta installed... on RPI2.
Try to disable all your Events and see it that helps. It can also be the backup function which runs every hour.
- Minglarn
- Posts: 214
- Joined: Friday 21 August 2015 19:27
- Target OS: Raspberry Pi / ODroid
- Domoticz version: v3.8153
- Location: Stockholm / Sweden
- Contact:
Re: Error messages in log : ... thread seems to have ended unexp
Tried that ...
And the solution was to stop BACKUP ...
And the solution was to stop BACKUP ...
“When you eliminate the impossible, whatever remains, however improbable, must be the truth.” -Spock in Star Trek VI
- ejsmith
- Posts: 2
- Joined: Wednesday 24 July 2019 15:25
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Error messages in log : ... thread seems to have ended unexp
Hi guys,
A short update to mention that I had similar issue with my rasberry PI 3 with raspberian and domoticz.
I just disabled blue tooth and the error is gone!
A short update to mention that I had similar issue with my rasberry PI 3 with raspberian and domoticz.
Which, after reboot, provoked domoticz to end in the state "active (exited)".2019-07-24 00:11:55.472 Status: EventSystem: Started
2019-07-24 00:11:55.472 Status: EventSystem: Queue thread started...
2019-07-24 00:11:55.477 Status: PluginSystem: Entering work loop.
2019-07-24 00:13:34.159 Error: EventSystem thread seems to have ended unexpectedly (last update 82.000000 seconds ago)
2019-07-24 00:13:34.160 Error: Scheduler thread seems to have ended unexpectedly (last update 82.000000 seconds ago)
I just disabled blue tooth and the error is gone!
Who is online
Users browsing this forum: Google [Bot] and 1 guest