Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mainworker seems to have ended or hung unexpectedly #3215

Closed
BRUCH05 opened this issue May 14, 2019 · 6 comments
Closed

mainworker seems to have ended or hung unexpectedly #3215

BRUCH05 opened this issue May 14, 2019 · 6 comments

Comments

@BRUCH05
Copy link

BRUCH05 commented May 14, 2019

Hello,

Every day, about midgnight, Domoticz stops with this message. This issue is since the last Domoticz update with Beta version.

I've updated to

Synology : DS 216+II / Intel Celeron N3060 / DSM 6.2.1 23824 Update 6
Source : http://www.jadahl.com/domoticz_beta_6.2/
Version: 4.10734
Build Hash: 3ac5b23-modified
Compile Date: 2019-05-12 08:06:25
dzVents Version: 2.4.19

In debug mode, i can see that "cleaning sessions" seems to be the root cause of this issue.
It looks like a bug ?!

The error messages.

2019-05-09 00:04:59.501 (ZWave) Temp (Congélateur 4)
2019-05-09 00:05:00.042 InfluxLink: value Temperature,idx=70,name=Congélateur-5 value=-18.6
2019-05-09 00:05:00.552 Error: mainworker seems to have ended or hung unexpectedly (last update 301.000000 seconds ago)
2019-05-09 00:05:00.701 Error: Domoticz(10899) is exiting due to watchdog triggered...
2019-05-09 00:05:00.757 Error: Failed to start gdb, will use backtrace() for printing stack frame

2019-05-09 00:05:01.557 Status: Closing application!...
2019-05-09 00:05:01.557 Status: Stopping worker...
2019-05-09 00:05:01.558 Status: RxQueue: queue worker stopped...
2019-05-09 00:05:02.281 Status: WebServer(HTTP) stopped

2019-05-10 00:00:07.570 InfluxLink: value Temperature,idx=63,name=Congélateur-7 value=-21.8
2019-05-10 00:00:09.652 (Virtual Hardware) Light/Switch (PC-SMO02)
2019-05-10 00:04:57.998 Error: mainworker seems to have ended or hung unexpectedly (last update 301.000000 seconds ago)
2019-05-10 00:04:57.998 Error: Domoticz(7159) is exiting due to watchdog triggered...
2019-05-10 00:04:58.061 Error: Failed to start gdb, will use backtrace() for printing stack frame

2019-05-10 00:04:58.215 Status: Closing application!...
2019-05-10 00:04:58.215 Status: Stopping worker...
2019-05-11 00:00:31.189 Status: EventSystem: Script event triggered: Check Congélateur 1
2019-05-11 00:04:55.854 Error: mainworker seems to have ended or hung unexpectedly (last update 301.000000 seconds ago)
2019-05-11 00:04:55.948 Error: Domoticz(27036) is exiting due to watchdog triggered...
2019-05-11 00:04:56.142 Error: Failed to start gdb, will use backtrace() for printing stack frame

2019-05-14 00:04:42.660 [7fa2fcb1f700] Debug: [web:8084] cleaning sessions...
2019-05-14 00:04:42.663 [7fa2fbb1d700] Debug: [web:8443] cleaning sessions...
2019-05-14 00:04:55.948 [7fa2fe322700] Error: mainworker seems to have ended or hung unexpectedly (last update 301.000000 seconds ago)
2019-05-14 00:04:55.948 [7fa2fe322700] Error: Domoticz(21666) is exiting due to watchdog triggered...
2019-05-14 00:04:55.955 [7fa2fe322700] Error: Failed to start gdb, will use backtrace() for printing stack frame

2019-05-14 00:04:56.107 [7fa300985780] Status: Closing application!...
2019-05-14 00:04:56.107 [7fa300985780] Status: Stopping worker...

@derekoharrow
Copy link

I'm getting this too (as per post on the forum

Same error, but on Raspberry Pi running both v4.10740 and v4.10761

@mcwieger
Copy link

Same issue here.
Synology DS414 (after update to DSM 6.2.3.
Domoticz v4.10717.

@PabloBrzoska
Copy link

The same issue

raspberry pi 3b+, Domoticz version 2020.2 (build 12741)

any ideas?

@gizmocuz
Copy link
Contributor

I made some changes in beta 12883, I suspect it was a mutex issue. Hope it's OK now

@PabloBrzoska
Copy link

PabloBrzoska commented Jan 24, 2021

Thank you.
Updated. I'll back if happen again. I hope Not ;)

@gizmocuz
Copy link
Contributor

Thanks, closing issue. If it happens again, feel free top re-open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants