Segmentation error after upgrade

[roelvdh]

After upgrading to the 2024.2 release my Raspi system fails operating, reporting Segmentation Error.

1. Status is active (exited):
pi@EnergyPi:~/domoticz $ sudo service domoticz status
● domoticz.service - LSB: Home Automation System
Loaded: loaded (/etc/init.d/domoticz.sh; generated)
Active: active (exited) since Tue 2024-01-16 09:05:09 CET; 20min ago
Docs: man:systemd-sysv-generator(8)
Process: 1129 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/S

jan 16 09:05:09 EnergyPi systemd[1]: Starting LSB: Home Automation System...
jan 16 09:05:09 EnergyPi domoticz.sh[1129]: Segmentation fault
jan 16 09:05:09 EnergyPi systemd[1]: Started LSB: Home Automation System.pi@EnergyPi:~/domoticz $ sudo service domoticz status

2. Tried updatebeta (updaterelease was empty) : no access to backups
pi@EnergyPi:~/domoticz $ ./updatebeta
Stopping Domoticz...
Making backup of current installation...
ls: kan geen toegang krijgen tot 'backups/domoticz_backup_*': Toegang geweigerd
Output file: backups/domoticz_backup_20240116_090408.tar.gz

gzip: stdout: No space left on device
tar: backups/domoticz_backup_20240116_090408.tar.gz: Slechts 4096 van 10240 bytes geschreven
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Backup finished...
Downloading latest beta version...
Problem downloading new Domoticz version!!. Restarting current version...
pi@EnergyPi:~/domoticz $

pi@EnergyPi:~/domoticz $ cd backups
-bash: cd: backups: Toegang geweigerd
pi@EnergyPi:~/domoticz $

3. Hardware check : Problem with Water Meter
pi@EnergyPi:~/domoticz $ sudo ps uax | grep domoticz
root 457 0.0 0.0 1940 392 ? Ss 08:56 0:00 /bin/sh -c /usr/bin/python /home/pi/domoticz/scripts/watermeter.py >/var/log/cronlog.log 2>&1
root 460 0.0 0.9 24708 9228 ? Sl 08:56 0:00 /usr/bin/python /home/pi/domoticz/scripts/watermeter.py
pi 1278 0.0 0.0 7500 496 pts/0 S+ 09:17 0:00 grep --color=auto domoticz
pi@EnergyPi:~/domoticz $

Indeed, this hardware was physically removed quite a while ago (a few Domoticz updates have successfully been installed since) but I never removed the Water Meter from the hardware list as I wanted to reinstall it later.

4. Logs
At the end of this post in order not to clutter


-----------------------------

Current situation: my remote cannot access the Domoticz API on the Raspi, on the Raspi I have no access to the backups. The Raspi has a SD-card of 8Gb. Problem might be the SD is full

-----------------------------

