Domoticz version 2025.2 released (Fails)

[gerard1]

Today I noticed the update version 2025.2 was available, and updated. (webpage)
Sadly, Nothing worked any more, no webpage or what ever.
The system was telling me that all worked.
Cleaning the browser cash, did not solve the issue.
Restored the previous version and all came on line again.
Something is not right.

[jvdz]

Care to share the domoticz.log of the bootup of the new version or else it will be a lot of stabbing in the dark.

[PeJeWe]

my domoticz is down after update

My crash.log:

Code: Select all

gdb: warning: Couldn't determine a path for the index cache directory.
[New LWP 8743]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
__pthread_clockjoin_ex (threadid=1838146048, thread_return=0x0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, block=block@entry=true) at pthread_join_common.c:145
145	pthread_join_common.c: No such file or directory.
  Id   Target Id                                Frame 
* 1    Thread 0x75e75240 (LWP 16158) "domoticz" __pthread_clockjoin_ex (threadid=1838146048, thread_return=0x0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, block=block@entry=true) at pthread_join_common.c:145
  2    Thread 0x6d8fe200 (LWP 8743) "domoticz"  0x76976864 in __GI___wait4 (pid=8744, stat_loc=0x6d8fce28, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27

Thread 2 (Thread 0x6d8fe200 (LWP 8743) "domoticz"):
#0  0x76976864 in __GI___wait4 (pid=8744, stat_loc=0x6d8fce28, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#1  0x006ba0ba in dumpstack_gdb(bool) ()
#2  0x006ba510 in signal_handler(int, siginfo_t*, void*) ()
#3  <signal handler called>
#4  raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  <signal handler called>
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x768eb364 in __GI_abort () at abort.c:79
#8  0x00b71fc0 in __gnu_cxx::__verbose_terminate_handler() ()
#9  0x00b18140 in __cxxabiv1::__terminate(void (*)()) ()
#10 0x00b18196 in std::terminate() ()
#11 0x009f5d92 in boost::asio::detail::posix_thread::func<boost::asio::system_context::thread_function>::run() ()
#12 0x00795d7e in boost_asio_detail_posix_thread_function ()
#13 0x76aed310 in start_thread (arg=0x6d8fe200) at pthread_create.c:477
#14 0x769af5d8 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x75e75240 (LWP 16158) "domoticz"):
#0  __pthread_clockjoin_ex (threadid=1838146048, thread_return=0x0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, block=block@entry=true) at pthread_join_common.c:145
#1  0x76aee7ac in __pthread_join (threadid=<optimized out>, thread_return=<optimized out>) at pthread_join.c:24
#2  0x006365f0 in boost::asio::detail::posix_global_impl<boost::asio::system_context>::~posix_global_impl() ()
#3  0x76904eb4 in __run_exit_handlers (status=0, listp=0x76a24130 <__new_exitfn_called>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108
#4  0x76905054 in __GI_exit (status=<optimized out>) at exit.c:139
#5  0x768eb744 in __libc_start_main (main=0x7efe5e14, argc=1990340608, argv=0x768eb744 <__libc_start_main+280>, init=<optimized out>, fini=0xb7abb5 <__libc_csu_fini>, rtld_fini=0x76fd0510 <_dl_fini>, stack_end=0x7efe5e14) at libc-start.c:342
#6  0x00630a98 in _start ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Main thread:
#0  __pthread_clockjoin_ex (threadid=1838146048, thread_return=0x0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, block=block@entry=true) at pthread_join_common.c:145
#1  0x76aee7ac in __pthread_join (threadid=<optimized out>, thread_return=<optimized out>) at pthread_join.c:24
#2  0x006365f0 in boost::asio::detail::posix_global_impl<boost::asio::system_context>::~posix_global_impl() ()
#3  0x76904eb4 in __run_exit_handlers (status=0, listp=0x76a24130 <__new_exitfn_called>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108
#4  0x76905054 in __GI_exit (status=<optimized out>) at exit.c:139
#5  0x768eb744 in __libc_start_main (main=0x7efe5e14, argc=1990340608, argv=0x768eb744 <__libc_start_main+280>, init=<optimized out>, fini=0xb7abb5 <__libc_csu_fini>, rtld_fini=0x76fd0510 <_dl_fini>, stack_end=0x7efe5e14) at libc-start.c:342
#6  0x00630a98 in _start ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Inferior 1 (process 16158) detached]

[jannl]

You have Bookworm of a newer OS installed or use Docker?

[PeJeWe]

You have Bookworm of a newer OS installed or use Docker?

No docker, and running on bullseye

[waltervl]

You have Bookworm of a newer OS installed or use Docker?

No docker, and running on bullseye

From the announcement: viewtopic.php?f=3&t=44018

Please note that this release is using OpenSSL 3.0, you need a Debian version Bookworm or newer (Debian 13 Trixie),
on Ubuntu 24.04 or newer (due to gcc requirements). You can also move to the Docker installation if you do not want to upgrade the OS of your system.

There is a great guide to update your system from Debian 11 (Bullseye) to Bookworm.
If you are running an older version (Debian 10, Buster), then upgrade first to Bullseye (11) and then to Bookworm
https://www.cyberciti.biz/faq/update-up ... 2-bookworm

[jvdz]

@PeJeWe is using docker already.

[PeJeWe]

You have Bookworm of a newer OS installed or use Docker?

No docker, and running on bullseye

From the announcement: viewtopic.php?f=3&t=44018

Please note that this release is using OpenSSL 3.0, you need a Debian version Bookworm or newer (Debian 13 Trixie),
on Ubuntu 24.04 or newer (due to gcc requirements). You can also move to the Docker installation if you do not want to upgrade the OS of your system.

There is a great guide to update your system from Debian 11 (Bullseye) to Bookworm.
If you are running an older version (Debian 10, Buster), then upgrade first to Bullseye (11) and then to Bookworm
https://www.cyberciti.biz/faq/update-up ... 2-bookworm

how can i upgrade to bookworm

[jvdz]

Did you upgrade the docker image yo the latest version?

[PeJeWe]

Did you upgrade the docker image yo the latest version?

I'm not running docker.
I'm currently upgrading to bookworm
can it run on trixie

[Rik60]

I updated from 2025.1 to 2025.2 without problems. I was already on Bookworm running on a Rpi3B+. I did the upgrade from Bullseye to Bookworm a few weeks ago and ran in to problems when i followed: https://www.cyberciti.biz/faq/update-up ... 2-bookworm.
Z4D did not work, requirements failed. For me the only solution to get Z4D working was a fresh Bookworm install.

[PeJeWe]

I have updated my rpi to bookworm and have domoticz up and running again.
maybe in the update script a warning that the debian version is to old???

[waltervl]

I have updated my rpi to bookworm and have domoticz up and running again.
maybe in the update script a warning that the debian version is to old???

I think that is not possible as the script is already on your system.
How did you update your RPI to bookworm, what instructions did you use?

[jannl]

Always make a backup and read the relase notes.

[DIKKEHENK]

here 2025.1 on a RPI 5 Trixie, update announcement is incoming, the timer starts running, after 100 % says issues with internet connection, does not download.
Internet connection is fine, everything is getting data from the outside.

[waltervl]

here 2025.1 on a RPI 5 Trixie, update announcement is incoming, the timer starts running, after 100 % says issues with internet connection, does not download.
Internet connection is fine, everything is getting data from the outside.

Try it manual with following command from the domoticz folder to see what the update logging says.

Code: Select all

sudo ./updaterelease

[DIKKEHENK]

ha, thxs..

@rpi5:~/domoticz $ sudo ./updaterelease
Stopping Domoticz...
Making backup of current installation...
ls: cannot access 'backups/domoticz_backup_*': No such file or directory
Output file: backups/domoticz_backup_20251013_174858.tar.gz
Backup finished...
Downloading latest release version...
Checking file integrity...
Installing new version...
........................................
Starting Domoticz... (please standby...)
Done...
@rpi5:~/domoticz $

Maar na een reboot blijft het op de 2025.1 staan
Over Domoticz
Version: 2025.1
Build Hash: dd8b766bc
Compile Date: 2025-08-31 07:55:29
dzVents Version: 3.1.8
Python Version: 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]
Active User:

2025-10-13 17:51:57.280 Status: Domoticz V2025.1 (c)2012-2025 GizMoCuz
2025-10-13 17:51:57.280 Status: Build Hash: dd8b766bc, Date: 2025-08-31 07:55:29
2025-10-13 17:51:57.280 Status: Startup Path: /opt/domoticz/
2025-10-13 17:51:57.354 Status: PluginSystem: Started, Python version '3.13.5', 1 plugin definitions loaded.
2025-10-13 17:51:57.358 Status: WebServer(HTTP) started on address: :: with port 8080
2025-10-13 17:51:57.372 Status: WebServer(SSL) startup failed on address :: with port: 443: bind: Permission denied [system:13 at /usr/include/boost/asio/detail/reactive_socket_service.hpp:161 in function 'bind'], trying ::
2025-10-13 17:51:57.374 Status: WebServer(SSL) startup failed on address :: with port: 443: bind: Permission denied [system:13 at /usr/include/boost/asio/detail/reactive_socket_service.hpp:161 in function 'bind'], trying 0.0.0.0
2025-10-13 17:51:57.376 Status: TCPServer: shared server started...
2025-10-13 17:51:57.387 Status: RxQueue: queue worker started...
2025-10-13 17:51:59.387 Status: intergas thuis: Worker started...
2025-10-13 17:51:59.387 Status: Gaslichtmeter: Using serial port: /dev/ttyUSB0
2025-10-13 17:51:59.398 Status: Gaslichtmeter: Worker started...
2025-10-13 17:51:59.399 Status: Buienradar: Worker started...
2025-10-13 17:51:59.415 Status: mobosensoren: System: ODroid/Raspberry
2025-10-13 17:51:59.415 Status: mobosensoren: Hardware Monitor: Started (OStype Linux)
2025-10-13 17:51:59.415 Status: noorsweer: Started...
2025-10-13 17:51:59.415 Status: Enever Dutch Electricity/Gas Price feed: Worker started...
2025-10-13 17:51:59.415 Status: NotificationSystem: thread started...
2025-10-13 17:51:59.415 Status: EventSystem: reset all events...
2025-10-13 17:51:59.416 Status: dzVents: Write file: /opt/domoticz/scripts/dzVents/generated_scripts/luchtkwaliteit2.lua
2025-10-13 17:51:59.416 Status: EventSystem: reset all device statuses...
2025-10-13 17:51:59.438 Status: Python EventSystem: Initializing event module.
2025-10-13 17:51:59.438 Status: Python EventSystem: Initializing event module.
2025-10-13 17:51:59.438 Status: EventSystem: Started
2025-10-13 17:51:59.438 Status: EventSystem: Queue thread started...
2025-10-13 17:51:59.563 Status: Gaslichtmeter: Meter reports as ESMR 5.0
2025-10-13 17:51:59.624 Status: Gaslichtmeter: Current electricity tariff: High
2025-10-13 17:51:59.959 Status: Gaslichtmeter: Found gas meter on M-Bus channel 1

[waltervl]

I see
Startup Path: /opt/domoticz/

Are you using Domoticz in a docker container? Because then you need to use another method of updating.

[DIKKEHENK]

Nope, no containers. Just plain on RPI5, trixie

[waltervl]

Then I would expect that you run the update command from /opt/domoticz and not from ~/domoticz.
But perhaps they are the same.