ZigBeeForDomoticZ fatal signal 11

Xiaomi, Ikea TRÅDFRI, Philips Hue and more.

Moderator: leecollings

Post Reply
t3v3h
Posts: 14
Joined: Tuesday 06 August 2019 9:29
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

ZigBeeForDomoticZ fatal signal 11

Post by t3v3h »

Hi,

I have a fresh install. Only install domoticz (on RPi) and the ZigBeeForDomoticZ plugin.
After a restart have the following errors and the system does not start.
Any idea?

Thanks!

Code: Select all

Current thread 0x6e8ff200 (most recent call first):
  File "/home/rpiadmin/domoticz/plugins/Domoticz-Zigbee/Classes/AdminWidgets.py", line 102 in createStatusWidget
  File "/home/rpiadmin/domoticz/plugins/Domoticz-Zigbee/Classes/AdminWidgets.py", line 31 in __init__
  File "/home/rpiadmin/domoticz/plugins/Domoticz-Zigbee/plugin.py", line 405 in onStart
  File "/home/rpiadmin/domoticz/plugins/Domoticz-Zigbee/plugin.py", line 1658 in onStart
2022-04-28 09:37:51.618  Error: Domoticz(pid:4374, tid:4388('Zigbee')) received fatal signal 11 (Segmentation fault)
2022-04-28 09:37:51.618  Error: siginfo address=0x1116, address=(nil)
2022-04-28 09:37:54.097  Error: Did not find stack frame for thread (LWP 4388)), printing full gdb output:

