Domoticz

Yeap it works from 17053 to 17056 and i saw an new design in about page. Thanks!

Hi,

Again from 17057 to 1760.
It needs to be updated twice to work.
This is the third time that it has had to be updated twice to get it to work. The same problem was with the last 2 previous update versions.

>> Checking package dependencies...
>> All required packages are already installed
>> Running updated script - proceeding with installation...
>> Stopping Domoticz service...
>> Creating backup: backups/domoticz_backup_20260130_083246.tar.gz
tar: .: file changed as we read it
>> Backup creation failed!

No update issues here.
if you update from command line with ./updatebeta do you need to use sudo or not? I need to use sudo.
Does the account that runs domoticz have write access on the backups folder?

It looks like a/some file still changed while the tar backup was running and the update batch file checks the successful creation of the tar backupfile, so the update process is stopped.
This test was added recently: Maybe the check for successful completion needs to be modified to "> 1" as rc=1 means there are only warnings?

Hi,

I updated my system to Debian 13 x64 i have beta 17091 and now the same issue...can;t update to 17096.
Between certain versions it works perfectly. Now it can't be updated again

There should be a logging screen in your webgui update. What does it say?
There was again a breaking change due to libmosquitto1 that needs to be downloaded and installed. For me it installed just in the available 100 seconds timeframe but perhaps on a slower system you need to run the update twice.

Usually it gets stuck at the backup part. But something very strange happens, I try to update several times and it doesn't work... I try again in 5-6 hours and it works the first time like now...i received 17096. I have encountered this situation several times in the last month. I'm thinking maybe he doesn't have enough time to create the backup or something else?

So guess it dies with this statement in your update log, as I mentioned earlier?: "Backup creation failed!"

Exactly "Backup creation failed!"

Seems there is some race condition where files are still being changed while the backup creation is running. Maybe test with a "sleep 5" just before starting the backup to give the system 5 seconds to finish all writes?

The domoticz service was stopped just before backup archive creation starts, but some writes may still be in caches and not written on storage... Especially if some memory management tunables were changed to better merge writes in order to preserve a SD card and even normal commit time may lead to writes starting after several seconds delay.

=> IMHO, better that a fixed delay, I would recommend adding this in the script after service stop:
Source for this tip to ensure all is flushed afterwards:
https://www.kernel.org/doc/Documentation/sysctl/vm.txt

Especially:

To free slab objects and pagecache:
echo 3 > /proc/sys/vm/drop_caches
(...)
To increase the number of objects freed by this operation, the user may run
`sync' prior to writing to /proc/sys/vm/drop_caches. This will minimize the
number of dirty objects on the system and create more candidates to be
dropped.

I tried several times to upgrade 17096 to 17099 and the same issue but with Failed to stop service in addition.


> Package 'libmosquitto1' is already installed
>> All required packages are already installed
>> Running updated script - proceeding with installation...
>> Stopping Domoticz service...
Job for domoticz.service canceled.
>> Failed to stop service (may not be running)
>> Creating backup: backups/domoticz_backup_20260210_203401.tar.gz
tar: ./domoticz.db-wal: file changed as we read it
tar: .: file changed as we read it
>> Backup creation failed!