pi@EnergyPi:~/domoticz $ sudo cat domoticz_crash.log
[New LWP 523]
[New LWP 524]
[New LWP 529]
[New LWP 530]
[New LWP 532]
[New LWP 534]
[New LWP 535]
[New LWP 536]
[New LWP 537]
[New LWP 538]
[New LWP 539]
[New LWP 540]
[New LWP 710]
[New LWP 711]
[New LWP 713]
[New LWP 714]
[New LWP 715]
[New LWP 716]
[New LWP 717]
[New LWP 725]
[New LWP 726]
[New LWP 727]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
__GI___nanosleep (remaining=0x7e91b8c8, requested_time=0x7e91b8c8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
28 ../sysdeps/unix/sysv/linux/nanosleep.c: Bestand of map bestaat niet.
Id Target Id Frame
* 1 Thread 0x76f78010 (LWP 522) "domoticz" __GI___nanosleep (remaining=0x7e91b8c8, requested_time=0x7e91b8c8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
2 Thread 0x75a20220 (LWP 523) "SQLHelper" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
3 Thread 0x7521f220 (LWP 524) "PluginMgr" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
4 Thread 0x743ed220 (LWP 529) "InfluxPush" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
5 Thread 0x73bec220 (LWP 530) "Webem_ssncleane" 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x73beb270, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
6 Thread 0x733eb220 (LWP 532) "WebServer_8080" 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x733ea320, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
7 Thread 0x729ff220 (LWP 534) "Webem_ssncleane" 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x729fe270, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
8 Thread 0x721fe220 (LWP 535) "WebServer_443" 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x721fd320, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
9 Thread 0x717ff220 (LWP 536) "Scheduler" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
10 Thread 0x70ffe220 (LWP 537) "TCPServer" 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x70ffd350, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
11 Thread 0x705ff220 (LWP 538) "MainWorker" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
12 Thread 0x6fdfe220 (LWP 539) "MainWorkerRxMsg" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6fdfdba0, expected=0, futex_word=0xa70c34 <m_mainworker+4036>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
13 Thread 0x6f5fd220 (LWP 540) "Watchdog" __waitpid (options=0, stat_loc=0x6f5fc380, pid=1104) at ../sysdeps/unix/sysv/linux/waitpid.c:30
14 Thread 0x6e9ff220 (LWP 710) "MainWorker" 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x6e9fe318, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
15 Thread 0x6e1fe220 (LWP 711) "Slimme Meter ka" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
16 Thread 0x6d7ff220 (LWP 713) "Weerkanaal" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
17 Thread 0x6cffe220 (LWP 714) "Tado systeem" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
18 Thread 0x6c7fd220 (LWP 715) "Plat Dak" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
19 Thread 0x6bffc220 (LWP 716) "Schuin Dak" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
20 Thread 0x6b7fb220 (LWP 717) "NotificationSys" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6b7fabd0, expected=0, futex_word=0xa70694 <m_mainworker+2596>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
21 Thread 0x6affa220 (LWP 725) "EventSystem" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
22 Thread 0x6a7f9220 (LWP 726) "EventSystemQueu" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6a7f8ae0, expected=0, futex_word=0xa6fd94 <m_mainworker+292>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
23 Thread 0x69ff8220 (LWP 727) "Plugin_ASIO" futex_wait_cancelable (private=0, expected=0, futex_word=0x16f4f88) at ../sysdeps/unix/sysv/linux/futex-internal.h:88

Thread 23 (Thread 0x69ff8220 (LWP 727)):
#0 futex_wait_cancelable (private=0, expected=0, futex_word=0x16f4f88) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1 __pthread_cond_wait_common (abstime=0x0, mutex=0x0, cond=0x16f4f60) at pthread_cond_wait.c:502
#2 __pthread_cond_wait (cond=0x16f4f60, mutex=0x0) at pthread_cond_wait.c:655
#3 0x003cb694 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#4 0x00673134 in Plugins::BoostWorkers() ()
#5 0x00756588 in thread_proxy ()
#6 0x76a9d494 in start_thread (arg=0x69ff8220) at pthread_create.c:486
#7 0x76950578 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 22 (Thread 0x6a7f9220 (LWP 726)):
#0 futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6a7f8ae0, expected=0, futex_word=0xa6fd94 <m_mainworker+292>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1 __pthread_cond_wait_common (abstime=0x6a7f8ae0, mutex=0x0, cond=0xa6fd68 <m_mainworker+248>) at pthread_cond_wait.c:539
#2 __pthread_cond_timedwait (cond=0xa6fd68 <m_mainworker+248>, mutex=0x0, abstime=0x6a7f8ae0) at pthread_cond_wait.c:667
#3 0x0020a86c in CEventSystem::EventQueueThread() ()
#4 0x008dd334 in execute_native_thread_routine ()
#5 0x76a9d494 in start_thread (arg=0x6a7f9220) at pthread_create.c:486
#6 0x76950578 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 21 (Thread 0x6affa220 (LWP 725)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x00201780 in CEventSystem::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x6affa220) at pthread_create.c:486
#5 0x76950578 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 20 (Thread 0x6b7fb220 (LWP 717)):
#0 futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6b7fabd0, expected=0, futex_word=0xa70694 <m_mainworker+2596>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1 __pthread_cond_wait_common (abstime=0x6b7fabd0, mutex=0x0, cond=0xa70668 <m_mainworker+2552>) at pthread_cond_wait.c:539
#2 __pthread_cond_timedwait (cond=0xa70668 <m_mainworker+2552>, mutex=0x0, abstime=0x6b7fabd0) at pthread_cond_wait.c:667
#3 0x0026f1f8 in CNotificationSystem::QueueThread() ()
#4 0x008dd334 in execute_native_thread_routine ()
#5 0x76a9d494 in start_thread (arg=0x6b7fb220) at pthread_create.c:486
Backtrace stopped: Cannot access memory at address 0x1d39bcc4

Thread 19 (Thread 0x6bffc220 (LWP 716)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x005ea7fc in CSBFSpot::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x6bffc220) at pthread_create.c:486
#5 0x76950578 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 18 (Thread 0x6c7fd220 (LWP 715)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x005ea7fc in CSBFSpot::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x6c7fd220) at pthread_create.c:486
#5 0x76950578 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 17 (Thread 0x6cffe220 (LWP 714)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x0060801c in CTado::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x6cffe220) at pthread_create.c:486
#5 0x76950578 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 16 (Thread 0x6d7ff220 (LWP 713)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x00540af8 in COpenWeatherMap::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x6d7ff220) at pthread_create.c:486
#5 0x76950578 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 15 (Thread 0x6e1fe220 (LWP 711)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x0059e514 in P1MeterSerial::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x6e1fe220) at pthread_create.c:486
#5 0x76950578 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 14 (Thread 0x6e9ff220 (LWP 710)):
#0 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x6e9fe318, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c9a30 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003cb5ac in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3 0x003cd644 in boost::detail::thread_data<AsyncSerial::open(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned int, boost::asio::serial_port_base::parity, boost::asio::serial_port_base::character_size, boost::asio::serial_port_base::flow_control, boost::asio::serial_port_base::stop_bits)::{lambda()#2}>::run() ()
#4 0x00756588 in thread_proxy ()
#5 0x76a9d494 in start_thread (arg=0x6e9ff220) at pthread_create.c:486
#6 0x76950578 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 13 (Thread 0x6f5fd220 (LWP 540)):
#0 __waitpid (options=0, stat_loc=0x6f5fc380, pid=1104) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1 __waitpid (pid=1104, stat_loc=0x6f5fc380, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
#2 0x0028756c in dumpstack_gdb(bool) ()
#3 0x00287a70 in signal_handler(int, siginfo_t*, void*) ()
#4 <signal handler called>
#5 raise (sig=10) at ../sysdeps/unix/sysv/linux/raise.c:50
#6 0x00287d3c in Do_Watchdog_Work() ()
#7 0x008dd334 in execute_native_thread_routine ()
#8 0x76a9d494 in start_thread (arg=0x6f5fd220) at pthread_create.c:486
#9 0x76950578 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 12 (Thread 0x6fdfe220 (LWP 539)):
#0 futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6fdfdba0, expected=0, futex_word=0xa70c34 <m_mainworker+4036>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1 __pthread_cond_wait_common (abstime=0x6fdfdba0, mutex=0x0, cond=0xa70c08 <m_mainworker+3992>) at pthread_cond_wait.c:539
#2 __pthread_cond_timedwait (cond=0xa70c08 <m_mainworker+3992>, mutex=0x0, abstime=0x6fdfdba0) at pthread_cond_wait.c:667
#3 0x0025d68c in MainWorker::Do_Work_On_Rx_Messages() ()
#4 0x008dd334 in execute_native_thread_routine ()
#5 0x76a9d494 in start_thread (arg=0x6fdfe220) at pthread_create.c:486
#6 0x76950578 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 11 (Thread 0x705ff220 (LWP 538)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x00259898 in MainWorker::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x705ff220) at pthread_create.c:486
#5 0x76950578 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 10 (Thread 0x70ffe220 (LWP 537)):
#0 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x70ffd350, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c9a30 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003cb5ac in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3 0x006c509c in std::thread::_State_impl<std::thread::_Invoker<std::tuple<tcp::server::CTCPServer::StartServer(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda()#1}> > >::_M_run() ()
#4 0x008dd334 in execute_native_thread_routine ()
#5 0x76a9d494 in start_thread (arg=0x70ffe220) at pthread_create.c:486
#6 0x76950578 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 9 (Thread 0x717ff220 (LWP 536)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x0027f6a0 in CScheduler::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x717ff220) at pthread_create.c:486
#5 0x76950578 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 8 (Thread 0x721fe220 (LWP 535)):
#0 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x721fd320, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c9a30 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003cb5ac in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3 0x00707798 in http::server::server_base::run() ()
#4 0x002d0128 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<http::server::CWebServer::StartServer(http::server::server_settings&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool)::{lambda()#294}> > >::_M_run() ()
#5 0x008dd334 in execute_native_thread_routine ()
#6 0x76a9d494 in start_thread (arg=0x721fe220) at pthread_create.c:486
#7 0x76950578 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 7 (Thread 0x729ff220 (LWP 534)):
#0 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x729fe270, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c9a30 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003cb5ac in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3 0x006deff0 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<http::server::cWebem::cWebem(http::server::server_settings const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda()#2}> > >::_M_run() ()
#4 0x008dd334 in execute_native_thread_routine ()
#5 0x76a9d494 in start_thread (arg=0x729ff220) at pthread_create.c:486
#6 0x76950578 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 6 (Thread 0x733eb220 (LWP 532)):
#0 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x733ea320, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c9a30 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003cb5ac in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3 0x00707798 in http::server::server_base::run() ()
#4 0x002d0128 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<http::server::CWebServer::StartServer(http::server::server_settings&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool)::{lambda()#294}> > >::_M_run() ()
#5 0x008dd334 in execute_native_thread_routine ()
#6 0x76a9d494 in start_thread (arg=0x733eb220) at pthread_create.c:486
#7 0x76950578 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 5 (Thread 0x73bec220 (LWP 530)):
#0 0x769509d0 in epoll_wait (epfd=<optimized out>, events=0x73beb270, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c9a30 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003cb5ac in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3 0x006deff0 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<http::server::cWebem::cWebem(http::server::server_settings const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda()#2}> > >::_M_run() ()
#4 0x008dd334 in execute_native_thread_routine ()
#5 0x76a9d494 in start_thread (arg=0x73bec220) at pthread_create.c:486
#6 0x76950578 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 4 (Thread 0x743ed220 (LWP 529)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x00384e34 in CInfluxPush::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x743ed220) at pthread_create.c:486
#5 0x76950578 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 3 (Thread 0x7521f220 (LWP 524)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x00673844 in Plugins::CPluginSystem::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x7521f220) at pthread_create.c:486
#5 0x76950578 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 2 (Thread 0x75a20220 (LWP 523)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x008bada4 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x0029d118 in CSQLHelper::Do_Work() ()
#3 0x008dd334 in execute_native_thread_routine ()
#4 0x76a9d494 in start_thread (arg=0x75a20220) at pthread_create.c:486
Backtrace stopped: Cannot access memory at address 0x2e

Thread 1 (Thread 0x76f78010 (LWP 522)):
#0 __GI___nanosleep (remaining=0x7e91b8c8, requested_time=0x7e91b8c8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1 __GI___nanosleep (requested_time=0x7e91b8c8, remaining=0x7e91b8c8) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0x0021cbe8 in sleep_seconds(long) ()
#3 0x001aebf0 in main ()

Main thread:
#0 __GI___nanosleep (remaining=0x7e91b8c8, requested_time=0x7e91b8c8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1 __GI___nanosleep (requested_time=0x7e91b8c8, remaining=0x7e91b8c8) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0x0021cbe8 in sleep_seconds(long) ()
#3 0x001aebf0 in main ()
[Inferior 1 (process 522) detached]
pi@EnergyPi:~/domoticz $

[gizmocuz]

I understand you are using master/client setup (two instances) ? (Remote...)
In this case, make sure both systems are using the latest stable/beta

All these messages are rights issues, try to execute them with 'sudo'

[Kedi]

This might give a hint:

Code: Select all

gzip: stdout: No space left on device

Do a

Code: Select all

sudo df -H

and see if there is a problem with space.
Otherwise it might be a permission problem.

[MikeyMan]

After upgrading to the 2024.2 release my Raspi system fails operating, reporting Segmentation Error.

I'm having similar issues, lots of crashes. Did you manage to fix it?

[elzorrovega]

Hello All,

I recently updated my Domoticz/RaspberryPi 3+ server as follows:

1st-update
RASPBERRY Pi Information -Bullseye
Linux version 6.1.21-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023

2nd-update
zwave-js-ui: 9.8.2.9ba5886
zwave-js: 12.4.3
home id: 3714679688
home hex: 0xdd698388

3rd-update
DOMOTICZ Information
build_time : 2024-01-30 09:16:34
dzvents_version : 3.1.8
hash : 731719420
python_version : 3.9.2 (default Feb 28 2021 17:03:44) \n[GCC 10.2.1 20210110]
version : 2024.4


After an update, I reboot system to ensure that there are no additional snags. At the third reboot, I noticed that Domoticz crashed. Please find attached the crash log.

Service is started via Init.d method. Literature says that the preferred method is via Systemd.
In directory etc/systemd/system, there is no domoticz.service file.

Gismocuz says that these are right issues. I used a simple script below and system is up.

sudo service domoticz.sh stop
sudo service domoticz.sh start
sudo service domoticz.sh status
sudo /etc/init.d/monit start

Has someone else experienced similar issues after rebooting?

domoticz_crash.log

(22.86 KiB) Downloaded 33 times

[HvdW]

It is not recommended to update RPI to a higher version for example from buster to bullseye.
It is recommended to do a clean install with a newer version.
I tried the first method several times, it was successful with the latter.

[MikeyMan]

It is not recommended to update RPI to a higher version for example from buster to bullseye.
It is recommended to do a clean install with a newer version.
I tried the first method several times, it was successful with the latter.

For me this is independent of any upgrade. Just started crashing a lot without any cause.

Really feeling a huge decline in stability over the last years. Getting totally unusable.

[waltervl]

I never had any crashes with my system recently (last 3 years) Crashes most likely are related to bad written python plugins or python modules OR bad hardware (SD card, disk full, bad power supply etc) or strange values in the database.
Look in the troubleshooting wiki https://www.domoticz.com/wiki/Troubleshooting

[MikeyMan]

I never had any crashes with my system recently (last 3 years) Crashes most likely are related to bad written python plugins or python modules OR bad hardware (SD card, disk full, bad power supply etc) or strange values in the database.
Look in the troubleshooting wiki https://www.domoticz.com/wiki/Troubleshooting

That's all very nice, but it's just not sustainable.
Dropped almost all plugins and hardware, which even had been stable for a long time, bar the p1 integration and some output to pvoutput. Change over my sd card several times, power supply is superb and got a full metal housing. Even with less shit running it's getting worse and worse.

Robustness is key, and that's simply lacking.

[waltervl]

Seems to be hardware or database related. For most users Domoticz runs stable as ever.....
So something on your systems seems wrong. You are complaining now for months on this forum but these kind of issues are very difficult to track down if they cannot be related to some reproducible circumstances.

[MikeyMan]

Seems to be hardware or database related. For most users Domoticz runs stable as ever.....
So something on your systems seems wrong. You are complaining now for months on this forum but these kind of issues are very difficult to track down if they cannot be related to some reproducible circumstances.

That's my point. Like I said, I only removed hardware and even made the unwanted step towards HA. The logging does not help. I cannot remove anymore hardware without being completely useless. Both database and software robustness is key. And should be part of software development.

[HvdW]

I installed domoticz over and over. (just for experimenting)
Never ran into trouble recept when trying to change from buster to bullseye and bullseye to bookworm in the background.

[elzorrovega]

Hello,

Thanks for the tip.

Our battery power supply died and had to switch to simple plug this morning.
Domoticz did not load at boot time but Monit loaded it afterwards. Somewhere hidden in bullseye there is/are conflict(s) causing issues.

Will take your advice and make a clean installation of bookwork this time and use a RaspberryPi4 as hardware to ensure that RAM is not an issue.
Pi3 1 GB RAM usage is approximately 56 %.

[elzorrovega]

Hello,

After a clean install of Bullseye, Domoticz is up and running normally in Pi4 B.

Domoticz Z-Wave Controller is Z-Stick Gen5+ Chip Type ZW0501 Ver 4.54. Even with new Power Supply - iUniker with output 5,1V 4A 20,4W - controller is not seen when connected directly to Pi's USB 2.0 ports.

As suggested by others in the community, connected controller to an USB 2.0 Hub with own power supply and everyone seems to be happy.

These boot messages and/or crashes are due most probably to current OS running on Pi and/or other hardware issues.