2022-04-28 09:37:54.097  Error: > [New LWP 4376]
2022-04-28 09:37:54.097  Error: > [New LWP 4377]
2022-04-28 09:37:54.097  Error: > [New LWP 4378]
2022-04-28 09:37:54.097  Error: > [New LWP 4379]
2022-04-28 09:37:54.097  Error: > [New LWP 4380]
2022-04-28 09:37:54.097  Error: > [New LWP 4381]
2022-04-28 09:37:54.097  Error: > [New LWP 4382]
2022-04-28 09:37:54.097  Error: > [New LWP 4383]
2022-04-28 09:37:54.097  Error: > [New LWP 4384]
2022-04-28 09:37:54.097  Error: > [New LWP 4385]
2022-04-28 09:37:54.097  Error: > [New LWP 4386]
2022-04-28 09:37:54.098  Error: > [New LWP 4387]
2022-04-28 09:37:54.098  Error: > [New LWP 4388]
2022-04-28 09:37:54.098  Error: > [New LWP 4389]
2022-04-28 09:37:54.098  Error: > [New LWP 4390]
2022-04-28 09:37:54.098  Error: > [New LWP 4391]
2022-04-28 09:37:54.098  Error: > [New LWP 4392]
2022-04-28 09:37:54.098  Error: > [New LWP 4393]
2022-04-28 09:37:54.098  Error: > [Thread debugging using libthread_db enabled]
2022-04-28 09:37:54.098  Error: > Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
2022-04-28 09:37:54.098  Error: > 0x76873f8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7e8772f8, req@entry=0x7e8772f0, rem=0x7e877308, rem@entry=0x7e877300) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
2022-04-28 09:37:54.098  Error: > 52    ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory.
2022-04-28 09:37:54.098  Error: >   Id   Target Id                                      Frame
2022-04-28 09:37:54.098  Error: > * 1    Thread 0x76ef5240 (LWP 4374) "domoticz"        0x76873f8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7e8772f8, req@entry=0x7e8772f0, rem=0x7e877308, rem@entry=0x7e877300) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
2022-04-28 09:37:54.098  Error: >   2    Thread 0x7586f200 (LWP 4376) "Watchdog"        0x76873f8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7586eb70, req@entry=0x7586eb68, rem=0x7586eb80, rem@entry=0x7586eb78) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
2022-04-28 09:37:54.098  Error: >   3    Thread 0x7506e200 (LWP 4377) "SQLHelper"       syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.099  Error: >   4    Thread 0x7486d200 (LWP 4378) "PluginMgr"       syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.099  Error: >   5    Thread 0x73a32200 (LWP 4379) "InfluxPush"      syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.099  Error: >   6    Thread 0x73231200 (LWP 4380) "Webem_ssncleane" 0x768b363c in epoll_wait (epfd=14, events=0x73230358, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2022-04-28 09:37:54.099  Error: >   7    Thread 0x72a30200 (LWP 4381) "WebServer_8080"  0x768b363c in epoll_wait (epfd=10, events=0x72a2f328, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2022-04-28 09:37:54.099  Error: >   8    Thread 0x720ff200 (LWP 4382) "Webem_ssncleane" 0x768b363c in epoll_wait (epfd=21, events=0x720fe358, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2022-04-28 09:37:54.099  Error: >   9    Thread 0x718fe200 (LWP 4383) "WebServer_443"   0x768b363c in epoll_wait (epfd=17, events=0x718fd328, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2022-04-28 09:37:54.099  Error: >   10   Thread 0x70eff200 (LWP 4384) "Scheduler"       syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.099  Error: >   11   Thread 0x706fe200 (LWP 4385) "TCPServer"       0x768b363c in epoll_wait (epfd=24, events=0x706fd358, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2022-04-28 09:37:54.099  Error: >   12   Thread 0x6fcff200 (LWP 4386) "MainWorker"      syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.099  Error: >   13   Thread 0x6f4fe200 (LWP 4387) "MainWorkerRxMsg" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6f4fdb80, clockid=<optimized out>, expected=0, futex_word=0xa8e3b0 <m_mainworker+3984>) at ../sysdeps/nptl/futex-internal.h:323
2022-04-28 09:37:54.099  Error: >   14   Thread 0x6e8ff200 (LWP 4388) "Zigbee"          0x7687a4d4 in __GI___wait4 (pid=4394, stat_loc=0x6ea25380, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
2022-04-28 09:37:54.099  Error: >   15   Thread 0x6e0fe200 (LWP 4389) "NotificationSys" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6e0fdbb0, clockid=<optimized out>, expected=0, futex_word=0xa8de7c <m_mainworker+2652>) at ../sysdeps/nptl/futex-internal.h:323
2022-04-28 09:37:54.099  Error: >   16   Thread 0x6d6ff200 (LWP 4390) "EventSystem"     syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.099  Error: >   17   Thread 0x6cefe200 (LWP 4391) "EventSystemQueu" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6cefdac0, clockid=<optimized out>, expected=0, futex_word=0xa8d57c <m_mainworker+348>) at ../sysdeps/nptl/futex-internal.h:323
2022-04-28 09:37:54.099  Error: >   18   Thread 0x6c6fd200 (LWP 4392) "Plugin_ASIO"     futex_wait_cancelable (private=0, expected=0, futex_word=0x1817330) at ../sysdeps/nptl/futex-internal.h:186
2022-04-28 09:37:54.100  Error: >   19   Thread 0x6b5ff200 (LWP 4393) "Zigbee"          futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6b5fe248, clockid=<optimized out>, expected=0, futex_word=0x75d6a9e8 <_PyRuntime+256>) at ../sysdeps/nptl/futex-internal.h:323
2022-04-28 09:37:54.100  Error: >
2022-04-28 09:37:54.100  Error: > Thread 19 (Thread 0x6b5ff200 (LWP 4393) "Zigbee"):
2022-04-28 09:37:54.100  Error: > #0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6b5fe248, clockid=<optimized out>, expected=0, futex_word=0x75d6a9e8 <_PyRuntime+256>) at ../sysdeps/nptl/futex-internal.h:323
2022-04-28 09:37:54.100  Error: > #1  __pthread_cond_wait_common (abstime=0x6b5fe248, clockid=<optimized out>, mutex=0x0, cond=0x75d6a9c0 <_PyRuntime+216>) at pthread_cond_wait.c:520
2022-04-28 09:37:54.100  Error: > #2  __pthread_cond_timedwait (cond=0x75d6a9c0 <_PyRuntime+216>, mutex=0x0, abstime=0x6b5fe248) at pthread_cond_wait.c:656
2022-04-28 09:37:54.100  Error: > #3  0x75a22e90 in ?? () from /lib/arm-linux-gnueabihf/libpython3.9.so
2022-04-28 09:37:54.100  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.100  Error: >
2022-04-28 09:37:54.100  Error: > Thread 18 (Thread 0x6c6fd200 (LWP 4392) "Plugin_ASIO"):
2022-04-28 09:37:54.100  Error: > #0  futex_wait_cancelable (private=0, expected=0, futex_word=0x1817330) at ../sysdeps/nptl/futex-internal.h:186
2022-04-28 09:37:54.100  Error: > #1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x0, cond=0x1817308) at pthread_cond_wait.c:508
2022-04-28 09:37:54.100  Error: > #2  __pthread_cond_wait (cond=0x1817308, mutex=0x0) at pthread_cond_wait.c:638
2022-04-28 09:37:54.100  Error: > #3  0x003d727c in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2022-04-28 09:37:54.100  Error: > #4  0x00683e74 in Plugins::BoostWorkers() ()
2022-04-28 09:37:54.101  Error: > #5  0x0077d374 in thread_proxy ()
2022-04-28 09:37:54.101  Error: > #6  0x769ef300 in start_thread (arg=0x6c6fd200) at pthread_create.c:477
2022-04-28 09:37:54.101  Error: > #7  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.101  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.101  Error: >
2022-04-28 09:37:54.101  Error: > Thread 17 (Thread 0x6cefe200 (LWP 4391) "EventSystemQueu"):
2022-04-28 09:37:54.101  Error: > #0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6cefdac0, clockid=<optimized out>, expected=0, futex_word=0xa8d57c <m_mainworker+348>) at ../sysdeps/nptl/futex-internal.h:323
2022-04-28 09:37:54.101  Error: > #1  __pthread_cond_wait_common (abstime=0x6cefdac0, clockid=<optimized out>, mutex=0x6cefda60, cond=0xa8d550 <m_mainworker+304>) at pthread_cond_wait.c:520
2022-04-28 09:37:54.101  Error: > #2  __pthread_cond_timedwait (cond=0xa8d550 <m_mainworker+304>, mutex=0x6cefda60, abstime=0x6cefdac0) at pthread_cond_wait.c:656
2022-04-28 09:37:54.101  Error: > #3  0x00213404 in CEventSystem::EventQueueThread() ()
2022-04-28 09:37:54.101  Error: > #4  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.101  Error: > #5  0x769ef300 in start_thread (arg=0x6cefe200) at pthread_create.c:477
2022-04-28 09:37:54.101  Error: > #6  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.101  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.101  Error: >
2022-04-28 09:37:54.101  Error: > Thread 16 (Thread 0x6d6ff200 (LWP 4390) "EventSystem"):
2022-04-28 09:37:54.102  Error: > #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.102  Error: > #1  0x008e41a4 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> >) ()
2022-04-28 09:37:54.102  Error: > #2  0x0020a438 in CEventSystem::Do_Work() ()
2022-04-28 09:37:54.102  Error: > #3  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.102  Error: > #4  0x769ef300 in start_thread (arg=0x6d6ff200) at pthread_create.c:477
2022-04-28 09:37:54.102  Error: > #5  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.102  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.102  Error: >
2022-04-28 09:37:54.102  Error: > Thread 15 (Thread 0x6e0fe200 (LWP 4389) "NotificationSys"):
2022-04-28 09:37:54.102  Error: > #0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6e0fdbb0, clockid=<optimized out>, expected=0, futex_word=0xa8de7c <m_mainworker+2652>) at ../sysdeps/nptl/futex-internal.h:323
2022-04-28 09:37:54.102  Error: > #1  __pthread_cond_wait_common (abstime=0x6e0fdbb0, clockid=<optimized out>, mutex=0x6e0fdb58, cond=0xa8de50 <m_mainworker+2608>) at pthread_cond_wait.c:520
2022-04-28 09:37:54.102  Error: > #2  __pthread_cond_timedwait (cond=0xa8de50 <m_mainworker+2608>, mutex=0x6e0fdb58, abstime=0x6e0fdbb0) at pthread_cond_wait.c:656
2022-04-28 09:37:54.102  Error: > #3  0x00277298 in CNotificationSystem::QueueThread() ()
2022-04-28 09:37:54.102  Error: > #4  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.102  Error: > #5  0x769ef300 in start_thread (arg=0x6e0fe200) at pthread_create.c:477
2022-04-28 09:37:54.102  Error: > #6  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.102  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.103  Error: >
2022-04-28 09:37:54.103  Error: > Thread 14 (Thread 0x6e8ff200 (LWP 4388) "Zigbee"):
2022-04-28 09:37:54.103  Error: > #0  0x7687a4d4 in __GI___wait4 (pid=4394, stat_loc=0x6ea25380, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
2022-04-28 09:37:54.103  Error: > #1  0x0029121c in dumpstack_gdb(bool) ()
2022-04-28 09:37:54.103  Error: > #2  0x002917e8 in signal_handler(int, siginfo_t*, void*) ()
2022-04-28 09:37:54.103  Error: > #3  <signal handler called>
2022-04-28 09:37:54.103  Error: > #4  raise (sig=11) at ../sysdeps/unix/sysv/linux/raise.c:50
2022-04-28 09:37:54.103  Error: > #5  <signal handler called>
2022-04-28 09:37:54.103  Error: > #6  0x00000014 in ?? ()
2022-04-28 09:37:54.103  Error: > #7  0x758f247c in _PyEval_EvalFrameDefault () from /lib/arm-linux-gnueabihf/libpython3.9.so
2022-04-28 09:37:54.103  Error: > #8  0x6b92bdd0 in ?? ()
2022-04-28 09:37:54.103  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.103  Error: >
2022-04-28 09:37:54.103  Error: > Thread 13 (Thread 0x6f4fe200 (LWP 4387) "MainWorkerRxMsg"):
2022-04-28 09:37:54.103  Error: > #0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6f4fdb80, clockid=<optimized out>, expected=0, futex_word=0xa8e3b0 <m_mainworker+3984>) at ../sysdeps/nptl/futex-internal.h:323
2022-04-28 09:37:54.104  Error: > #1  __pthread_cond_wait_common (abstime=0x6f4fdb80, clockid=<optimized out>, mutex=0x769eaa1c, cond=0xa8e388 <m_mainworker+3944>) at pthread_cond_wait.c:520
2022-04-28 09:37:54.104  Error: > #2  __pthread_cond_timedwait (cond=0xa8e388 <m_mainworker+3944>, mutex=0x769eaa1c, abstime=0x6f4fdb80) at pthread_cond_wait.c:656
2022-04-28 09:37:54.104  Error: > #3  0x00263724 in MainWorker::Do_Work_On_Rx_Messages() ()
2022-04-28 09:37:54.104  Error: > #4  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.104  Error: > #5  0x769ef300 in start_thread (arg=0x6f4fe200) at pthread_create.c:477
2022-04-28 09:37:54.104  Error: > #6  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.104  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.104  Error: >
2022-04-28 09:37:54.104  Error: > Thread 12 (Thread 0x6fcff200 (LWP 4386) "MainWorker"):
2022-04-28 09:37:54.104  Error: > #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.104  Error: > #1  0x008e41a4 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> >) ()
2022-04-28 09:37:54.104  Error: > #2  0x0025f5fc in MainWorker::Do_Work() ()
2022-04-28 09:37:54.104  Error: > #3  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.104  Error: > #4  0x769ef300 in start_thread (arg=0x6fcff200) at pthread_create.c:477
2022-04-28 09:37:54.104  Error: > #5  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.104  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.105  Error: >
2022-04-28 09:37:54.105  Error: > Thread 11 (Thread 0x706fe200 (LWP 4385) "TCPServer"):
2022-04-28 09:37:54.105  Error: > #0  0x768b363c in epoll_wait (epfd=24, events=0x706fd358, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2022-04-28 09:37:54.105  Error: > #1  0x003d519c in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2022-04-28 09:37:54.105  Error: > #2  0x003d7194 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2022-04-28 09:37:54.105  Error: > #3  0x006e0d80 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() ()
2022-04-28 09:37:54.105  Error: > #4  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.105  Error: > #5  0x769ef300 in start_thread (arg=0x706fe200) at pthread_create.c:477
2022-04-28 09:37:54.105  Error: > #6  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.105  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.105  Error: >
2022-04-28 09:37:54.105  Error: > Thread 10 (Thread 0x70eff200 (LWP 4384) "Scheduler"):
2022-04-28 09:37:54.105  Error: > #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.105  Error: > #1  0x008e41a4 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> >) ()
2022-04-28 09:37:54.105  Error: > #2  0x00288690 in CScheduler::Do_Work() ()
2022-04-28 09:37:54.105  Error: > #3  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.106  Error: > #4  0x769ef300 in start_thread (arg=0x70eff200) at pthread_create.c:477
2022-04-28 09:37:54.106  Error: > #5  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.106  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.106  Error: >
2022-04-28 09:37:54.106  Error: > Thread 9 (Thread 0x718fe200 (LWP 4383) "WebServer_443"):
2022-04-28 09:37:54.106  Error: > #0  0x768b363c in epoll_wait (epfd=17, events=0x718fd328, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2022-04-28 09:37:54.106  Error: > #1  0x003d519c in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2022-04-28 09:37:54.106  Error: > #2  0x003d7194 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2022-04-28 09:37:54.106  Error: > #3  0x0072bc88 in http::server::server_base::run() ()
2022-04-28 09:37:54.106  Error: > #4  0x002d9bfc 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()#280}> > >::_M_run() ()
2022-04-28 09:37:54.106  Error: > #5  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.106  Error: > #6  0x769ef300 in start_thread (arg=0x718fe200) at pthread_create.c:477
2022-04-28 09:37:54.106  Error: > #7  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.106  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.106  Error: >
2022-04-28 09:37:54.106  Error: > Thread 8 (Thread 0x720ff200 (LWP 4382) "Webem_ssncleane"):
2022-04-28 09:37:54.107  Error: > #0  0x768b363c in epoll_wait (epfd=21, events=0x720fe358, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2022-04-28 09:37:54.107  Error: > #1  0x003d519c in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2022-04-28 09:37:54.107  Error: > #2  0x003d7194 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2022-04-28 09:37:54.107  Error: > #3  0x006fc0b4 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() ()
2022-04-28 09:37:54.107  Error: > #4  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.107  Error: > #5  0x769ef300 in start_thread (arg=0x720ff200) at pthread_create.c:477
2022-04-28 09:37:54.107  Error: > #6  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.107  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.107  Error: >
2022-04-28 09:37:54.107  Error: > Thread 7 (Thread 0x72a30200 (LWP 4381) "WebServer_8080"):
2022-04-28 09:37:54.107  Error: > #0  0x768b363c in epoll_wait (epfd=10, events=0x72a2f328, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2022-04-28 09:37:54.107  Error: > #1  0x003d519c in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2022-04-28 09:37:54.107  Error: > #2  0x003d7194 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2022-04-28 09:37:54.107  Error: > #3  0x0072bc88 in http::server::server_base::run() ()
2022-04-28 09:37:54.107  Error: > #4  0x002d9bfc 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()#280}> > >::_M_run() ()
2022-04-28 09:37:54.107  Error: > #5  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.107  Error: > #6  0x769ef300 in start_thread (arg=0x72a30200) at pthread_create.c:477
2022-04-28 09:37:54.108  Error: > #7  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.108  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.108  Error: >
2022-04-28 09:37:54.108  Error: > Thread 6 (Thread 0x73231200 (LWP 4380) "Webem_ssncleane"):
2022-04-28 09:37:54.108  Error: > #0  0x768b363c in epoll_wait (epfd=14, events=0x73230358, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2022-04-28 09:37:54.108  Error: > #1  0x003d519c in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2022-04-28 09:37:54.108  Error: > #2  0x003d7194 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2022-04-28 09:37:54.108  Error: > #3  0x006fc0b4 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() ()
2022-04-28 09:37:54.108  Error: > #4  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.108  Error: > #5  0x769ef300 in start_thread (arg=0x73231200) at pthread_create.c:477
2022-04-28 09:37:54.108  Error: > #6  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.108  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.108  Error: >
2022-04-28 09:37:54.108  Error: > Thread 5 (Thread 0x73a32200 (LWP 4379) "InfluxPush"):
2022-04-28 09:37:54.108  Error: > #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.108  Error: > #1  0x008e41a4 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> >) ()
2022-04-28 09:37:54.108  Error: > #2  0x00393ed0 in CInfluxPush::Do_Work() ()
2022-04-28 09:37:54.108  Error: > #3  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.108  Error: > #4  0x769ef300 in start_thread (arg=0x73a32200) at pthread_create.c:477
2022-04-28 09:37:54.108  Error: > #5  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.108  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.108  Error: >
2022-04-28 09:37:54.108  Error: > Thread 4 (Thread 0x7486d200 (LWP 4378) "PluginMgr"):
2022-04-28 09:37:54.108  Error: > #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.108  Error: > #1  0x008e41a4 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> >) ()
2022-04-28 09:37:54.108  Error: > #2  0x00684684 in Plugins::CPluginSystem::Do_Work() ()
2022-04-28 09:37:54.108  Error: > #3  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.108  Error: > #4  0x769ef300 in start_thread (arg=0x7486d200) at pthread_create.c:477
2022-04-28 09:37:54.108  Error: > #5  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.109  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.109  Error: >
2022-04-28 09:37:54.109  Error: > Thread 3 (Thread 0x7506e200 (LWP 4377) "SQLHelper"):
2022-04-28 09:37:54.109  Error: > #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2022-04-28 09:37:54.109  Error: > #1  0x008e41a4 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> >) ()
2022-04-28 09:37:54.109  Error: > #2  0x002a8698 in CSQLHelper::Do_Work() ()
2022-04-28 09:37:54.109  Error: > #3  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.109  Error: > #4  0x769ef300 in start_thread (arg=0x7506e200) at pthread_create.c:477
2022-04-28 09:37:54.109  Error: > #5  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.109  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.109  Error: >
2022-04-28 09:37:54.109  Error: > Thread 2 (Thread 0x7586f200 (LWP 4376) "Watchdog"):
2022-04-28 09:37:54.109  Error: > #0  0x76873f8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7586eb70, req@entry=0x7586eb68, rem=0x7586eb80, rem@entry=0x7586eb78) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
2022-04-28 09:37:54.109  Error: > #1  0x76874080 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=<optimized out>, rem=0x7586ebb0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:92
2022-04-28 09:37:54.109  Error: > #2  0x7687a830 in __GI___nanosleep (requested_time=<optimized out>, remaining=<optimized out>) at nanosleep.c:27
2022-04-28 09:37:54.109  Error: > #3  0x00224e2c in sleep_milliseconds(long) ()
2022-04-28 09:37:54.109  Error: > #4  0x00291950 in Do_Watchdog_Work() ()
2022-04-28 09:37:54.109  Error: > #5  0x00906734 in execute_native_thread_routine ()
2022-04-28 09:37:54.109  Error: > #6  0x769ef300 in start_thread (arg=0x7586f200) at pthread_create.c:477
2022-04-28 09:37:54.109  Error: > #7  0x768b3208 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2022-04-28 09:37:54.109  Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2022-04-28 09:37:54.109  Error: >
2022-04-28 09:37:54.109  Error: > Thread 1 (Thread 0x76ef5240 (LWP 4374) "domoticz"):
2022-04-28 09:37:54.109  Error: > #0  0x76873f8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7e8772f8, req@entry=0x7e8772f0, rem=0x7e877308, rem@entry=0x7e877300) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
2022-04-28 09:37:54.109  Error: > #1  0x76874080 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=<optimized out>, rem=0x7e877338) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:92
2022-04-28 09:37:54.109  Error: > #2  0x7687a830 in __GI___nanosleep (requested_time=<optimized out>, remaining=<optimized out>) at nanosleep.c:27
2022-04-28 09:37:54.109  Error: > #3  0x00224d98 in sleep_seconds(long) ()
2022-04-28 09:37:54.109  Error: > #4  0x001af740 in main ()
2022-04-28 09:37:54.110  Error: >
2022-04-28 09:37:54.110  Error: > Main thread:
2022-04-28 09:37:54.110  Error: > #0  0x76873f8c in __GI___clock_nanosleep_time64 (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7e8772f8, req@entry=0x7e8772f0, rem=0x7e877308, rem@entry=0x7e877300) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:52
2022-04-28 09:37:54.110  Error: > #1  0x76874080 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=<optimized out>, rem=0x7e877338) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:92
2022-04-28 09:37:54.110  Error: > #2  0x7687a830 in __GI___nanosleep (requested_time=<optimized out>, remaining=<optimized out>) at nanosleep.c:27
2022-04-28 09:37:54.110  Error: > #3  0x00224d98 in sleep_seconds(long) ()
2022-04-28 09:37:54.110  Error: > #4  0x001af740 in main ()
2022-04-28 09:37:54.110  Error: > [Inferior 1 (process 4374) detached]

pipiche
Posts: 2005
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by pipiche »

Please provides Domoticz version, Python version and OS version.
If you are on Bulleseye you must use the latest Domotciz from development branch as the Stable 2022.1 is not compatible with the Python3.9 embedded with Bulleseye
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
t3v3h
Posts: 14
Joined: Tuesday 06 August 2019 9:29
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by t3v3h »

Thank you for your quick response!

OS: Raspbian GNU/Linux 11 (bullseye)
Domoticz: 2022.01
Python: 3.9.2

So, do I need a different Python?

Thanks!
pipiche
Posts: 2005
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by pipiche »

yes, you need to downgrade to python3.8 if you want to stay with Domoticz 2022.1.
Otherwise you need to get the Domoticz latest beta version
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
t3v3h
Posts: 14
Joined: Tuesday 06 August 2019 9:29
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by t3v3h »

Thanks, working on downgrade python or install older version from scratch.. not easy :D
t3v3h
Posts: 14
Joined: Tuesday 06 August 2019 9:29
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by t3v3h »

I could install it and add the hardware as well.
There is no utility sensor. So have no idea how to add devices. Bit different than the Zigbee2MQTT :D
pipiche
Posts: 2005
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by pipiche »

Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
pipiche
Posts: 2005
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by pipiche »

Usally you get access to the Plugin WebUI ( accessible on port 9440 by default ), and from that you get the plugin Dashboard, you can go to the Provisioning menu and enable provisioning of a new device
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
t3v3h
Posts: 14
Joined: Tuesday 06 August 2019 9:29
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by t3v3h »

cannot reach that WebUI. I use port 9440 :?
pipiche
Posts: 2005
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by pipiche »

check the logs: domoticz/plugins/Domoticz-Zigbee/Logs

did you correctly set the Coordinator model . Zigate or Texas or whatever you use

Make sure the 1st time you run it the Initialize coordinator is set
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
t3v3h
Posts: 14
Joined: Tuesday 06 August 2019 9:29
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by t3v3h »

I have Sonoff USB dongle and I selected the Texas.
1st run I initialized the coordinator.

Find some error in the log:

Code: Select all

2022-04-28 13:00:59,100 ERROR   : [       MainThread] [ 70] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:00:59,103 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:09,073 ERROR   : [       MainThread] [ 80] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:01:09,077 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:19,096 ERROR   : [       MainThread] [ 90] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:01:19,101 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:29,069 ERROR   : [       MainThread] [100] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:01:29,074 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:39,091 ERROR   : [       MainThread] [110] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:01:39,097 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:49,065 ERROR   : [       MainThread] [120] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:01:49,072 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.

and also some interesting info:

Code: Select all

2022-04-28 13:01:50,168 INFO    : [       MainThread] onStop calling (1) domoticzDb DeviceStatus closed
2022-04-28 13:01:50,169 INFO    : [       MainThread] onStop calling (2) domoticzDb Hardware closed
2022-04-28 13:01:50,170 INFO    : [       MainThread] onStop calling (3) Transport off
2022-04-28 13:01:50,171 INFO    : [       MainThread] onStop calling (4) WebServer off
pipiche
Posts: 2005
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by pipiche »

I need the early log, can you drop the log file here ?
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
t3v3h
Posts: 14
Joined: Tuesday 06 August 2019 9:29
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by t3v3h »

it is a bit short.. isn't it?

Code: Select all

2022-04-28 12:59:50,092 INFO    : [       MainThread] Zigate plugin stable6-6.1.004 started
2022-04-28 12:59:50,121 INFO    : [       MainThread] Plugin Database: DeviceList-2.txt
2022-04-28 12:59:50,130 INFO    : [       MainThread] DeviceConf loaded - 23 confs loaded
2022-04-28 12:59:50,340 INFO    : [       MainThread] DeviceConf loaded - 334 confs loaded
2022-04-28 12:59:50,341 INFO    : [       MainThread] load ListOfDevice
2022-04-28 12:59:50,343 INFO    : [       MainThread] Transport mode: ZigpyZNP
2022-04-28 13:00:59,100 ERROR   : [       MainThread] [ 70] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:00:59,103 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:09,073 ERROR   : [       MainThread] [ 80] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:01:09,077 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:19,096 ERROR   : [       MainThread] [ 90] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:01:19,101 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:29,069 ERROR   : [       MainThread] [100] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:01:29,074 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:39,091 ERROR   : [       MainThread] [110] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:01:39,097 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:49,065 ERROR   : [       MainThread] [120] I have hard time to get Coordinator Version. Mostlikly there is a communication issue
2022-04-28 13:01:49,072 ERROR   : [       MainThread] [   ] Stop the plugin and check the Coordinator connectivity.
2022-04-28 13:01:50,073 INFO    : [       MainThread] Is GC enabled: True
2022-04-28 13:01:50,076 INFO    : [       MainThread] DomoticzVersion: 2022.1
2022-04-28 13:01:50,077 INFO    : [       MainThread] Parameters[HardwareID] 2
2022-04-28 13:01:50,078 INFO    : [       MainThread] Parameters[HomeFolder] /home/rpiadmin/domoticz/plugins/Domoticz-Zigbee/
2022-04-28 13:01:50,079 INFO    : [       MainThread] Parameters[StartupFolder] /home/rpiadmin/domoticz/
2022-04-28 13:01:50,081 INFO    : [       MainThread] Parameters[UserDataFolder] /home/rpiadmin/domoticz/
2022-04-28 13:01:50,082 INFO    : [       MainThread] Parameters[WebRoot] 
2022-04-28 13:01:50,083 INFO    : [       MainThread] Parameters[Database] /home/rpiadmin/domoticz/domoticz.db
2022-04-28 13:01:50,084 INFO    : [       MainThread] Parameters[Language] en
2022-04-28 13:01:50,085 INFO    : [       MainThread] Parameters[Version] 6.2
2022-04-28 13:01:50,086 INFO    : [       MainThread] Parameters[Author] pipiche38
2022-04-28 13:01:50,087 INFO    : [       MainThread] Parameters[Name] Zigbee
2022-04-28 13:01:50,088 INFO    : [       MainThread] Parameters[Address] 0.0.0.0
2022-04-28 13:01:50,088 INFO    : [       MainThread] Parameters[Port] 9999
2022-04-28 13:01:50,089 INFO    : [       MainThread] Parameters[SerialPort] /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_ea1d3e0b0660ec11b2ee365f25bfaa52-if00-port0
2022-04-28 13:01:50,090 INFO    : [       MainThread] Parameters[Username] 
2022-04-28 13:01:50,091 INFO    : [       MainThread] Parameters[Password] 
2022-04-28 13:01:50,092 INFO    : [       MainThread] Parameters[Key] Zigate
2022-04-28 13:01:50,093 INFO    : [       MainThread] Parameters[Mode1] ZigpyZNP
2022-04-28 13:01:50,094 INFO    : [       MainThread] Parameters[Mode2] USB
2022-04-28 13:01:50,095 INFO    : [       MainThread] Parameters[Mode3] True
2022-04-28 13:01:50,096 INFO    : [       MainThread] Parameters[Mode4] 9440
2022-04-28 13:01:50,097 INFO    : [       MainThread] Parameters[Mode5] 
2022-04-28 13:01:50,097 INFO    : [       MainThread] Parameters[Mode6] 2
2022-04-28 13:01:50,098 INFO    : [       MainThread] Parameters[DomoticzVersion] 2022.1
2022-04-28 13:01:50,100 INFO    : [       MainThread] Parameters[DomoticzHash] c9526851b
2022-04-28 13:01:50,101 INFO    : [       MainThread] Parameters[DomoticzBuildTime] 2022-01-31 08:34:32
2022-04-28 13:01:50,102 INFO    : [       MainThread] Parameters[PluginBranch] stable6
2022-04-28 13:01:50,103 INFO    : [       MainThread] Parameters[PluginVersion] 6.1.004
2022-04-28 13:01:50,104 INFO    : [       MainThread] Parameters[TimeStamp] 0
2022-04-28 13:01:50,105 INFO    : [       MainThread] Parameters[available] None
2022-04-28 13:01:50,107 INFO    : [       MainThread] Parameters[available-firmMajor] None
2022-04-28 13:01:50,108 INFO    : [       MainThread] Parameters[available-firmMinor] None
2022-04-28 13:01:50,108 INFO    : [       MainThread] Parameters[FirmwareVersion] None
2022-04-28 13:01:50,109 INFO    : [       MainThread] Parameters[FirmwareUpdate] None
2022-04-28 13:01:50,110 INFO    : [       MainThread] Parameters[PluginUpdate] None
2022-04-28 13:01:50,111 INFO    : [       MainThread] Parameters[LogLevel] (7,)
2022-04-28 13:01:50,112 INFO    : [       MainThread] Debug: 2
2022-04-28 13:01:50,113 INFO    : [       MainThread] Python Version - 3.8.12 (default, Apr 28 2022, 12:40:36) 
[GCC 10.2.1 20210110]
2022-04-28 13:01:50,114 INFO    : [       MainThread] DomoticzVersion: 2022.1
2022-04-28 13:01:50,115 INFO    : [       MainThread] DomoticzHash: c9526851b
2022-04-28 13:01:50,116 INFO    : [       MainThread] DomoticzBuildTime: 2022-01-31 08:34:32
2022-04-28 13:01:50,117 INFO    : [       MainThread] Startup Folder: /home/rpiadmin/domoticz/
2022-04-28 13:01:50,117 INFO    : [       MainThread] Home Folder: /home/rpiadmin/domoticz/plugins/Domoticz-Zigbee/
2022-04-28 13:01:50,118 INFO    : [       MainThread] User Data Folder: /home/rpiadmin/domoticz/
2022-04-28 13:01:50,119 INFO    : [       MainThread] Web Root Folder: 
2022-04-28 13:01:50,120 INFO    : [       MainThread] Database: /home/rpiadmin/domoticz/domoticz.db
2022-04-28 13:01:50,121 INFO    : [       MainThread] Opening DomoticzDB in raw
2022-04-28 13:01:50,121 INFO    : [       MainThread]    - DeviceStatus table
2022-04-28 13:01:50,168 INFO    : [       MainThread] onStop called
2022-04-28 13:01:50,168 INFO    : [       MainThread] onStop calling (1) domoticzDb DeviceStatus closed
2022-04-28 13:01:50,169 INFO    : [       MainThread] onStop calling (2) domoticzDb Hardware closed
2022-04-28 13:01:50,170 INFO    : [       MainThread] onStop calling (3) Transport off
2022-04-28 13:01:50,171 INFO    : [       MainThread] onStop calling (4) WebServer off
2022-04-28 13:01:50,172 INFO    : [       MainThread] onStop called (4) WebServer off
2022-04-28 13:01:50,172 INFO    : [       MainThread] onStop calling (5) Plugin Database saved
2022-04-28 13:01:50,174 INFO    : [       MainThread] onStop called (5) Plugin Database saved
pipiche
Posts: 2005
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by pipiche »

If it is a PI4, make sure that it is connected on a USB2 and not USB3 port
If you have an SSD disk make sure that the

Can you try to add the following lines in the file /home/rpiadmin/domoticz/plugins/Domoticz-Zigbee/Conf/PluginConf-02.json

"debugTransportZigpy": 1,
"debugTransportZigpyZNP": 1,


did you also do the

sudo pip3 install -r requirements.txt
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
pipiche
Posts: 2005
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by pipiche »

You can also try what is describe here, just to make sure that the communication is working well

viewtopic.php?p=287371#p287371
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
t3v3h
Posts: 14
Joined: Tuesday 06 August 2019 9:29
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: ZigBeeForDomoticZ fatal signal 11

Post by t3v3h »

I have reinstalled tho whole system and now everíthing is working like a charm!
Thank you for your help and congrats for the great developement!
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest