clean installation but not accessible Domoticz Topic is solved

On various Hardware and OS systems: pi / windows / routers / nas, etc

Moderator: leecollings

Post Reply
Geertjan
Posts: 4
Joined: Wednesday 20 January 2021 17:18
Target OS: Raspberry Pi / ODroid
Domoticz version: newest
Location: Haarlem, NL
Contact:

clean installation but not accessible Domoticz

Post by Geertjan »

Hello,
I would like to ask for help with my problem with Domoticz.
A while ago I bought an RPI 3b to read my energy meter. That went well for a while, approximately 1.5 months. After working well for a while, I got problems with Domoticz, which was not approachable. On top of that, my RPI also broke and I was done with the RPI.
Recently received a new one (warranty). Now I want to start Domoticz. However, this will lead to nothing.
My last attempt today was:
- a freshly formatted SD card
- a new raspbian installation incl. updates
- a new domoticz installation incl. updates
After all this, Domoticz could be reached (via the address line that is in the WiFi symbol on my RPI +: 8080) on my windows laptop. I created 2 devices for the test. After about 15 minutes, Domoticz changed and was no longer available, in any way and on any device. Check done on RPI, Domoticz was active.
It seems as if Domoticz works on my RPI but that the reachability / accessibility of the program is not working properly.
I have checked a number of things.
- the status of Domoticz, it was ongoing.
- check on port 8080, via "sudo netstat -lpn" port 8080 was not visible.
- on the RPI itself via address line 127.0.0.1:8080, no response
I cannot read crashlog in Domoticz, pop-up with "failed to open Crash .... log and access denied


I no longer know how to reach Domoticz.
as for my RPI / Rasbian knowledge, it is less than average

what can I do to reach my Domoticz?
RPI3b+cc2531+p1 meter+watermeter Connectix
User avatar
waltervl
Posts: 5908
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: clean installation but not accessible Domoticz

Post by waltervl »

you need administrator rights to open the crash log file.
See also https://www.domoticz.com/wiki/Troubleshooting for some more troubleshooting tips.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Geertjan
Posts: 4
Joined: Wednesday 20 January 2021 17:18
Target OS: Raspberry Pi / ODroid
Domoticz version: newest
Location: Haarlem, NL
Contact:

Re: clean installation but not accessible Domoticz

Post by Geertjan »

Hi Walter,

thanks for the suggestion.
I did some troubelshooting and it gave me some parameters

Code: Select all

