Domoticz

Since the upgrade to 2024.7, I noticed that Domoticz just stops responding in the website. It seem it has hung itself. Only a restart of the domiticz.sh will solve this. I see no errors in the log and it has worked flawlessly until 2024.7 version.

This is the status just before I restarted the service:

● domoticz.service - LSB: Home Automation System
Loaded: loaded (/etc/init.d/domoticz.sh; generated)
Active: active (running) since Sun 2024-07-28 08:10:16 CEST; 5 days ago
Docs: man:systemd-sysv-generator(8)
Process: 17653 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/SUCCESS)
Tasks: 30 (limit: 3720)
CPU: 9h 7min 47.252s
CGroup: /system.slice/domoticz.service
└─17659 /home/pi/domoticz/domoticz -daemon -www 8080 -sslwww 443 -log /tmp/log/domoticz.log

Jul 28 08:10:16 domoticz systemd[1]: Starting LSB: Home Automation System...
Jul 28 08:10:16 domoticz domoticz.sh[17658]: 2024-07-28 08:10:16.362 Status: Domoticz V2024.7 (c)2012-2024 GizMoCuz
Jul 28 08:10:16 domoticz domoticz.sh[17658]: 2024-07-28 08:10:16.362 Status: Build Hash: b317cfab1, Date: 2024-07-1>
Jul 28 08:10:16 domoticz domoticz.sh[17658]: 2024-07-28 08:10:16.363 Status: Startup Path: /home/pi/domoticz/
Jul 28 08:10:16 domoticz domoticz.sh[17658]: domoticz: Domoticz is starting up....
Jul 28 08:10:16 domoticz domoticz[17658]: Domoticz is starting up....
Jul 28 08:10:16 domoticz systemd[1]: Started LSB: Home Automation System.

Just for the record, I'm noticing the same behaviour since this version as well, every few days I have to restart Domoticz as it became completely unresponsive (interface as well as working under the bonnet/hood)

No issues here, what platform o/s etc

No issues here too. Check the troubleshooting wiki for hints how to debug: https://www.domoticz.com/wiki/Troubleshooting

microkid wrote: ↑Friday 02 August 2024 11:43 I see no errors in the log and it has worked flawlessly until 2024.7 version.

In the log extract you provide, there is only the restart log.
The log before hang/stop would be the useful one but if you don't log to a file you'll not be able to get it. In domoticz startup script (should be in /etc/init.d), you should add the startup option to log in a file, like:

DAEMON_ARGS="$DAEMON_ARGS -log /tmp/domoticz.txt"

You may log on storage (home dir...), not on /tmp as I do, if not sure to have enough size as it's a tmpfs (aka ramdisk). Mine was resized (that's a /etc/fstab edit + Linux restart, if you want to go this way, 100m should be OK for a few days) & a cron job limits the file size grow every couple of day, as I'm only interested in some post mortem log analysis (with a still running Linux so ramdisk content is kept) when needed & don't want added SD card wear with these logs. But just the time to figure-out what's wrong for you, that's OK. Just don't forget to clean this setup after.

If more is needed, consider waltervi suggestion...

On my side, no issue with 2024.7 so far, only restart I had was triggered by my certificate renewal (for external https connection), this happens every 2 or 3 months & I got one recently. I now often have several months of Domoticz uptime, usually I only reboot the wole PI when there was a Linux kernel (or a library used system-wide like libc) showing-up in the upgrades. Got few issues on some new device inclusion (zwave) in the past, but with a stable hardware that's OK.

I enabled the DAEMON_ARGS="$DAEMON_ARGS -log /tmp/domoticz.txt" now, let's see if that gives some info.

Sorry, English: I have enabled the same setting as I am experiencing the problem of domoticz hanging quite frequently. Maybe since the update? Don't know.

Domoticz hung today. Nothing in the logs though. Last message is about the P1 interface values:
2024-08-06 14:49:39.559 P1meter: Usage (Actual Delivery (L1 + L2 + L3))

I've added the line to log debug level as well. Maybe that is why I don't see anything....

Hi,

I'm having the same issues.
Before 2027.7 my domoticz was very stable, but after the update it something hangs and do i need to do a restart
The problem is that i can regenerate the problem and it seems to occurs randomly. Something just when i'm in the browser in the config, but i had once it just stopped in the middle of the day.

There is also already a running github issue for randomly crashing on 2024.7 (and later beta's) https://github.com/domoticz/domoticz/issues/6117

I suppose everyone having this issue, is using the default binary Domoticz or docker image, have not enabled any additional logging (like debug info etc)

If yes, please try beta 16178

I have the samme issue every day round about 4 am.

Version: 2024.7
Build Hash: b317cfab1
Compile Date: 2024-07-13 16:59:31
dzVents Version: 3.1.8
Python Version: 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110]

Running on my Synology NAS as docker container.

I have created other domoticz instance and restored backup from primary instance - not any better.

Disabled automatic backup, EventSystem & dzvents - not any better

Disabled all scheduled tasks on my NAS - not any better

Log part:

2024-08-07 04:00:01.061 dzVents: Handling httpResponse-events for: "lastSeen"
2024-08-07 04:00:24.794 dzVents: Handling events for: "TV Salon", value: "Open"
2024-08-07 04:02:04.858 Error: Scheduler thread seems to have ended unexpectedly (last update 64.000000 seconds ago)
2024-08-07 04:02:06.074 dzVents: Handling events for: "TV Salon", value: "Closed"
2024-08-07 04:03:54.197 dzVents: Handling events for: "TV Salon", value: "Open"
2024-08-07 04:06:26.511 dzVents: Handling events for: "TV Salon", value: "Closed"
2024-08-07 04:06:32.523 Error: Scheduler thread seems to have ended unexpectedly (last update 92.000000 seconds ago)
2024-08-07 04:07:42.533 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 68.000000 seconds ago)
2024-08-07 04:07:56.535 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 82.000000 seconds ago)
2024-08-07 04:08:10.538 Error: Scheduler thread seems to have ended unexpectedly (last update 70.000000 seconds ago)
2024-08-07 04:08:10.538 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 96.000000 seconds ago)
2024-08-07 04:08:24.540 Error: Scheduler thread seems to have ended unexpectedly (last update 84.000000 seconds ago)
2024-08-07 04:08:28.742 dzVents: Handling events for: "TV Salon", value: "Open"
2024-08-07 04:09:02.505 dzVents: Handling events for: "TV Salon", value: "Closed"
2024-08-07 04:09:12.460 Error: EventSystem: Warning!, lua script /opt/domoticz/dzVents/runtime/dzVents.lua has been running for more than 10 seconds
2024-08-07 04:12:02.739 [WebServer] Deprecated RType (devices) for API request. Handled via fallback (getdevices), please use correct API Command! (172.26.0.1)
2024-08-07 04:12:06.862 Error: Scheduler thread seems to have ended unexpectedly (last update 126.000000 seconds ago)
2024-08-07 04:14:12.888 Error: Scheduler thread seems to have ended unexpectedly (last update 72.000000 seconds ago)
2024-08-07 04:14:26.890 Error: Scheduler thread seems to have ended unexpectedly (last update 86.000000 seconds ago)
2024-08-07 04:14:40.894 Error: Scheduler thread seems to have ended unexpectedly (last update 100.000000 seconds ago)
2024-08-07 04:14:40.895 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 66.000000 seconds ago)
2024-08-07 04:16:13.312 Error: Pogoda hardware (35) thread seems to have ended unexpectedly
2024-08-07 04:16:13.361 Error: Autodiscovery: Disconnected, restarting (rc=19/Keepalive exceeded)



2024-08-08 04:00:01.196 dzVents: Handling httpResponse-events for: "lastSeen"
2024-08-08 04:07:52.559 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 110.000000 seconds ago)
2024-08-08 04:07:54.392 Error: MQTT LAN: Disconnected, restarting (rc=14/Broken pipe)
2024-08-08 04:07:54.993 Error: Autodiscovery: Disconnected, restarting (rc=14/Broken pipe)
2024-08-08 04:08:17.715 Status: MQTT LAN: Connecting to A.B.C.247:1883
2024-08-08 04:08:18.102 Status: MQTT LAN: Re-connected to: A.B.C.247:1883
2024-08-08 04:08:18.918 Status: Autodiscovery: Connecting to A.B.C.247:1883
2024-08-08 04:08:19.119 Status: Autodiscovery: Re-connected to: A.B.C.247:1883

Any hint ? :/

I have next 24 containers running on my Docker without a single issue.

Domoticz hung again just now. Nothing in the log files. Very annoying.

same problem suddenly after a few weeks no problem with 2024.7 version. Backup database was already turned off.
For next days,
Google message disabled. And all IP addresses are allowed again under the trusted network. (changed that a few days). Maybe it helps...
I had 2 crashed last days, in the middele of the night.

All running on beta 16178 or above?

gizmocuz wrote: ↑Tuesday 20 August 2024 7:54 All running on beta 16178 or above?

No not yet, i will do that. I wasn't sure if there already was an update for the problem.

Updated yesterday to 16182, crashed again today. Automatic back-up is disabled. Attached the crash log, but i do not know if there is any useable information in there.

This was again at midnight or during the day?

During the day.

gizmocuz wrote: ↑Tuesday 20 August 2024 7:54 All running on beta 16178 or above?

No more problems so far. Thanks!