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

worker thread blocks #17

Open
etmmvdp opened this issue Jan 6, 2025 · 0 comments
Open

worker thread blocks #17

etmmvdp opened this issue Jan 6, 2025 · 0 comments

Comments

@etmmvdp
Copy link

etmmvdp commented Jan 6, 2025

Once a while I noticed that domoticz was not updating the p1/watermeter counter anymore. It also shows an error that the p1/watermeter worker thread was not responsive. The only way to fix this was to restart the domoticz server
In once such case I used gdb to learn the worker thread was blocking in a call to urllib.request.urlopen
By adding a timeout argument to this call the blocked problem is fixed.
I now see once a while a log message regarding failed communications but that's a benign condition which is most likely fixed in the next update request.

2025-01-06 10:13:41.529 Status: Watermeter: Started.
2025-01-06 10:13:41.530 Status: Watermeter: Entering work loop.
2025-01-06 10:13:42.321 Status: Watermeter: Initialized version 1.0.0, author 'Eraser'
2025-01-06 11:26:41.138 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
2025-01-06 14:16:11.088 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
2025-01-06 17:48:31.115 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
2025-01-06 20:19:42.359 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
2025-01-06 21:55:42.813 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
2025-01-06 23:18:32.107 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80


See also my fix at:
gettevan@6f0be08

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

1 participant