Hello guys,
It's a while ago I was here. Everything was working great for a while. But somehow the last months I have to restart once a week?
I start putty and type:
sudo service domoticz.sh restart
Then everything works fine again for a week. I can't see anything in setup->log.
Can someone point me in the right direction?
Best regards,
Wouterlet
Have to restart once a week
Moderator: leecollings
-
waltervl
- Posts: 5714
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: Have to restart once a week
Here is a good start: https://www.domoticz.com/wiki/Troubleshooting
I would start with investigation of the crash log.
If it leads to a specific Domoticz hardware update the appropriate plugin (if possible).
I would start with investigation of the crash log.
If it leads to a specific Domoticz hardware update the appropriate plugin (if possible).
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
kiddigital
- Posts: 438
- Joined: Thursday 10 August 2017 6:52
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: Have to restart once a week
Use the ‘motherboard’ hardware module to keep track of CPU and memory usage.
If memory is leaked somewhere, it could bring Domoticz to a stand stil without actually crashing…
If memory is leaked somewhere, it could bring Domoticz to a stand stil without actually crashing…
One RPi with Domoticz, RFX433e, aeon labs z-wave plus stick GEN5, ha-bridge 5.4.0 for Alexa, Philips Hue Bridge, Pimoroni Automation Hat
One RPi with Pi foundation standard touch screen to display Dashticz
One RPi with Pi foundation standard touch screen to display Dashticz
-
wouterlet
- Posts: 109
- Joined: Tuesday 02 October 2018 20:52
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Have to restart once a week
Thanks, I found the crash log. And the signal_handler was in there in Thread 21. But I don't understand really what it says,waltervl wrote: ↑Sunday 24 October 2021 12:31 Here is a good start: https://www.domoticz.com/wiki/Troubleshooting
I would start with investigation of the crash log.
If it leads to a specific Domoticz hardware update the appropriate plugin (if possible).
Code: Select all
Thread 21 (Thread 0x6b1fe220 (LWP 18337)):
#0 __waitpid (options=0, stat_loc=0x6b1fc978, pid=18342) at ../sysdeps/unix/sys v/linux/waitpid.c:30
#1 __waitpid (pid=18342, stat_loc=0x6b1fc978, options=0) at ../sysdeps/unix/sys v/linux/waitpid.c:25
#2 0x0028b14c in dumpstack_gdb(bool) ()
#3 0x0028b718 in signal_handler(int, siginfo_t*, void*) ()
#4 <signal handler called>
#5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#6 0x769d7230 in __GI_abort () at abort.c:79
#7 0x76238b00 in ?? () from /lib/arm-linux-gnueabihf/libgcrypt.so.20
Backtrace stopped: previous frame identical to this frame (corrupt stack?)-
wouterlet
- Posts: 109
- Joined: Tuesday 02 October 2018 20:52
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Have to restart once a week
To be sure here is the complete log:
Code: Select all
[New LWP 18315]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
__GI___nanosleep (remaining=0x7ec8d9d8, requested_time=0x7ec8d9d8) at ../sysdeps /unix/sysv/linux/nanosleep.c:28
28 ../sysdeps/unix/sysv/linux/nanosleep.c: No such file or directory.
Id Target Id Frame
* 1 Thread 0x76fb7010 (LWP 18314) "domoticz" __GI___nanosleep (remaini ng=0x7ec8d9d8, requested_time=0x7ec8d9d8) at ../sysdeps/unix/sysv/linux/nanoslee p.c:28
2 Thread 0x75b67220 (LWP 18315) "Watchdog" __GI___nanosleep (remaini ng=0x75b66bd0, requested_time=0x75b66bd0) at ../sysdeps/unix/sysv/linux/nanoslee p.c:28
3 Thread 0x75366220 (LWP 18319) "SQLHelper" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
4 Thread 0x74b65220 (LWP 18320) "PluginMgr" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
5 Thread 0x73d32220 (LWP 18321) "InfluxPush" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
6 Thread 0x73531220 (LWP 18322) "Webem_ssncleane" 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x73530378, maxevents=128, timeout=-1) at ../sysde ps/unix/sysv/linux/epoll_wait.c:30
7 Thread 0x72d30220 (LWP 18323) "WebServer_8080" 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x72d2f348, maxevents=128, timeout=-1) at ../sysde ps/unix/sysv/linux/epoll_wait.c:30
8 Thread 0x723ff220 (LWP 18324) "Webem_ssncleane" 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x723fe378, maxevents=128, timeout=-1) at ../sysde ps/unix/sysv/linux/epoll_wait.c:30
9 Thread 0x71bfe220 (LWP 18325) "WebServer_443" 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x71bfd348, maxevents=128, timeout=-1) at ../sysde ps/unix/sysv/linux/epoll_wait.c:30
10 Thread 0x711ff220 (LWP 18326) "Scheduler" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
11 Thread 0x709fe220 (LWP 18327) "TCPServer" 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x709fd378, maxevents=128, timeout=-1) at ../sysde ps/unix/sysv/linux/epoll_wait.c:30
12 Thread 0x701fd220 (LWP 18328) "MainWorker" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
13 Thread 0x6f9fc220 (LWP 18329) "MainWorkerRxMsg" futex_abstimed_wait_cance lable (private=<optimized out>, abstime=0x6f9fbba0, expected=0, futex_word=0xb22 9a4 <m_mainworker+3964>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
14 Thread 0x6edff220 (LWP 18330) "ZWaveBase" 0x006fe2f0 in TiXmlBase:: ReadText(char const*, TiXmlString*, bool, char const*, bool, TiXmlEncoding) ()
15 Thread 0x6e5fe220 (LWP 18331) "RFXCom" __GI___nanosleep (remaini ng=0x6e5fd700, requested_time=0x6e5fd700) at ../sysdeps/unix/sysv/linux/nanoslee p.c:28
16 Thread 0x6ddfd220 (LWP 18332) "AccuWeather" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
17 Thread 0x6d3ff220 (LWP 18333) "Harmony Hub Woo" __GI___nanosleep (remaini ng=0x6d3feb98, requested_time=0x6d3feb98) at ../sysdeps/unix/sysv/linux/nanoslee p.c:28
18 Thread 0x6cbfe220 (LWP 18334) "Buienradar" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
19 Thread 0x6c3fd220 (LWP 18335) "Netatmo " syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
20 Thread 0x6b9ff220 (LWP 18336) "Airco Ivo" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
21 Thread 0x6b1fe220 (LWP 18337) "Airco Pim" __waitpid (options=0, sta t_loc=0x6b1fc978, pid=18342) at ../sysdeps/unix/sysv/linux/waitpid.c:30
22 Thread 0x6a9fd220 (LWP 18338) "Airco Huiskamer" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
23 Thread 0x6a1fc220 (LWP 18339) "Airco Robin" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
24 Thread 0x699fb220 (LWP 18340) "Airco Ons" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
25 Thread 0x691fa220 (LWP 18341) "Harmony Hub Ver" __GI___poll (timeout=5000 , nfds=1, fds=0x691f9b70) at ../sysdeps/unix/sysv/linux/poll.c:29
26 Thread 0x689f9220 (LWP 18343) "NotificationSys" futex_abstimed_wait_cance lable (private=<optimized out>, abstime=0x689f8bd0, expected=0, futex_word=0xb22 484 <m_mainworker+2652>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
27 Thread 0x681f8220 (LWP 18348) "Plugin_ASIO" futex_wait_cancelable (pr ivate=0, expected=0, futex_word=0x26adb00) at ../sysdeps/unix/sysv/linux/futex-i nternal.h:88
28 Thread 0x679f7220 (LWP 18349) "EventSystem" syscall () at ../sysdeps/ unix/sysv/linux/arm/syscall.S:37
29 Thread 0x671f6220 (LWP 18350) "EventSystemQueu" futex_abstimed_wait_cance lable (private=<optimized out>, abstime=0x671f5ae0, expected=0, futex_word=0xb21 b80 <m_mainworker+344>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
30 Thread 0x669f5220 (LWP 18361) "RFXCom" 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x669f4360, maxevents=128, timeout=-1) at ../sysde ps/unix/sysv/linux/epoll_wait.c:30
Thread 30 (Thread 0x669f5220 (LWP 18361)):
#0 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x669f4360, maxevents =128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c53b4 in boost::asio::detail::epoll_reactor::run(long, boost::asio::det ail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003c73ac in boost::asio::detail::scheduler::run(boost::system::error_code& ) ()
#3 0x003c9738 in boost::detail::thread_data<AsyncSerial::open(std::__cxx11::bas ic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned int, boost::asio::serial_port_base::parity, boost::asio::serial_port_base::chara cter_size, boost::asio::serial_port_base::flow_control, boost::asio::serial_port _base::stop_bits)::{lambda()#2}>::run() ()
#4 0x008197bc in thread_proxy ()
#5 0x76be4494 in start_thread (arg=0x669f5220) at pthread_create.c:486
#6 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 29 (Thread 0x671f6220 (LWP 18350)):
#0 futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x671f5ae0, expected=0, futex_word=0xb21b80 <m_mainworker+344>) at ../sysdeps/unix/sysv/lin ux/futex-internal.h:205
#1 __pthread_cond_wait_common (abstime=0x671f5ae0, mutex=0x0, cond=0xb21b58 <m_ mainworker+304>) at pthread_cond_wait.c:539
#2 __pthread_cond_timedwait (cond=0xb21b58 <m_mainworker+304>, mutex=0x0, absti me=0x671f5ae0) at pthread_cond_wait.c:667
#3 0x0020e0d0 in CEventSystem::EventQueueThread() ()
#4 0x009a15a4 in execute_native_thread_routine ()
#5 0x76be4494 in start_thread (arg=0x671f6220) at pthread_create.c:486
#6 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 28 (Thread 0x679f7220 (LWP 18349)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x002054b4 in CEventSystem::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x679f7220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 27 (Thread 0x681f8220 (LWP 18348)):
#0 futex_wait_cancelable (private=0, expected=0, futex_word=0x26adb00) at ../sy sdeps/unix/sysv/linux/futex-internal.h:88
#1 __pthread_cond_wait_common (abstime=0x0, mutex=0x0, cond=0x26adad8) at pthre ad_cond_wait.c:502
#2 __pthread_cond_wait (cond=0x26adad8, mutex=0x0) at pthread_cond_wait.c:655
#3 0x003c7494 in boost::asio::detail::scheduler::run(boost::system::error_code& ) ()
#4 0x0064ca24 in Plugins::BoostWorkers() ()
#5 0x008197bc in thread_proxy ()
#6 0x76be4494 in start_thread (arg=0x681f8220) at pthread_create.c:486
#7 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 26 (Thread 0x689f9220 (LWP 18343)):
#0 futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x689f8bd0, expected=0, futex_word=0xb22484 <m_mainworker+2652>) at ../sysdeps/unix/sysv/li nux/futex-internal.h:205
#1 __pthread_cond_wait_common (abstime=0x689f8bd0, mutex=0x0, cond=0xb22458 <m_ mainworker+2608>) at pthread_cond_wait.c:539
#2 __pthread_cond_timedwait (cond=0xb22458 <m_mainworker+2608>, mutex=0x0, abst ime=0x689f8bd0) at pthread_cond_wait.c:667
#3 0x00271270 in CNotificationSystem::QueueThread() ()
#4 0x009a15a4 in execute_native_thread_routine ()
#5 0x76be4494 in start_thread (arg=0x689f9220) at pthread_create.c:486
#6 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 25 (Thread 0x691fa220 (LWP 18341)):
#0 __GI___poll (timeout=5000, nfds=1, fds=0x691f9b70) at ../sysdeps/unix/sysv/l inux/poll.c:29
#1 __GI___poll (fds=0x691f9b70, nfds=1, timeout=5000) at ../sysdeps/unix/sysv/l inux/poll.c:26
#2 0x003fb9c0 in csocket::connect(char const*, unsigned int) ()
#3 0x00497b08 in CHarmonyHub::SetupCommunicationSocket() ()
#4 0x0049abb0 in CHarmonyHub::Do_Work() ()
#5 0x009a15a4 in execute_native_thread_routine ()
#6 0x76be4494 in start_thread (arg=0x691fa220) at pthread_create.c:486
#7 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 24 (Thread 0x699fb220 (LWP 18340)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x003ad374 in CAirconWithMe::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x699fb220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 23 (Thread 0x6a1fc220 (LWP 18339)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x003ad374 in CAirconWithMe::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x6a1fc220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 22 (Thread 0x6a9fd220 (LWP 18338)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x003ad374 in CAirconWithMe::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x6a9fd220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 20 (Thread 0x6b9ff220 (LWP 18336)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x003ad374 in CAirconWithMe::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x6b9ff220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 19 (Thread 0x6c3fd220 (LWP 18335)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x0050d2d8 in CNetatmo::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x6c3fd220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 18 (Thread 0x6cbfe220 (LWP 18334)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x003ecc18 in CBuienRadar::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x6cbfe220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 17 (Thread 0x6d3ff220 (LWP 18333)):
#0 __GI___nanosleep (remaining=0x6d3feb98, requested_time=0x6d3feb98) at ../sys deps/unix/sysv/linux/nanosleep.c:28
#1 __GI___nanosleep (requested_time=0x6d3feb98, remaining=0x6d3feb98) at ../sys deps/unix/sysv/linux/nanosleep.c:25
#2 0x0021f744 in sleep_milliseconds(long) ()
#3 0x0049ac24 in CHarmonyHub::Do_Work() ()
#4 0x009a15a4 in execute_native_thread_routine ()
#5 0x76be4494 in start_thread (arg=0x6d3ff220) at pthread_create.c:486
#6 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 16 (Thread 0x6ddfd220 (LWP 18332)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x003a72e0 in CAccuWeather::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x6ddfd220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 15 (Thread 0x6e5fe220 (LWP 18331)):
#0 __GI___nanosleep (remaining=0x6e5fd700, requested_time=0x6e5fd700) at ../sys deps/unix/sysv/linux/nanosleep.c:28
#1 __GI___nanosleep (requested_time=0x6e5fd700, remaining=0x6e5fd700) at ../sys deps/unix/sysv/linux/nanosleep.c:25
#2 0x0021f744 in sleep_milliseconds(long) ()
#3 0x005a79b8 in CRFXBase::SendResetCommand() ()
#4 0x00398a84 in boost::signals2::detail::signal_impl<void (CDomoticzHardwareBa se*), boost::signals2::optional_last_value<void>, int, std::less<int>, boost::fu nction<void (CDomoticzHardwareBase*)>, boost::function<void (boost::signals2::co nnection const&, CDomoticzHardwareBase*)>, boost::signals2::mutex>::operator()(C DomoticzHardwareBase*) ()
#5 0x005aab2c in RFXComSerial::OpenSerialDevice(bool) ()
#6 0x005ab7fc in RFXComSerial::Do_Work() ()
#7 0x009a15a4 in execute_native_thread_routine ()
#8 0x76be4494 in start_thread (arg=0x6e5fe220) at pthread_create.c:486
#9 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 14 (Thread 0x6edff220 (LWP 18330)):
#0 0x006fe2f0 in TiXmlBase::ReadText(char const*, TiXmlString*, bool, char cons t*, bool, TiXmlEncoding) ()
#1 0x006ff420 in TiXmlText::Parse(char const*, TiXmlParsingData*, TiXmlEncoding ) ()
#2 0x006ff718 in TiXmlElement::ReadValue(char const*, TiXmlParsingData*, TiXmlE ncoding) ()
#3 0x006ffe3c in TiXmlElement::Parse(char const*, TiXmlParsingData*, TiXmlEncod ing) ()
#4 0x006ff7f4 in TiXmlElement::ReadValue(char const*, TiXmlParsingData*, TiXmlE ncoding) ()
#5 0x006ffe3c in TiXmlElement::Parse(char const*, TiXmlParsingData*, TiXmlEncod ing) ()
#6 0x006ff7f4 in TiXmlElement::ReadValue(char const*, TiXmlParsingData*, TiXmlE ncoding) ()
#7 0x006ffe3c in TiXmlElement::Parse(char const*, TiXmlParsingData*, TiXmlEncod ing) ()
#8 0x006feda4 in TiXmlDocument::Parse(char const*, TiXmlParsingData*, TiXmlEnco ding) ()
#9 0x006fba88 in TiXmlDocument::LoadFile(_IO_FILE*, TiXmlEncoding) ()
#10 0x006fbc08 in TiXmlDocument::LoadFile(char const*, TiXmlEncoding) ()
#11 0x00865f74 in OpenZWave::Internal::ManufacturerSpecificDB::LoadConfigFileRev ision(OpenZWave::Internal::ProductDescriptor*) ()
#12 0x00868084 in OpenZWave::Internal::ManufacturerSpecificDB::LoadProductXML() ()
#13 0x008687c0 in OpenZWave::Internal::ManufacturerSpecificDB::ManufacturerSpeci ficDB() ()
#14 0x00868a2c in OpenZWave::Internal::ManufacturerSpecificDB::Create() ()
#15 0x00860fd8 in OpenZWave::Driver::Driver(std::__cxx11::basic_string<char, std ::char_traits<char>, std::allocator<char> > const&, OpenZWave::Driver::Controlle rInterface const&) ()
#16 0x0081da94 in OpenZWave::Manager::AddDriver(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, OpenZWave::Driver::Contr ollerInterface const&) ()
#17 0x00548b74 in COpenZWave::OpenSerialConnector() ()
#18 0x005492b8 in COpenZWave::GetInitialDevices() ()
#19 0x0063acb0 in ZWaveBase::Do_Work() ()
#20 0x009a15a4 in execute_native_thread_routine ()
#21 0x76be4494 in start_thread (arg=0x6edff220) at pthread_create.c:486
#22 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 13 (Thread 0x6f9fc220 (LWP 18329)):
#0 futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6f9fbba0, expected=0, futex_word=0xb229a4 <m_mainworker+3964>) at ../sysdeps/unix/sysv/li nux/futex-internal.h:205
#1 __pthread_cond_wait_common (abstime=0x6f9fbba0, mutex=0x0, cond=0xb22978 <m_ mainworker+3920>) at pthread_cond_wait.c:539
#2 __pthread_cond_timedwait (cond=0xb22978 <m_mainworker+3920>, mutex=0x0, abst ime=0x6f9fbba0) at pthread_cond_wait.c:667
#3 0x0025d76c in MainWorker::Do_Work_On_Rx_Messages() ()
#4 0x009a15a4 in execute_native_thread_routine ()
#5 0x76be4494 in start_thread (arg=0x6f9fc220) at pthread_create.c:486
#6 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 12 (Thread 0x701fd220 (LWP 18328)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x002595d0 in MainWorker::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x701fd220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 11 (Thread 0x709fe220 (LWP 18327)):
#0 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x709fd378, maxevents =128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c53b4 in boost::asio::detail::epoll_reactor::run(long, boost::asio::det ail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003c73ac in boost::asio::detail::scheduler::run(boost::system::error_code& ) ()
#3 0x006a2220 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<tcp: :server::CTCPServer::StartServer(std::__cxx11::basic_string<char, std::char_trai ts<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::c har_traits<char>, std::allocator<char> > const&)::{lambda()#1}> > >::_M_run() ()
#4 0x009a15a4 in execute_native_thread_routine ()
#5 0x76be4494 in start_thread (arg=0x709fe220) at pthread_create.c:486
#6 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 10 (Thread 0x711ff220 (LWP 18326)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x002825c0 in CScheduler::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x711ff220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 9 (Thread 0x71bfe220 (LWP 18325)):
#0 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x71bfd348, maxevents =128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c53b4 in boost::asio::detail::epoll_reactor::run(long, boost::asio::det ail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003c73ac in boost::asio::detail::scheduler::run(boost::system::error_code& ) ()
#3 0x006ed098 in http::server::server_base::run() ()
#4 0x002d2664 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()#278}> > >::_M_run() ()
#5 0x009a15a4 in execute_native_thread_routine ()
#6 0x76be4494 in start_thread (arg=0x71bfe220) at pthread_create.c:486
#7 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 8 (Thread 0x723ff220 (LWP 18324)):
#0 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x723fe378, maxevents =128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c53b4 in boost::asio::detail::epoll_reactor::run(long, boost::asio::det ail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003c73ac in boost::asio::detail::scheduler::run(boost::system::error_code& ) ()
#3 0x006bd5e0 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<http ::server::cWebem::cWebem(http::server::server_settings const&, std::__cxx11::bas ic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda( )#2}> > >::_M_run() ()
#4 0x009a15a4 in execute_native_thread_routine ()
#5 0x76be4494 in start_thread (arg=0x723ff220) at pthread_create.c:486
#6 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 7 (Thread 0x72d30220 (LWP 18323)):
#0 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x72d2f348, maxevents =128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c53b4 in boost::asio::detail::epoll_reactor::run(long, boost::asio::det ail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003c73ac in boost::asio::detail::scheduler::run(boost::system::error_code& ) ()
#3 0x006ed098 in http::server::server_base::run() ()
#4 0x002d2664 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()#278}> > >::_M_run() ()
#5 0x009a15a4 in execute_native_thread_routine ()
#6 0x76be4494 in start_thread (arg=0x72d30220) at pthread_create.c:486
#7 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 6 (Thread 0x73531220 (LWP 18322)):
#0 0x76a979d0 in epoll_wait (epfd=<optimized out>, events=0x73530378, maxevents =128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x003c53b4 in boost::asio::detail::epoll_reactor::run(long, boost::asio::det ail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2 0x003c73ac in boost::asio::detail::scheduler::run(boost::system::error_code& ) ()
#3 0x006bd5e0 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<http ::server::cWebem::cWebem(http::server::server_settings const&, std::__cxx11::bas ic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda( )#2}> > >::_M_run() ()
#4 0x009a15a4 in execute_native_thread_routine ()
#5 0x76be4494 in start_thread (arg=0x73531220) at pthread_create.c:486
#6 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 5 (Thread 0x73d32220 (LWP 18321)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x00384634 in CInfluxPush::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x73d32220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 4 (Thread 0x74b65220 (LWP 18320)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x0064d114 in Plugins::CPluginSystem::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x74b65220) at pthread_create.c:486
#5 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 3 (Thread 0x75366220 (LWP 18319)):
#0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1 0x0097f014 in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigne d int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll > >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
#2 0x002a31ac in CSQLHelper::Do_Work() ()
#3 0x009a15a4 in execute_native_thread_routine ()
#4 0x76be4494 in start_thread (arg=0x75366220) at pthread_create.c:486
Backtrace stopped: Cannot access memory at address 0x16
Thread 2 (Thread 0x75b67220 (LWP 18315)):
#0 __GI___nanosleep (remaining=0x75b66bd0, requested_time=0x75b66bd0) at ../sys deps/unix/sysv/linux/nanosleep.c:28
#1 __GI___nanosleep (requested_time=0x75b66bd0, remaining=0x75b66bd0) at ../sys deps/unix/sysv/linux/nanosleep.c:25
#2 0x0021f744 in sleep_milliseconds(long) ()
#3 0x0028b880 in Do_Watchdog_Work() ()
#4 0x009a15a4 in execute_native_thread_routine ()
#5 0x76be4494 in start_thread (arg=0x75b67220) at pthread_create.c:486
#6 0x76a97578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/a rm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 1 (Thread 0x76fb7010 (LWP 18314)):
#0 __GI___nanosleep (remaining=0x7ec8d9d8, requested_time=0x7ec8d9d8) at ../sys deps/unix/sysv/linux/nanosleep.c:28
#1 __GI___nanosleep (requested_time=0x7ec8d9d8, remaining=0x7ec8d9d8) at ../sys deps/unix/sysv/linux/nanosleep.c:25
#2 0x0021f6b0 in sleep_seconds(long) ()
#3 0x001af338 in main ()
Main thread:
#0 __GI___nanosleep (remaining=0x7ec8d9d8, requested_time=0x7ec8d9d8) at ../sys deps/unix/sysv/linux/nanosleep.c:28
#1 __GI___nanosleep (requested_time=0x7ec8d9d8, remaining=0x7ec8d9d8) at ../sys deps/unix/sysv/linux/nanosleep.c:25
#2 0x0021f6b0 in sleep_seconds(long) ()
#3 0x001af338 in main ()
[Inferior 1 (process 18314) detached]
-
wouterlet
- Posts: 109
- Joined: Tuesday 02 October 2018 20:52
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Have to restart once a week
Ok, I added these motherboard sensors. Lets see if something strange happened at the next crashkiddigital wrote: ↑Sunday 24 October 2021 15:55 Use the ‘motherboard’ hardware module to keep track of CPU and memory usage.
If memory is leaked somewhere, it could bring Domoticz to a stand stil without actually crashing…
-
waltervl
- Posts: 5714
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: Have to restart once a week
Thread 21 is "Airco Pim" so monitor that (and the other similar airco's ) in your log file.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
wouterlet
- Posts: 109
- Joined: Tuesday 02 October 2018 20:52
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Have to restart once a week
Ah, now I see how I could find that. Ok, by monitor the log you mean the log in setup->log and then when I had to restart again?
Or are there more logs I don't know about?
-
waltervl
- Posts: 5714
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: Have to restart once a week
Yes I mean the log file. If you changed the Domoticz startup script it is also stored on disk. In the web only the latest part of the logging is shown. To see the full log you have to store the log to disk. Errors are shown longer.
In the troubleshooting page there is a section about activating the log file on disk.
In the troubleshooting page there is a section about activating the log file on disk.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
wouterlet
- Posts: 109
- Joined: Tuesday 02 October 2018 20:52
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Have to restart once a week
Ok, I manage to set the log-file at the disk I thing. To bad it was after this mornings crash. But we'll see it the next crash. So it may take a few days before I could find some results.waltervl wrote: ↑Wednesday 27 October 2021 0:20 Yes I mean the log file. If you changed the Domoticz startup script it is also stored on disk. In the web only the latest part of the logging is shown. To see the full log you have to store the log to disk. Errors are shown longer.
In the troubleshooting page there is a section about activating the log file on disk.
Thanks for the help so far, and sorry for the noob questions
-
wouterlet
- Posts: 109
- Joined: Tuesday 02 October 2018 20:52
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Have to restart once a week
This morning the system was off again. I attache the % of memory and CPU usage. CPU seems nothing special i guess. But memory was a peak at that time. Could that explain something? Or could this be the AirconWithMe plugin crashing (The plugin from my Airco units)wouterlet wrote: ↑Sunday 24 October 2021 20:14Ok, I added these motherboard sensors. Lets see if something strange happened at the next crashkiddigital wrote: ↑Sunday 24 October 2021 15:55 Use the ‘motherboard’ hardware module to keep track of CPU and memory usage.
If memory is leaked somewhere, it could bring Domoticz to a stand stil without actually crashing…
- Attachments
-
- CPU usage.png (112.49 KiB) Viewed 1480 times
-
- memory usage.png (82.19 KiB) Viewed 1480 times
-
waltervl
- Posts: 5714
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: Have to restart once a week
Could also be another program on your Pi that is hampering Domoticz. The Memory Spike is not normal. If there is a memory leak you will see a slow rise in usage. Is there something else running on this system?
Check the crash log again to see what caused Domoticz to crash. A crash once a week is a little long to disable a plugin to test.
To get around the manual startup you also as a workaround install monit to monitor your Pi and reboot the system if necessary.
See wiki https://www.domoticz.com/wiki/Monitoring_domoticz
Check the crash log again to see what caused Domoticz to crash. A crash once a week is a little long to disable a plugin to test.
To get around the manual startup you also as a workaround install monit to monitor your Pi and reboot the system if necessary.
See wiki https://www.domoticz.com/wiki/Monitoring_domoticz
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
wouterlet
- Posts: 109
- Joined: Tuesday 02 October 2018 20:52
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Have to restart once a week
No I'm only using my pi for Domoticz. The workaround sounds helpful, I'll give it a try. But I really hope to find the cause off the crash. Would be nice that it could be fixed. Hope to find something useful in the log!waltervl wrote: ↑Wednesday 27 October 2021 11:35 Could also be another program on your Pi that is hampering Domoticz. The Memory Spike is not normal. If there is a memory leak you will see a slow rise in usage. Is there something else running on this system?
Check the crash log again to see what caused Domoticz to crash. A crash once a week is a little long to disable a plugin to test.
To get around the manual startup you also as a workaround install monit to monitor your Pi and reboot the system if necessary.
See wiki https://www.domoticz.com/wiki/Monitoring_domoticz
Re: Have to restart once a week
I had the same kind of problem. It disappeared after I updated to a version where a memory leak in json was fixed.
The memory leak manifested in my case in the zigbee2mqtt plugin.
What Domoticz version are you on?
If you enabled the Motherboard Sensors there should be a device named "Process Usage", that is the device to monitor the memory usage of Domoticz.
The memory leak manifested in my case in the zigbee2mqtt plugin.
What Domoticz version are you on?
If you enabled the Motherboard Sensors there should be a device named "Process Usage", that is the device to monitor the memory usage of Domoticz.
-
heggink
- Posts: 977
- Joined: Tuesday 08 September 2015 21:44
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 12451
- Location: NL
- Contact:
Re: Have to restart once a week
Which version was that? Luckily I am on a pi with a lot of memory but it grows steadily and I suspect it's indeed related to the python plugin system (or an individual plugin) hence my interest in the autodiscovery...EddyG wrote:I had the same kind of problem. It disappeared after I updated to a version where a memory leak in json was fixed.
The memory leak manifested in my case in the zigbee2mqtt plugin.
What Domoticz version are you on?
If you enabled the Motherboard Sensors there should be a device named "Process Usage", that is the device to monitor the memory usage of Domoticz.
Sent from my SM-G980F using Tapatalk
Docker in Truenas scale, close to latest beta
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
Re: Have to restart once a week
I think that fix was build 13495. I was on build 13360 and had the crash issue, but when I switched to build 13515 it was over. Now I am on 13703 and fine.
I cannot not switch regularly, because I also have, and still have, the issue that when starting Domoticz it crashes.
I have to follow a complex procedure to be able to start Domoticz, so I (re)start as less as possible.
I cannot not switch regularly, because I also have, and still have, the issue that when starting Domoticz it crashes.
I have to follow a complex procedure to be able to start Domoticz, so I (re)start as less as possible.
-
heggink
- Posts: 977
- Joined: Tuesday 08 September 2015 21:44
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 12451
- Location: NL
- Contact:
Re: Have to restart once a week
Using the previous domoticz python framework or the new domoticzEx (with the fixed 256 device limit)?
Sent from my SM-G980F using Tapatalk
Sent from my SM-G980F using Tapatalk
Docker in Truenas scale, close to latest beta
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
Re: Have to restart once a week
I use the previous zigbee2mqtt plugin not the new DomoticzEx.
I don't like how the new version handled the devices (Dutch lapmiddel)
I already used as blacklist .*_power_;.*_effect;.*_pwrmem;.*_volt;.*_ampere;.*_thb;.*_lowbtr
So with my 50+ devices I currently have some 106 zigbee devices, with which I can handle my home automation.
106 is still far away from 256
The json bug was in Domoticz not in the plugin.
I don't like how the new version handled the devices (Dutch lapmiddel)
I already used as blacklist .*_power_;.*_effect;.*_pwrmem;.*_volt;.*_ampere;.*_thb;.*_lowbtr
So with my 50+ devices I currently have some 106 zigbee devices, with which I can handle my home automation.
106 is still far away from 256
The json bug was in Domoticz not in the plugin.
-
heggink
- Posts: 977
- Joined: Tuesday 08 September 2015 21:44
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 12451
- Location: NL
- Contact:
Re: Have to restart once a week
Ah, excellent. Thanks! That's what I needed to know. I also noticed a memory leak but never saw that there was one related to the json processing. I also have no intention to migrate either the zigbee or zwave plugin to DomoticzEx since I would rather switch straight to the MQTT autodiscovery feature. I was hesitant to upgrade to the latest beta given all the python framework changes but apparently, you did switch to a much more recent version than I so I took teh jump 
. Fingers crossed and apologies for hijacking this thread. A memory leak will indeed be a major cause for a crash. For some reason, even my watchdog would not restart my pi 
.
. Fingers crossed and apologies for hijacking this thread. A memory leak will indeed be a major cause for a crash. For some reason, even my watchdog would not restart my pi .Docker in Truenas scale, close to latest beta
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
-
wouterlet
- Posts: 109
- Joined: Tuesday 02 October 2018 20:52
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Have to restart once a week
I'm using the latest stable version. I'm want it to work as stable as possible so I prefer no beta's. I took a look at the memory usage that's since I activated it on the 24th never above 100 mb. I'll see what happens during a crash.EddyG wrote: ↑Wednesday 27 October 2021 22:24 I had the same kind of problem. It disappeared after I updated to a version where a memory leak in json was fixed.
The memory leak manifested in my case in the zigbee2mqtt plugin.
What Domoticz version are you on?
If you enabled the Motherboard Sensors there should be a device named "Process Usage", that is the device to monitor the memory usage of Domoticz.
Who is online
Users browsing this forum: No registered users and 1 guest