2021-01-20 21:40:55.389  Status: Domoticz V2020.2 (c)2012-2020 GizMoCuz
2021-01-20 21:40:55.389  Status: Build Hash: b63341bc0, Date: 2020-04-26 13:47:55
2021-01-20 21:40:55.389  Status: Startup Path: /home/pi/domoticz/
2021-01-20 21:40:55.984  Status: PluginSystem: Started, Python version '3.7.3'.
2021-01-20 21:40:55.992  Active notification Subsystems: fcm, http (2/13)
2021-01-20 21:40:56.018  Status: WebServer(HTTP) started on address: :: with port 8080
2021-01-20 21:40:56.057  [color=#FF0000]Error: WebServer(SSL) startup failed on address 0.0.0.0 with port: 443: bind: Permission denied[/color]
2021-01-20 21:40:56.057  [color=#FF0000]Error: WebServer(SSL) check privileges for opening ports below 1024[/color]
2021-01-20 21:40:56.060  Starting shared server on: :::6144
2021-01-20 21:40:56.060  Status: TCPServer: shared server started...
2021-01-20 21:40:56.061  Status: RxQueue: queue worker started...
2021-01-20 21:40:58.061  Status: Hardware Monitor: Started
2021-01-20 21:40:58.137  Status: NotificationSystem: thread started...
2021-01-20 21:40:58.138  Status: BuienRadar: Worker started...
2021-01-20 21:40:58.138  Status: EventSystem: reset all events...
2021-01-20 21:40:58.141  Status: EventSystem: reset all device statuses...
2021-01-20 21:40:58.264  Status: Python EventSystem: Initalizing event module.
2021-01-20 21:40:58.264  Status: EventSystem: Started
2021-01-20 21:40:58.265  Status: EventSystem: Queue thread started...
2021-01-20 21:40:58.614  Status: PluginSystem: Entering work loop.
terminate called after throwing an instance of 'std::invalid_argument'
  what():  stod
2021-01-20 21:41:05.697  Error: Domoticz(pid:9415, tid:9436('BuienRadar')) received fatal signal 6 (Aborted)
2021-01-20 21:41:05.697  Error: siginfo address=0x24c7, address=0xffffffff
2021-01-20 21:41:10.695  Error: Thread 13 (Thread 0x6f5fe220 (LWP 9436)):
2021-01-20 21:41:10.696  Error: #0  __waitpid (options=0, stat_loc=0x6f5fcf78, pid=9461) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2021-01-20 21:41:10.696  Error: #1  __waitpid (pid=9461, stat_loc=0x6f5fcf78, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
2021-01-20 21:41:10.696  Error: #2  0x002db8ec in dumpstack_gdb(bool) ()
2021-01-20 21:41:10.696  Error: #3  0x002dbeb8 in signal_handler(int, siginfo_t*, void*) ()
2021-01-20 21:41:10.696  Error: #4  <signal handler called>
2021-01-20 21:41:10.696  Error: #5  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
2021-01-20 21:41:10.696  Error: #6  0x769e5230 in __GI_abort () at abort.c:79
2021-01-20 21:41:10.696  Error: #7  0x0096d02c in __gnu_cxx::__verbose_terminate_handler() ()
2021-01-20 21:41:10.696  Error: #8  0x008d04cc in __cxxabiv1::__terminate(void (*)()) ()
2021-01-20 21:41:10.696  Error: #9  0x008d0540 in std::terminate() ()
2021-01-20 21:41:10.696  Error: #10 0x008daff0 in __cxa_throw ()
2021-01-20 21:41:10.696  Error: #11 0x00909a48 in std::__throw_invalid_argument(char const*) ()
2021-01-20 21:41:10.696  Error: #12 0x0039ce94 in double __gnu_cxx::__stoa<double, double, char>(double (*)(char const*, char**), char const*, char const*, unsigned int*) ()
2021-01-20 21:41:10.696  Error: #13 0x00407628 in CBuienRadar::GetStationDetails() ()
2021-01-20 21:41:10.696  Error: #14 0x00407e70 in CBuienRadar::GetMeterDetails() ()
2021-01-20 21:41:10.696  Error: #15 0x00408a90 in CBuienRadar::Do_Work() ()
2021-01-20 21:41:10.696  Error: #16 0x009447ec in execute_native_thread_routine ()
2021-01-20 21:41:10.696  Error: #17 0x76bf2494 in start_thread (arg=0x6f5fe220) at pthread_create.c:486
first error is when the webserver starts port 443. port 8080 should still work, there is no error in it.
Paragraph crash log doesn't tell me how I can become the owner of it. Just something about a "signal handler"
RPI3b+cc2531+p1 meter+watermeter Connectix
User avatar
waltervl
Posts: 5908
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: clean installation but not accessible Domoticz

Post by waltervl »

Looks like buienradar is crashing your system. Please try the remove the hardware.
Or as it is a fresh installation, do a complete reinstall.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Geertjan
Posts: 4
Joined: Wednesday 20 January 2021 17:18
Target OS: Raspberry Pi / ODroid
Domoticz version: newest
Location: Haarlem, NL
Contact:

Re: clean installation but not accessible Domoticz

Post by Geertjan »

tried again, now with good results.

Code: Select all

[New LWP 9416]
[New LWP 9418]
[New LWP 9419]
[New LWP 9420]
[New LWP 9421]
[New LWP 9422]
[New LWP 9423]
[New LWP 9424]
[New LWP 9425]
[New LWP 9426]
[New LWP 9433]
[New LWP 9436]
[New LWP 9437]
[New LWP 9438]
[New LWP 9439]
[New LWP 9440]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
__GI___nanosleep (remaining=0x7ef82f88, requested_time=0x7ef82f88) 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 0x76fc6190 (LWP 9415) "domoticz"        __GI___nanosleep (remaining=0x7ef82f88, requested_time=0x7ef82f88) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
  2    Thread 0x75b74220 (LWP 9416) "Watchdog"        __GI___nanosleep (remaining=0x75b73bd0, requested_time=0x75b73bd0) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
  3    Thread 0x75373220 (LWP 9418) "SQLHelper"       syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  4    Thread 0x74b72220 (LWP 9419) "PluginMgr"       syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  5    Thread 0x73d77220 (LWP 9420) "InfluxPush"      syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  6    Thread 0x73576220 (LWP 9421) "Webem_ssncleane" 0x76aa59d0 in epoll_wait (epfd=<optimized out>, events=0x73575378, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
  7    Thread 0x72d75220 (LWP 9422) "WebServer_8080"  0x76aa59d0 in epoll_wait (epfd=<optimized out>, events=0x72d74348, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
  8    Thread 0x723ff220 (LWP 9423) "Scheduler"       syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  9    Thread 0x71bfe220 (LWP 9424) "TCPServer"       0x76aa59d0 in epoll_wait (epfd=<optimized out>, events=0x71bfd378, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
  10   Thread 0x711ff220 (LWP 9425) "MainWorker"      syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  11   Thread 0x709fe220 (LWP 9426) "MainWorkerRxMsg" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x709fdbb8, expected=0, futex_word=0xabb688 <m_mainworker+4192>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  12   Thread 0x6fdff220 (LWP 9433) "HardwareMonitor" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  13   Thread 0x6f5fe220 (LWP 9436) "BuienRadar"      __waitpid (options=0, stat_loc=0x6f5fcf78, pid=9461) at ../sysdeps/unix/sysv/linux/waitpid.c:30
  14   Thread 0x6edfd220 (LWP 9437) "NotificationSys" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6edfcbcc, expected=0, futex_word=0xabb154 <m_mainworker+2860>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  15   Thread 0x6e1ff220 (LWP 9438) "EventSystem"     syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  16   Thread 0x6d9fe220 (LWP 9439) "EventSystemQueu" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6d9fdaf8, expected=0, futex_word=0xaba770 <m_mainworker+328>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  17   Thread 0x6d1fd220 (LWP 9440) "Plugin_ASIO"     futex_wait_cancelable (private=0, expected=0, futex_word=0x14098c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88

Thread 17 (Thread 0x6d1fd220 (LWP 9440)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x14098c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x0, cond=0x14098a0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x14098a0, mutex=0x0) at pthread_cond_wait.c:655
#3  0x003e1088 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#4  0x00626270 in Plugins::BoostWorkers() ()
#5  0x007c287c in thread_proxy ()
#6  0x76bf2494 in start_thread (arg=0x6d1fd220) at pthread_create.c:486
#7  0x76aa5578 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 0x6d9fe220 (LWP 9439)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6d9fdaf8, expected=0, futex_word=0xaba770 <m_mainworker+328>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0x6d9fdaf8, mutex=0x0, cond=0xaba748 <m_mainworker+288>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xaba748 <m_mainworker+288>, mutex=0x0, abstime=0x6d9fdaf8) at pthread_cond_wait.c:667
#3  0x0025f4e8 in CEventSystem::EventQueueThread() ()
#4  0x009447ec in execute_native_thread_routine ()
#5  0x76bf2494 in start_thread (arg=0x6d9fe220) at pthread_create.c:486
#6  0x76aa5578 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 0x6e1ff220 (LWP 9438)):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x0092225c 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  0x00256d80 in CEventSystem::Do_Work() ()
#3  0x009447ec in execute_native_thread_routine ()
#4  0x76bf2494 in start_thread (arg=0x6e1ff220) at pthread_create.c:486
#5  0x76aa5578 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 0x6edfd220 (LWP 9437)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6edfcbcc, expected=0, futex_word=0xabb154 <m_mainworker+2860>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0x6edfcbcc, mutex=0x0, cond=0xabb128 <m_mainworker+2816>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xabb128 <m_mainworker+2816>, mutex=0x0, abstime=0x6edfcbcc) at pthread_cond_wait.c:667
#3  0x002c0b88 in CNotificationSystem::QueueThread() ()
#4  0x009447ec in execute_native_thread_routine ()
#5  0x76bf2494 in start_thread (arg=0x6edfd220) at pthread_create.c:486
#6  0x76aa5578 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 0x6f5fe220 (LWP 9436)):
#0  __waitpid (options=0, stat_loc=0x6f5fcf78, pid=9461) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1  __waitpid (pid=9461, stat_loc=0x6f5fcf78, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
#2  0x002db8ec in dumpstack_gdb(bool) ()
#3  0x002dbeb8 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  0x769e5230 in __GI_abort () at abort.c:79
#7  0x0096d02c in __gnu_cxx::__verbose_terminate_handler() ()
#8  0x008d04cc in __cxxabiv1::__terminate(void (*)()) ()
#9  0x008d0540 in std::terminate() ()
#10 0x008daff0 in __cxa_throw ()
#11 0x00909a48 in std::__throw_invalid_argument(char const*) ()
#12 0x0039ce94 in double __gnu_cxx::__stoa<double, double, char>(double (*)(char const*, char**), char const*, char const*, unsigned int*) ()
#13 0x00407628 in CBuienRadar::GetStationDetails() ()
#14 0x00407e70 in CBuienRadar::GetMeterDetails() ()
#15 0x00408a90 in CBuienRadar::Do_Work() ()
#16 0x009447ec in execute_native_thread_routine ()
#17 0x76bf2494 in start_thread (arg=0x6f5fe220) at pthread_create.c:486
Backtrace stopped: Cannot access memory at address 0x6008955a

Thread 12 (Thread 0x6fdff220 (LWP 9433)):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x0092225c 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  0x0049d360 in CHardwareMonitor::Do_Work() ()
#3  0x009447ec in execute_native_thread_routine ()
#4  0x76bf2494 in start_thread (arg=0x6fdff220) at pthread_create.c:486
#5  0x76aa5578 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 0x709fe220 (LWP 9426)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x709fdbb8, expected=0, futex_word=0xabb688 <m_mainworker+4192>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0x709fdbb8, mutex=0x0, cond=0xabb660 <m_mainworker+4152>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xabb660 <m_mainworker+4152>, mutex=0x0, abstime=0x709fdbb8) at pthread_cond_wait.c:667
#3  0x002af354 in MainWorker::Do_Work_On_Rx_Messages() ()
#4  0x009447ec in execute_native_thread_routine ()
#5  0x76bf2494 in start_thread (arg=0x709fe220) at pthread_create.c:486
#6  0x76aa5578 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 0x711ff220 (LWP 9425)):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x0092225c 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  0x002a9ee4 in MainWorker::Do_Work() ()
#3  0x009447ec in execute_native_thread_routine ()
#4  0x76bf2494 in start_thread (arg=0x711ff220) at pthread_create.c:486
#5  0x76aa5578 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 0x71bfe220 (LWP 9424)):
#0  0x76aa59d0 in epoll_wait (epfd=<optimized out>, events=0x71bfd378, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x003dfa1c in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2  0x003e0fa0 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3  0x00677854 in tcp::server::CTCPServer::Do_Work() ()
#4  0x009447ec in execute_native_thread_routine ()
#5  0x76bf2494 in start_thread (arg=0x71bfe220) at pthread_create.c:486
#6  0x76aa5578 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 0x723ff220 (LWP 9423)):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x0092225c 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  0x002d08f4 in CScheduler::Do_Work() ()
#3  0x009447ec in execute_native_thread_routine ()
#4  0x76bf2494 in start_thread (arg=0x723ff220) at pthread_create.c:486
#5  0x76aa5578 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 0x72d75220 (LWP 9422)):
#0  0x76aa59d0 in epoll_wait (epfd=<optimized out>, events=0x72d74348, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x003dfa1c in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2  0x003e0fa0 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3  0x006bf7ec in http::server::server_base::run() ()
#4  0x0031bc14 in http::server::CWebServer::Do_Work() ()
#5  0x009447ec in execute_native_thread_routine ()
#6  0x76bf2494 in start_thread (arg=0x72d75220) at pthread_create.c:486
#7  0x76aa5578 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 0x73576220 (LWP 9421)):
#0  0x76aa59d0 in epoll_wait (epfd=<optimized out>, events=0x73575378, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x003dfa1c in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
#2  0x003e0fa0 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#3  0x003e79fc in boost::asio::io_context::run() ()
#4  0x009447ec in execute_native_thread_routine ()
#5  0x76bf2494 in start_thread (arg=0x73576220) at pthread_create.c:486
#6  0x76aa5578 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 0x73d77220 (LWP 9420)):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x0092225c 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  0x003b71e4 in CInfluxPush::Do_Work() ()
#3  0x009447ec in execute_native_thread_routine ()
#4  0x76bf2494 in start_thread (arg=0x73d77220) at pthread_create.c:486
Backtrace stopped: Cannot access memory at address 0x78

Thread 4 (Thread 0x74b72220 (LWP 9419)):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x0092225c 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  0x00626940 in Plugins::CPluginSystem::Do_Work() ()
#3  0x009447ec in execute_native_thread_routine ()
#4  0x76bf2494 in start_thread (arg=0x74b72220) at pthread_create.c:486
#5  0x76aa5578 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 0x75373220 (LWP 9418)):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
#1  0x0092225c 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  0x003128dc in CSQLHelper::Do_Work() ()
#3  0x009447ec in execute_native_thread_routine ()
#4  0x76bf2494 in start_thread (arg=0x75373220) at pthread_create.c:486
Backtrace stopped: Cannot access memory at address 0xe

Thread 2 (Thread 0x75b74220 (LWP 9416)):
#0  __GI___nanosleep (remaining=0x75b73bd0, requested_time=0x75b73bd0) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1  __GI___nanosleep (requested_time=0x75b73bd0, remaining=0x75b73bd0) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2  0x00270c24 in sleep_milliseconds(long) ()
#3  0x002dc020 in Do_Watchdog_Work() ()
#4  0x009447ec in execute_native_thread_routine ()
#5  0x76bf2494 in start_thread (arg=0x75b74220) at pthread_create.c:486
#6  0x76aa5578 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 0x76fc6190 (LWP 9415)):
#0  __GI___nanosleep (remaining=0x7ef82f88, requested_time=0x7ef82f88) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1  __GI___nanosleep (requested_time=0x7ef82f88, remaining=0x7ef82f88) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2  0x00270b90 in sleep_seconds(long) ()
#3  0x001eef2c in main ()

Main thread:
#0  __GI___nanosleep (remaining=0x7ef82f88, requested_time=0x7ef82f88) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1  __GI___nanosleep (requested_time=0x7ef82f88, remaining=0x7ef82f88) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2  0x00270b90 in sleep_seconds(long) ()
#3  0x001eef2c in main ()
[Inferior 1 (process 9415) detached]
in this log I see a lot but nothing that I can bake a cookie with.
there is a signal handler at thread 13.
Does this mean anything?
RPI3b+cc2531+p1 meter+watermeter Connectix
User avatar
waltervl
Posts: 5908
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: clean installation but not accessible Domoticz

Post by waltervl »

Did you succeed in getting it running?
I have no idea what could be wrong. What does the normal log say.
How did you install Domoticz, followed the wiki?
Did you remove the Domoticz folder before reinstalling?
Did you change anything else after installation?
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: clean installation but not accessible Domoticz

Post by waaren »

Geertjan wrote: Wednesday 20 January 2021 22:38 there is a signal handler at thread 13.
Does this mean anything?
thread 13 is (in your system) in use for the buienradar plugin. Have you disabled that one?
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
Geertjan
Posts: 4
Joined: Wednesday 20 January 2021 17:18
Target OS: Raspberry Pi / ODroid
Domoticz version: newest
Location: Haarlem, NL
Contact:

Re: clean installation but not accessible Domoticz

Post by Geertjan »

Domoticz is running. Buienradar was the problem indeed, replaced bij OWM
had some trouble to get the old stuff of my Pi.
Now, with everything cleaned up, it is an succes.
thanks for the support!
RPI3b+cc2531+p1 meter+watermeter Connectix
User avatar
Copitano
Posts: 50
Joined: Friday 28 June 2019 1:26
Target OS: Raspberry Pi / ODroid
Domoticz version: 2022.2
Location: NL
Contact:

Re: clean installation but not accessible Domoticz

Post by Copitano »

I've been running into random domoticz crashing multiple times a day for days now, with nothing added or removed. Sometimes Monit manages to restart the domoticz, but that can take an hour or more. For the last time, domoticz went out this afternoon around three o'clock, not to come back either. Tried everything in vain. Recently I bluntly did sudo service domoticz.sh stop and then bluntly deleted the database and replaced it with a copy from this afternoon. Cleared cache and restarted domoticz. After a few attempts it's working again, although I've lost a bunch of data from today. I hope I get at least some day end positions at 00:00:00

this is what I could find in crashlog:

Code: Select all

Thread 10 (Thread 0x718fd220 (LWP 6111)):
#0  __waitpid (options=0, stat_loc=0x718fb2d8, pid=6135) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1  __waitpid (pid=6135, stat_loc=0x718fb2d8, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
#2  0x00109454 in dumpstack_gdb(bool) ()
#3  0x00109a20 in signal_handler(int, siginfo_t*, void*) ()
#4  <signal handler called>
#5  0x76a11f24 in raise () from /lib/arm-linux-gnueabihf/libc.so.6
#6  0x769fd230 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
#7  0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
I have no idea what to do with that and how to end this annoying domoticz behavior (without removing it completely of course) :?: .

Anybody meaningful answers please........... :?:
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest