Error: Domoticz received fatal signal 6 !

Please use template to report bugs and problems. Post here your questions when not sure where else to post
Only for bugs in the Domoticz application! other problems go in different subforums!
Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.

Use the following template when posting here:

Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....

If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly

If you are replying, please do not quote images/code from the first post

Please mark your topic as Solved when the problem is solved.
User avatar
heggink
Posts: 539
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi
Domoticz version: V4.9999
Location: NL
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by heggink » Friday 08 June 2018 11:05

Couple of suggestions:
1) Please go to https://github.com/domoticz/domoticz/issues and submit an issue
2) if possible, please run domoticz either under gdb or valgrind to get info on the root cause. This is something that keeps coming back in various forms where the root cause is unclear. You will find guidance on both either in this thread or in other threads (from both myself and @emontnemery).
3) even better if you could compile by hand with debug and then do 2)

Let me know if you need any help.
Pi3, latest beta
RFXCOM, z-wave (AEOTEC, switches, temhum, pir, contacts),
Plugwise2py, P1 'smart'meter & solar panel
Alexa, Wifi Cams motion detection
ESP: relays, PIR & Temp/TempHum
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest

User avatar
gizmocuz
Posts: 8677
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by gizmocuz » Friday 08 June 2018 13:02

@mrkrabs , can you please follow the forum rules in red while posting ?

First question asked... Version .... , platform etc

Also state your python version, for raspbian it should be 3.5.3
Quality outlives Quantity!

mrkrabs
Posts: 42
Joined: Sunday 12 March 2017 15:42
Target OS: Raspberry Pi
Domoticz version: 3.9589
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by mrkrabs » Friday 08 June 2018 13:16

sorry...

here are my specs:

Version: 9589 (happened on 2 previous release as well)
Platform: latest raspbian
Plugin/Hardware:
All plugins are disabled
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
Python version: Python 3.5.3

will try running with valgrind a bit later.

User avatar
gizmocuz
Posts: 8677
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by gizmocuz » Friday 08 June 2018 13:31

@mrkrabs, thanks!
I see you already use python 3.5.3 hmmmm
heggink is using 3.4 ...
I hope when you build in debug mode you get a good stack trace... i know building would take forever
Quality outlives Quantity!

mrkrabs
Posts: 42
Joined: Sunday 12 March 2017 15:42
Target OS: Raspberry Pi
Domoticz version: 3.9589
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by mrkrabs » Friday 08 June 2018 13:33

i am not that good in building, but will try.. a quick question. while i disabled my 2 plugins in the hardware tab in domoticz, there's still a folder AwoxSMP in the plugins folder that i cannot disable in web interface since it's not there. could this be an issue? is it safe to delete it?

User avatar
heggink
Posts: 539
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi
Domoticz version: V4.9999
Location: NL
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by heggink » Friday 08 June 2018 13:40

How do you mean "disable in web interface"? Using python plugin manager?
You should be able to delete by hand but, if not used then it won;t get called so should not cause the crash.
Forgot: there used to be an issue with python 3.5.3 on pi. downgrading to 3.4 did solve it (I run 3.4 as a result). Not sure if that's still the case.
Pi3, latest beta
RFXCOM, z-wave (AEOTEC, switches, temhum, pir, contacts),
Plugwise2py, P1 'smart'meter & solar panel
Alexa, Wifi Cams motion detection
ESP: relays, PIR & Temp/TempHum
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest

mrkrabs
Posts: 42
Joined: Sunday 12 March 2017 15:42
Target OS: Raspberry Pi
Domoticz version: 3.9589
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by mrkrabs » Friday 08 June 2018 13:43

i meant switching off "Enabled" switch in Hardware tab next to plugin. doesn't it disable and don't load the plugin?

User avatar
gizmocuz
Posts: 8677
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by gizmocuz » Friday 08 June 2018 13:46

@mrkrabs, please follow these build steps

https://www.domoticz.com/wiki/Raspberry ... rom_source

Only use the following cmake line

cmake -DCMAKE_BUILD_TYPE=Debug CMakeLists.txt

(note the debug type)
Quality outlives Quantity!

mrkrabs
Posts: 42
Joined: Sunday 12 March 2017 15:42
Target OS: Raspberry Pi
Domoticz version: 3.9589
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by mrkrabs » Friday 08 June 2018 13:47

@heggink how do i downgrade from 3.5.3 to 3.4? i am not sure i know how to do that

User avatar
heggink
Posts: 539
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi
Domoticz version: V4.9999
Location: NL
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by heggink » Friday 08 June 2018 14:38

There are some messages on the forum on that but its a manual exercise on the Pi.
If you are not using python (disabled it) then it's not really the issue since it leads to a sig-11 instead of a sig-6
Pi3, latest beta
RFXCOM, z-wave (AEOTEC, switches, temhum, pir, contacts),
Plugwise2py, P1 'smart'meter & solar panel
Alexa, Wifi Cams motion detection
ESP: relays, PIR & Temp/TempHum
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest

User avatar
gizmocuz
Posts: 8677
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by gizmocuz » Friday 08 June 2018 14:40

@heggink, thats only possible when you build domoticz yourself.
If this is from a binary, then removing python3 might help yes.
Quality outlives Quantity!

1kohm
Posts: 11
Joined: Thursday 29 December 2016 19:28
Target OS: Raspberry Pi
Domoticz version: 3.5877
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by 1kohm » Monday 11 June 2018 23:10

Hi,

so I was running on latest stable since months but from time to time (every few days or weeks) Domoticz was in offline (service was running - init.d/domoticz.sh).

I've decided to reinstall whole OS and now (since 2 days) I'm strugling to bring the system up again.

Code: Select all

Version: 9589 
Platform: Intel NUC
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.4 LTS
Release:        16.04
Codename:       xenial
Python version: Python 2.7.12
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.4 LTS
Release:        16.04
Codename:       xenial
I've installed Domoticz via curl, updated to newest version, imported .db, setup all hardware and then it started to crash. Now it wont even start :x
I hope that this will help:

Code: Select all

2018-06-11 22:44:18.638  Status: EventSystem: reset all events...
2018-06-11 22:44:18.639  Status: EventSystem: reset all device statuses...
2018-06-11 22:44:18.658  Error: Domoticz received fatal signal 6 !...
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz() [0x60a568]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz(_Z14signal_handleri+0x52) [0x60a622]
2018-06-11 22:44:18.663  Error:   /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7f16fc56c390]
2018-06-11 22:44:18.663  Error:   /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38) [0x7f16fbcb9428]
2018-06-11 22:44:18.663  Error:   /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7f16fbcbb02a]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x15d) [0xca5acd]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz(_ZN10__cxxabiv111__terminateEPFvvE+0x6) [0xc4b136]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz() [0xc4b181]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz() [0xc4c788]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz(_ZSt24__throw_invalid_argumentPKc+0x3f) [0xc9241f]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz(_ZN9__gnu_cxx6__stoaIyycJiEEET0_PFT_PKT1_PPS3_DpT2_EPKcS5_PmS9_+0x7e) [0x7a922e]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz(_ZN4http6server10CWebServer14GetJSonDevicesERN4Json5ValueERKSsS6_S6_S6_S6_S6_bbblS6_S6_+0x15297) [0x791787]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz(_ZN12CEventSystem13UpdateJsonMapERNS_14_tDeviceStatusEm+0x27e) [0x61e04e]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz(_ZN12CEventSystem16GetCurrentStatesEv+0x644) [0x62cdd4]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz(_ZN12CEventSystem16StartEventSystemEv+0x7f) [0x62d4cf]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz(_ZN10MainWorker7Do_WorkEv+0xf0) [0x684950]
2018-06-11 22:44:18.663  Error:   /home/domoticz/domoticz/domoticz() [0xb62979]
2018-06-11 22:44:18.663  Error:   /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7f16fc5626ba]
2018-06-11 22:44:18.663  Error:   /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f16fbd8b41d]

Code: Select all

==15751== Memcheck, a memory error detector
==15751== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==15751== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==15751== Command: ./domoticz -log domoticz_01.log
==15751== Parent PID: 15750
==15751==
==15751==
==15751== Process terminating with default action of signal 6 (SIGABRT)
==15751==    at 0x64E0428: raise (raise.c:54)
==15751==    by 0x64E2029: abort (abort.c:89)
==15751==    by 0xCA5ACC: __gnu_cxx::__verbose_terminate_handler() (in /home/domoticz/domoticz/domoticz)
==15751==    by 0xC4B135: __cxxabiv1::__terminate(void (*)()) (in /home/domoticz/domoticz/domoticz)
==15751==    by 0xC4B180: std::terminate() (in /home/domoticz/domoticz/domoticz)
==15751==    by 0xC4C787: __cxa_throw (in /home/domoticz/domoticz/domoticz)
==15751==    by 0xC9241E: std::__throw_invalid_argument(char const*) (in /home/domoticz/domoticz/domoticz)
==15751==    by 0x7A922D: unsigned long long __gnu_cxx::__stoa<unsigned long long, unsigned long long, char, int>(unsigned long long (*)(char const*, char**, $
==15751==    by 0x791786: http::server::CWebServer::GetJSonDevices(Json::Value&, std::string const&, std::string const&, std::string const&, std::string const$
==15751==    by 0x61E04D: CEventSystem::UpdateJsonMap(CEventSystem::_tDeviceStatus&, unsigned long) (in /home/domoticz/domoticz/domoticz)
==15751==    by 0x62CDD3: CEventSystem::GetCurrentStates() (in /home/domoticz/domoticz/domoticz)
==15751==    by 0x62D4CE: CEventSystem::StartEventSystem() (in /home/domoticz/domoticz/domoticz)
==15751==
==15751== HEAP SUMMARY:
==15751==     in use at exit: 1,148,939 bytes in 11,601 blocks
==15751==   total heap usage: 48,179 allocs, 36,578 frees, 9,545,162 bytes allocated
==15751==
==15751== LEAK SUMMARY:
==15751==    definitely lost: 16 bytes in 1 blocks
==15751==    indirectly lost: 0 bytes in 0 blocks
==15751==      possibly lost: 126,632 bytes in 121 blocks
==15751==    still reachable: 1,022,291 bytes in 11,479 blocks
==15751==                       of which reachable via heuristic:
==15751==                         stdstring          : 137,727 bytes in 3,648 blocks
==15751==                         length64           : 232,696 bytes in 1,109 blocks
==15751==         suppressed: 0 bytes in 0 blocks
==15751== Rerun with --leak-check=full to see details of leaked memory
==15751==
==15751== For counts of detected and suppressed errors, rerun with: -v
==15751== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

User avatar
gizmocuz
Posts: 8677
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by gizmocuz » Tuesday 12 June 2018 7:03

@1kOhm, what domoticz version are you using ?
Can you try to switch to the beta ?
cd domoticz
./updatebeta
Quality outlives Quantity!

lost
Posts: 191
Joined: Thursday 10 November 2016 10:30
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by lost » Tuesday 12 June 2018 7:16

gizmocuz wrote:
Tuesday 12 June 2018 7:03
@1kOhm, what domoticz version are you using ?
Can you try to switch to the beta ?
cd domoticz
./updatebeta
I also get this one, not very often, since my update to last stable (with also raspbian reinstalled to stretch, was quite straightforward after the usual libssl version hack): Will not be very easy to say for sure if problem is solved, on my system (mostly z-wave based with ~20 devices + cams + own script/services interfaced with Domoticz through JSON http API) I do run into this problem every 2 months or so! So cannot set detailled logs during this time on a raspberry PI, but if there is a possibility to get more useful data when this occurs without too much logging meantime, please let me know.

Regards.

1kohm
Posts: 11
Joined: Thursday 29 December 2016 19:28
Target OS: Raspberry Pi
Domoticz version: 3.5877
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by 1kohm » Tuesday 12 June 2018 18:05

gizmocuz wrote:
Tuesday 12 June 2018 7:03
@1kOhm, what domoticz version are you using ?
Can you try to switch to the beta ?
cd domoticz
./updatebeta
My current version is 3.9625 (previous information was wrong).
I've installed libpython3.5

Code: Select all

Version: 3.9625
Build Hash: 529bd73d
Compile Date: 2018-06-11 08:30:28
dzVents Version: 2.4.6
Python Version: 3.5.2 (default, Nov 23 2017, 16:37:01) [GCC 5.4.0 20160609]

Uptime: 17 Hours, 38 Minutes, 30 Seconds 
System is currently up. What I did to fix:
0. Installed libpython3.5
1. Rollback default domoticz.db file
2. start domoticz service with valgrind

Code: Select all

sudo valgrind --suppressions=./valgrind-python.supp --track-origins=yes --log-file=domoticz_vg_01.log ./domoticz -log domoticz_01.log
3. stop service and changed domoticz.db to my current one
4. Start service with valgrind

Let's see how long it will run without crash.

Is there anything in domoticz.db file that is different between versions, which might crash the service?

Maybe some hardware that is missconfigured (not yet configured when migrating the system, like python plugins) that can cause that crash?

As I said @begining, I've migrated to new OS due to previous random unclear crash of service (Domoticz Offline but service running).
Now I can at least make full memory dump thanks to advice of user heggink!

User avatar
gizmocuz
Posts: 8677
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by gizmocuz » Wednesday 13 June 2018 8:08

@1kohm, i do not think it has to do with the database version you are using.
If you are using an old database, and run the beta, when needed, the beta version will migrate your database to be compatible with it.
But if you then install the stable again, and use this migrated database, then you have issues
Quality outlives Quantity!

lost
Posts: 191
Joined: Thursday 10 November 2016 10:30
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by lost » Wednesday 13 June 2018 16:58

1kohm wrote:
Tuesday 12 June 2018 18:05
As I said @begining, I've migrated to new OS due to previous random unclear crash of service (Domoticz Offline but service running).
Now I can at least make full memory dump thanks to advice of user heggink!
On my side, with stable+stretch on a PI3, I sometimes runs into web interface being unresponsive with service that looks OK. Exemple today after ~3 weeks uptime:

Code: Select all

● domoticz.service - LSB: Home Automation System
   Loaded: loaded (/etc/init.d/domoticz.sh; generated; vendor preset: enabled)
   Active: active (running) since Mon 2018-05-28 11:10:36 CEST; 2 weeks 2 days ago
     Docs: man:systemd-sysv-generator(8)
   CGroup: /system.slice/domoticz.service
           └─28361 python /home/XXX/domoticz/scripts/checkZwJam.py -c2 -j144 -nSiren -m2 -s0

mai 28 11:10:34 rasDomo systemd[1]: Starting LSB: Home Automation System...
mai 28 11:10:36 rasDomo domoticz.sh[573]: 2018-05-28 11:10:36.376  Domoticz V3.8153 (c)2012-2017 GizMoCuz
mai 28 11:10:36 rasDomo domoticz.sh[573]: 2018-05-28 11:10:36.376  Build Hash: 494fff7, Date: 2017-07-30 12:19:41
mai 28 11:10:36 rasDomo domoticz.sh[573]: 2018-05-28 11:10:36.377  Startup Path: /home/XXX/domoticz/
mai 28 11:10:36 rasDomo domoticz.sh[573]: domoticz: Domoticz is starting up....
mai 28 11:10:36 rasDomo domoticz[600]: Domoticz is starting up....
mai 28 11:10:36 rasDomo domoticz[641]: Domoticz running...
mai 28 11:10:36 rasDomo systemd[1]: Started LSB: Home Automation System.
But on log side, it's aways the same:

Code: Select all

2018-06-13 10:43:33.150  (Z-Stick) Usage (Unknown)
2018-06-13 10:43:33.151  (Z-Stick) Usage (Power Meter)
2018-06-13 10:43:33.597  (Z-Stick) Usage (Smart-Meter W)
2018-06-13 10:43:33.598  (Z-Stick) Usage (Power Meter)
2018-06-13 10:43:33.804  (Z-Stick) General/Voltage (Smart-Meter V)
2018-06-13 10:43:33.998  (Z-Stick) Current (Smart-Meter I)
2018-06-13 10:43:34.150  (Z-Stick) General/Percentage (Percentage)
2018-06-13 10:44:00.151  (Z-Stick) General/Percentage (Percentage)
2018-06-13 10:44:00.384  Error: Domoticz received fatal signal 6 !...
2018-06-13 10:44:00.407  Error:   /home/XXX/domoticz/domoticz() [0x1cdc48]
2018-06-13 10:44:00.407  Error:   /home/XXX/domoticz/domoticz(_Z14signal_handleri+0x58) [0x1cdd00]
2018-06-13 10:44:00.407  Error:   /lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer+0) [0x76a8a6b0]
2018-06-13 10:44:00.407  Error:   /lib/arm-linux-gnueabihf/libc.so.6(gsignal+0xa0) [0x76a8945c]
And this time, just cannot restart the service as usual: Service status says OK with updated date/time, but http still unresponsive + log file does not fills a single more line! Starting Domoticz manually (with sudo, so not a priivilege pb) from a terminal shows this:

Code: Select all

2018-06-13 16:48:47.433  Domoticz V3.8153 (c)2012-2017 GizMoCuz
2018-06-13 16:48:47.434  Build Hash: 494fff7, Date: 2017-07-30 12:19:41
2018-06-13 16:48:47.434  Startup Path: /home/XXX/domoticz/
2018-06-13 16:48:47.464  Sunrise: 05:49:00 SunSet:21:54:00
2018-06-13 16:48:47.464  EventSystem: reset all events...
2018-06-13 16:48:47.465  PluginSystem: Failed dynamic library load, install the latest libpython3.x library that is available for your platform.
2018-06-13 16:48:47.474  Active notification Subsystems: email (1/12)
2018-06-13 16:48:47.476  Error: WebServer(HTTP) startup failed on address 0.0.0.0 with port: 8080: bind: Address already in use
2018-06-13 16:48:47.476  Error: WebServer(HTTP) check if no other application is using port: 8080
2018-06-13 16:48:47.484  Error: WebServer(SSL) startup failed on address 0.0.0.0 with port: 443: bind: Address already in use
2018-06-13 16:48:47.484  Error: WebServer(SSL) check privileges for opening ports below 1024
2018-06-13 16:48:47.485  Proxymanager started.
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >'
  what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument
shutdown'ed -r so unbinding both http(s) ports (blocking usual service restart) was done.

1kohm
Posts: 11
Joined: Thursday 29 December 2016 19:28
Target OS: Raspberry Pi
Domoticz version: 3.5877
Contact:

Re: Error: Domoticz received fatal signal 6 !

Post by 1kohm » Sunday 17 June 2018 11:34

Ok, so after some days Domoticz crashed again. Below you will find debug information. Please help me to analyze this log and maybe find root couse:

Code: Select all

Version: 3.9625
Build Hash: 529bd73d
Compile Date: 2018-06-11 08:30:28
dzVents Version: 2.4.6
Python Version: 3.5.2 (default, Nov 23 2017, 16:37:01) [GCC 5.4.0 20160609]

Code: Select all

==4398== Memcheck, a memory error detector
==4398== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==4398== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==4398== Command: ./domoticz -log domoticz_01.log
==4398== Parent PID: 4397
==4398== 
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0:
--4398-- Ignoring non-Dwarf2/3/4 block in .debug_info
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0:
--4398-- Last block truncated in .debug_info; ignoring
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0:
--4398-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
==4398== Thread 6:
==4398== Conditional jump or move depends on uninitialised value(s)
==4398==    at 0xA7A861: http::server::cWebemRequestHandler::CompressWebOutput(http::server::request const&, http::server::reply&) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0xA7F600: http::server::cWebemRequestHandler::handle_request(http::server::request const&, http::server::reply&) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0xA6C666: http::server::connection::handle_read(boost::system::error_code const&, unsigned long) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0xA6CDD2: boost::asio::detail::reactive_socket_recv_op<boost::asio::mutable_buffers_1, boost::_bi::bind_t<void, boost::_mfi::mf2<void, http::server::connection, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server::connection> >, boost::arg<1> (*)(), boost::arg<2> (*)()> > >::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x7EA463: boost::asio::detail::scheduler::run(boost::system::error_code&) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0xA9E7DB: http::server::server_base::run() (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x7021ED: http::server::CWebServer::Do_Work() (in /home/domoticz/domoticz/domoticz)
==4398==    by 0xB62978: thread_proxy (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x5D886B9: start_thread (pthread_create.c:333)
==4398==    by 0x65B241C: clone (clone.S:109)
==4398==  Uninitialised value was created by a heap allocation
==4398==    at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4398==    by 0xC4B1F7: operator new(unsigned long) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x798388: http::server::CWebServer::StartServer(http::server::server_settings&, std::string const&, bool) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x7AE28F: http::server::CWebServerHelper::StartServers(http::server::server_settings&, http::server::ssl_server_settings&, std::string const&, bool, tcp::server::CTCPServer*) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x6805B8: MainWorker::StartThread() (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x683F82: MainWorker::Start() (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x5C7814: main (in /home/domoticz/domoticz/domoticz)
==4398== 
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_hashlib.cpython-35m-x86_64-linux-gnu.so:
--4398-- Ignoring non-Dwarf2/3/4 block in .debug_info
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_hashlib.cpython-35m-x86_64-linux-gnu.so:
--4398-- Last block truncated in .debug_info; ignoring
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_hashlib.cpython-35m-x86_64-linux-gnu.so:
--4398-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_ssl.cpython-35m-x86_64-linux-gnu.so:
--4398-- Ignoring non-Dwarf2/3/4 block in .debug_info
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_ssl.cpython-35m-x86_64-linux-gnu.so:
--4398-- Last block truncated in .debug_info; ignoring
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_ssl.cpython-35m-x86_64-linux-gnu.so:
--4398-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_bz2.cpython-35m-x86_64-linux-gnu.so:
--4398-- Ignoring non-Dwarf2/3/4 block in .debug_info
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_bz2.cpython-35m-x86_64-linux-gnu.so:
--4398-- Last block truncated in .debug_info; ignoring
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_bz2.cpython-35m-x86_64-linux-gnu.so:
--4398-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_lzma.cpython-35m-x86_64-linux-gnu.so:
--4398-- Ignoring non-Dwarf2/3/4 block in .debug_info
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_lzma.cpython-35m-x86_64-linux-gnu.so:
--4398-- Last block truncated in .debug_info; ignoring
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_lzma.cpython-35m-x86_64-linux-gnu.so:
--4398-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_json.cpython-35m-x86_64-linux-gnu.so:
--4398-- Ignoring non-Dwarf2/3/4 block in .debug_info
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_json.cpython-35m-x86_64-linux-gnu.so:
--4398-- Last block truncated in .debug_info; ignoring
--4398-- WARNING: Serious error when reading debug info
--4398-- When reading debug info from /usr/lib/python3.5/lib-dynload/_json.cpython-35m-x86_64-linux-gnu.so:
--4398-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
==4398== Thread 11:
==4398== Conditional jump or move depends on uninitialised value(s)
==4398==    at 0xA419B5: CNotificationHelper::CheckAndHandleLastUpdateNotification() (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x6851E9: MainWorker::Do_Work() (in /home/domoticz/domoticz/domoticz)
==4398==    by 0xB62978: thread_proxy (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x5D886B9: start_thread (pthread_create.c:333)
==4398==    by 0x65B241C: clone (clone.S:109)
==4398==  Uninitialised value was created by a stack allocation
==4398==    at 0xA43724: CNotificationHelper::ReloadNotifications() (in /home/domoticz/domoticz/domoticz)
==4398== 
==4398== Thread 3:
==4398== Conditional jump or move depends on uninitialised value(s)
==4398==    at 0xA3F311: CNotificationHelper::CheckAndHandleNotification(unsigned long, std::string const&, unsigned char, unsigned char, _eNotificationTypes, float) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0xA40926: CNotificationHelper::CheckAndHandleNotification(unsigned long, int, std::string const&, std::string const&, unsigned char, unsigned char, unsigned char, int, std::string const&, float) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0xA2C78F: Plugins::CDevice_update(Plugins::CDevice*, _object*, _object*) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0xB14D058: PyCFunction_Call (in /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0)
==4398==    by 0xB25A08A: PyEval_EvalFrameEx (in /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0)
==4398==    by 0xB2E9CAB: _PyEval_EvalCodeWithName.lto_priv.1742 (in /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0)
==4398==    by 0xB257F38: PyEval_EvalFrameEx (in /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0)
==4398==    by 0xB259638: PyEval_EvalFrameEx (in /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0)
==4398==    by 0xB2E9CAB: _PyEval_EvalCodeWithName.lto_priv.1742 (in /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0)
==4398==    by 0xB2E9D82: PyEval_EvalCodeEx (in /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0)
==4398==    by 0xB171AD7: function_call.lto_priv.368 (in /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0)
==4398==    by 0xB22654D: PyObject_Call (in /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0)
==4398==  Uninitialised value was created by a stack allocation
==4398==    at 0xA43724: CNotificationHelper::ReloadNotifications() (in /home/domoticz/domoticz/domoticz)
==4398== 
==4398== Thread 39:
==4398== Conditional jump or move depends on uninitialised value(s)
==4398==    at 0x6B60A8: CSQLHelper::AddTaskItem(_tTaskItem const&, bool) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x61F010: CEventSystem::ScheduleEvent(int, std::string, bool, std::string const&, int) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x62F5BD: CEventSystem::parseBlocklyActions(CEventSystem::_tEventItem const&) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x632317: CEventSystem::ParseBlocklyLua(lua_State*, CEventSystem::_tEventItem const&) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x63264B: CEventSystem::EvaluateDatabaseEvents(CEventSystem::_tEventQueue const&) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x633A4E: CEventSystem::EvaluateEvent(std::vector<CEventSystem::_tEventQueue, std::allocator<CEventSystem::_tEventQueue> > const&) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x63499D: CEventSystem::EventQueueThread() (in /home/domoticz/domoticz/domoticz)
==4398==    by 0xB62978: thread_proxy (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x5D886B9: start_thread (pthread_create.c:333)
==4398==    by 0x65B241C: clone (clone.S:109)
==4398==  Uninitialised value was created by a stack allocation
==4398==    at 0x62F2F7: CEventSystem::parseBlocklyActions(CEventSystem::_tEventItem const&) (in /home/domoticz/domoticz/domoticz)
==4398== 
==4398== 
==4398== Process terminating with default action of signal 1 (SIGHUP)
==4398==    at 0x5D91C1D: ??? (syscall-template.S:84)
==4398==    by 0x6472A0: sleep_seconds(long) (in /home/domoticz/domoticz/domoticz)
==4398==    by 0x5C784F: main (in /home/domoticz/domoticz/domoticz)
==4398== 
==4398== HEAP SUMMARY:
==4398==     in use at exit: 15,488,618 bytes in 48,486 blocks
==4398==   total heap usage: 1,679,901,886 allocs, 1,679,853,400 frees, 199,690,738,549 bytes allocated
==4398== 
==4398== LEAK SUMMARY:
==4398==    definitely lost: 352 bytes in 3 blocks
==4398==    indirectly lost: 0 bytes in 0 blocks
==4398==      possibly lost: 2,552,120 bytes in 2,256 blocks
==4398==    still reachable: 12,936,146 bytes in 46,227 blocks
==4398==                       of which reachable via heuristic:
==4398==                         stdstring          : 224,615 bytes in 3,850 blocks
==4398==                         length64           : 246,776 bytes in 1,115 blocks
==4398==         suppressed: 0 bytes in 0 blocks
==4398== Rerun with --leak-check=full to see details of leaked memory
==4398== 
==4398== For counts of detected and suppressed errors, rerun with: -v
==4398== ERROR SUMMARY: 70293 errors from 4 contexts (suppressed: 768353 from 246)


Post Reply

Who is online

Users browsing this forum: GSV3Miac and 4 guests