Page 1 of 1

Debug and Stack trace

Posted: Sunday 03 November 2019 19:07
by pipiche
I have a user who is getting randomly such message and a restart of Domoticz is required.

He is using the latest version of Domoticz, how can we debug that ?

Code: Select all

2019-11-03 16:50:35.064  (Zigate) UpdateDevice - (   T° Buanderie) 0:23.8;57.3;1;994.8;4
2019-11-03 16:50:35.134  (Zigate) UpdateDevice - (   T° Buanderie) 0:23.8;55.9;1;994.8;4
2019-11-03 16:50:35.208  Error: Domoticz(pid:12260, tid:12269('PluginMgr')) received fatal signal 4 (Illegal instruction)
2019-11-03 16:50:35.208  Error: siginfo address=0x2fe4, address=0xb6de7fc0
2019-11-03 16:51:00.686  Status: EventSystem: Script event triggered: Time
2019-11-03 16:51:00.922  Error: Thread 4 (Thread 0xb4d56220 (LWP 12269)):
2019-11-03 16:51:00.922  Error: #0  _waitpid (options=0, statloc=0xb4d538b0, pid=17175) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2019-11-03 16:51:00.922  Error: #1  _waitpid (pid=17175, statloc=0xb4d538b0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
2019-11-03 16:51:00.922  Error: #2  0x00116d0c in dumpstack_gdb(bool) ()
2019-11-03 16:51:00.923  Error: #3  0x00117300 in signal_handler(int, siginfo_t*, void*) ()
2019-11-03 16:51:00.923  Error: #4  <signal handler called>
2019-11-03 16:51:00.923  Error: #5  raise (sig=4) at ../sysdeps/unix/sysv/linux/raise.c:50
2019-11-03 16:51:00.923  Error: #6  <signal handler called>
2019-11-03 16:51:00.923  Error: #7  0x00657000 in ecp_nistz256_precomputed ()
2019-11-03 16:51:00.924  Error: #8  0x00512000 in http::server::CWebsocketHandler::Handle(std::_cxx11::basicstring<char, std::char_traits<char>, std::allocator<char> > const&, bool) ()
2019-11-03 16:51:00.924  Error: #9  0x0050ed5c in http::server::CWebsocketHandler::OnDeviceChanged(unsigned long long) ()
2019-11-03 16:51:00.924  Error: #10 0x0020b1e8 in CWebSocketPush::OnDeviceReceived(int, unsigned long long, std::_cxx11::basicstring<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*) ()
2019-11-03 16:51:00.924  Error: #11 0x000fc394 in boost::signals2::detail::signal_impl<void (int, unsigned long long, std::_cxx11::basicstring<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*), boost::signals2::optional_last_value<void>, int, std::less<int>, boost::function<void (int, unsigned long long, std::_cxx11::basicstring<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*)>, boost::function<void (boost::signals2::connection const&, int, unsigned long long, std::_cxx11::basicstring<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*)>, boost::signals2::mutex>::operator()(int, unsigned long long, std::_cxx11::basicstring<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*) ()
2019-11-03 16:51:00.925  Error: #12 0x00495bf0 in Plugins::CDevice_update(Plugins::CDevice*, object*, object*) ()
2019-11-03 16:51:00.925  Error: #13 0xb602aaf8 in PyMethodDefRawFastCallKeywords () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-03 16:51:00.925  Error: #14 0xb602ba54 in PyCFunctionFastCallKeywords () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-03 16:51:00.925  Error: #15 0xb5e2b1d4 in PyEvalEvalFrameDefault () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-03 16:51:00.925  Error: #16 0xb5f5d298 in PyEvalEvalCodeWithName () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-03 16:51:00.926  Error: #17 0xb602b0f0 in PyFunctionFastCallKeywords () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-03 16:51:00.926  Error: #18 0xb5e28f9c in PyEvalEvalFrameDefault () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-03 16:51:00.926  Error: #19 0xb5f5d298 in PyEvalEvalCodeWithName () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-03 16:51:00.926  Error: #20 0xb602b0f0 in PyFunctionFastCallKeywords () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-03 16:51:00.926  Error: #21 0xb5e28f9c in PyEvalEvalFrameDefault () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-03 16:51:00.927  Error: #22 0xb5e2cdc8 in ?? () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so

Re: Debug and Stack trace

Posted: Monday 04 November 2019 8:53
by Ricky74
Unfortunately, I'm the poor user who has regularly this crash.
This morning I had new crash with this message :

2019-11-04 07:11:51.381 (Zigate) UpdateDevice - (Zigate - Temp+Hum-00158d000232761a-01) 0:18.0;62.5;1
2019-11-04 07:11:51.408 (Zigate) UpdateDevice - (Zigate - Temp-00158d000232761a-01) 18.0:18.0
2019-11-04 07:11:51.432 Error: Domoticz(pid:19050, tid:19056('PluginMgr')) received fatal signal 11 (Segmentation fault)
2019-11-04 07:11:51.432 Error: siginfo address=0x4a6a, address=0xb6dfcfc0
2019-11-04 07:12:15.644 Status: EventSystem: Script event triggered: Time
2019-11-04 07:12:15.886 Error: Thread 4 (Thread 0xb4d6b220 (LWP 19056)):
2019-11-04 07:12:15.886 Error: #0 __waitpid (options=0, stat_loc=0xb4d68ad8, pid=25841) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2019-11-04 07:12:15.886 Error: #1 __waitpid (pid=25841, stat_loc=0xb4d68ad8, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
2019-11-04 07:12:15.887 Error: #2 0x003094c4 in dumpstack_gdb(bool) ()
2019-11-04 07:12:15.887 Error: #3 0x00309ab8 in signal_handler(int, siginfo_t*, void*) ()
2019-11-04 07:12:15.887 Error: #4 <signal handler called>
2019-11-04 07:12:15.887 Error: #5 raise (sig=11) at ../sysdeps/unix/sysv/linux/raise.c:50
2019-11-04 07:12:15.888 Error: #6 <signal handler called>
2019-11-04 07:12:15.888 Error: #7 0x0070f370 in http::server::CWebsocketHandler::Handle(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool) ()
2019-11-04 07:12:15.888 Error: #8 0x0070c05c in http::server::CWebsocketHandler::OnDeviceChanged(unsigned long long) ()
2019-11-04 07:12:15.888 Error: #9 0x003fceb0 in CWebSocketPush::OnDeviceReceived(int, unsigned long long, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*) ()
2019-11-04 07:12:15.889 Error: #10 0x002edadc in boost::signals2::detail::signal_impl<void (int, unsigned long long, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*), boost::signals2::optional_last_value<void>, int, std::less<int>, boost::function<void (int, unsigned long long, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*)>, boost::function<void (boost::signals2::connection const&, int, unsigned long long, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*)>, boost::signals2::mutex>::operator()(int, unsigned long long, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*) ()
2019-11-04 07:12:15.889 Error: #11 0x00692f80 in Plugins::CDevice_update(Plugins::CDevice*, _object*, _object*) ()
2019-11-04 07:12:15.889 Error: #12 0xb603faf8 in _PyMethodDef_RawFastCallKeywords () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-04 07:12:15.890 Error: #13 0xb6040a54 in _PyCFunction_FastCallKeywords () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-04 07:12:15.890 Error: #14 0xb5e401d4 in _PyEval_EvalFrameDefault () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-04 07:12:15.890 Error: #15 0xb5f72298 in _PyEval_EvalCodeWithName () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-04 07:12:15.890 Error: #16 0xb60400f0 in _PyFunction_FastCallKeywords () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-04 07:12:15.890 Error: #17 0xb5e3df9c in _PyEval_EvalFrameDefault () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-04 07:12:15.891 Error: #18 0xb5f72298 in _PyEval_EvalCodeWithName () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-04 07:12:15.891 Error: #19 0xb60400f0 in _PyFunction_FastCallKeywords () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-04 07:12:15.891 Error: #20 0xb5e3df9c in _PyEval_EvalFrameDefault () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-04 07:12:15.891 Error: #21 0xb5e41dc8 in ?? () from /usr/lib/arm-linux-gnueabihf/libpython3.7m.so
2019-11-04 07:19:03.871 Status: Domoticz V4.11455 (c)2012-2019 GizMoCuz

Who can help me please ???

Re: Debug and Stack trace

Posted: Monday 04 November 2019 10:19
by EddyG
It looks like you are using the plugin manager, or is that falsely understood by me?
Worth a try. Remove the plugin manager and restart again.

Re: Debug and Stack trace

Posted: Monday 04 November 2019 10:29
by pipiche
EddyG wrote: Monday 04 November 2019 10:19 It looks like you are using the plugin manager, or is that falsely understood by me?
Worth a try. Remove the plugin manager and restart again.
I don't known what you mean by Plugin Manager. Here it is related to the Python Plugin Framework

Re: Debug and Stack trace

Posted: Monday 04 November 2019 12:06
by EddyG
Then you do not have the plugin manager installed and is the message from domoticz it self.
Then you have to come up with some more information about your system, debug logging and plugins and hardware installed.

Re: Debug and Stack trace

Posted: Monday 04 November 2019 13:27
by Ricky74
I confirm that I've never installed the plugin manager...

Here is my configuration :
- Domoticz beta 4.11455
- Raspberry Pi Model B Rev 2
- Hardwares : TeleInfo, Zigate, Netatmo & some dummy devices
- I use standards options for debugging...

Re: Debug and Stack trace

Posted: Monday 04 November 2019 18:55
by EddyG
I suppose there is a domoticz_crash.log file in the domoticz directory.
Maybe the developers can figure out by that log file what is causing the error.
And put it "Bugs and Problems"

Re: Debug and Stack trace

Posted: Monday 04 November 2019 19:02
by Ricky74
Here is the domoticz_crash.log from this morning 2019-11-04 07:12