• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
pilight 8.1.4 crashes after some hours
#31
Hi curlymo!

I did 4 more runs with new nightly. Time until crash is 3.5, 4, 0.2 and 6.75 hours. For the 43.log I disconnected the receiver, but it crashed all the same.

Uli


Attached Files
.zip   40-43Stripped.zip (Size: 28.64 KB / Downloads: 1)
 
Reply
#32
Updatet to the latest nightly yesterday morning.

Caught a crash Tonight:

Code:
(/home/pilight/source/daemon-dev/daemon.c #496) [Jun 17 23:04:23:229726] DEBUG: broadcasted: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":18,"weekday":3,"hour":1,"minute":4,"second":23,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 17 23:04:23:233635] DEBUG: rule #3 zeitschaltuhr1 was parsed in 0.000517 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 17 23:04:23:234526] DEBUG: rule #4 zeitschaltuhr2 was parsed in 0.000454 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 17 23:04:23:235376] DEBUG: rule #5 zeitschaltuhr3 was parsed in 0.000450 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 17 23:04:23:236225] DEBUG: rule #6 zeitschaltuhr4 was parsed in 0.000446 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 17 23:04:23:237067] DEBUG: rule #7 zeitschaltuhr5 was parsed in 0.000444 seconds
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 17 23:04:23:406119] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 17 23:04:23:656935] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 17 23:04:23:906776] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 17 23:04:24:156851] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #395) [Jun 17 23:04:24:228441] DEBUG: socket write succeeded: {"origin":"update","type":8,"uuid":"0000-74-da-38-382f5f","devices":["zeit"],"values":{"timestamp":1560812664,"year":2019,"month":6,"day":18,"hour":1,"minute":4,"second":24,"weekday":3,"dst":1}}
(/home/pilight/source/daemon-dev/daemon.c #405) [Jun 17 23:04:24:228659] DEBUG: broadcasted: {"origin":"update","type":8,"uuid":"0000-74-da-38-382f5f","devices":["zeit"],"values":{"timestamp":1560812664,"year":2019,"month":6,"day":18,"hour":1,"minute":4,"second":24,"weekday":3,"dst":1}}
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #395) [Jun 17 23:04:24:230083] DEBUG: socket write succeeded: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":18,"weekday":3,"hour":1,"minute":4,"second":24,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/daemon.c #496) [Jun 17 23:04:24:230290] DEBUG: broadcasted: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":18,"weekday":3,"hour":1,"minute":4,"second":24,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 17 23:04:24:234339] DEBUG: rule #3 zeitschaltuhr1 was parsed in 0.000553 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 17 23:04:24:235259] DEBUG: rule #4 zeitschaltuhr2 was parsed in 0.000460 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 17 23:04:24:236120] DEBUG: rule #5 zeitschaltuhr3 was parsed in 0.000456 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 17 23:04:24:237034] DEBUG: rule #6 zeitschaltuhr4 was parsed in 0.000487 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 17 23:04:24:238024] DEBUG: rule #7 zeitschaltuhr5 was parsed in 0.000587 seconds
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 17 23:04:24:406518] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 17 23:04:24:656953] DEBUG: lua wiringx on state #0
1: table  2: 'pilight'  3: table  4: table  5: '__gc'  6: userdata  7: table  8: function
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #1893) [Jun 17 23:04:24:682030] ERROR: registry:/usr/local/lib/pilight/storage/json/registry.lua /home/pilight/source/daemon-dev/libs/pilight/config/registry.c #127
pilight-daemon: /home/pilight/source/daemon-dev/libs/pilight/config/hardware.c:47: config_hardware_get_type: Assertion `plua_check_stack(state->L, 2, 32, 64) == 0' failed.
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #1996) [Jun 17 23:04:24:682811] ERROR:
---- LUA STACKTRACE ----
 /home/pilight/source/daemon-dev/daemon.c #2095
 attempt to index a userdata value
 [#000] [C]:-1
 [#001] [C]:-1 (metamethod __index)
 [#002] /usr/local/lib/pilight/storage/json/registry.lua:54
---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/daemon.c #2549) [Jun 17 23:04:24:683087] DEBUG: cpu: 6.315600%
Thread 13 "pilight-daemon" received signal SIGABRT, Aborted.
[Switching to Thread 0xb05f6470 (LWP 863)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51      ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden.
(gdb) backtrace
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0xb63f4824 in __GI_abort () at abort.c:89
#2  0xb63ec1a4 in __assert_fail_base (fmt=0xb05f6470 "\001",
    assertion=0xb684a2a8 "plua_check_stack(state->L, 2, 32, 64) == 0",
    assertion@entry=0x2 <error: Cannot access memory at address 0x2>,
    file=0xb05f4b8c " ", file@entry=0xb6504078 <lock> "", line=47,
    line@entry=2959041648,
    function=function@entry=0xb684a264 "config_hardware_get_type")
    at assert.c:92
#3  0xb63ec280 in __GI___assert_fail (
    assertion=0x2 <error: Cannot access memory at address 0x2>,
    file=0xb6504078 <lock> "", line=2959041648,
    function=0xb684a264 "config_hardware_get_type") at assert.c:101
#4  0xb67d24c4 in config_hardware_get_type () from /usr/local/lib/libpilight.so
#5  0x00010dfc in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) frame 5
#5  0x00010dfc in ?? ()
(gdb) frame 4
#4  0xb67d24c4 in config_hardware_get_type () from /usr/local/lib/libpilight.so
(gdb) frame 3
#3  0xb63ec280 in __GI___assert_fail (
    assertion=0x2 <error: Cannot access memory at address 0x2>,
    file=0xb6504078 <lock> "", line=2959041648,
    function=0xb684a264 "config_hardware_get_type") at assert.c:101
101     assert.c: Datei oder Verzeichnis nicht gefunden.
(gdb) frame 2
#2  0xb63ec1a4 in __assert_fail_base (fmt=0xb05f6470 "\001",
    assertion=0xb684a2a8 "plua_check_stack(state->L, 2, 32, 64) == 0",
    assertion@entry=0x2 <error: Cannot access memory at address 0x2>,
    file=0xb05f4b8c " ", file@entry=0xb6504078 <lock> "", line=47,
    line@entry=2959041648,
    function=function@entry=0xb684a264 "config_hardware_get_type")
    at assert.c:92
92      in assert.c
(gdb) frame 1
#1  0xb63f4824 in __GI_abort () at abort.c:89
89      abort.c: Datei oder Verzeichnis nicht gefunden.
(gdb) frame 0
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51      ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden.
(gdb)
 
Reply
#33
Are you both using a filter?
 
Reply
#34
(06-18-2019, 07:46 PM)curlymo Wrote: Are you both using a filter?

No filter, but as I wrote I got a crash with disconnected receiver too.

Uli
 
Reply
#35
Without that receiver, do you still get that lua wiringx on state # log messages?

I also got another hypothesis, now finding a way to fix it Smile
 
Reply
#36
Yes, I´m using a Filter.

Another one from Tonight:

Code:
(/home/pilight/source/daemon-dev/daemon.c #405) [Jun 18 18:51:19:547677] DEBUG: broadcasted: {"origin":"update","type":8,"uuid":"0000-74-da-38-382f5f","devices":["zeit"],"values":{"timestamp":1560883879,"year":2019,"month":6,"day":18,"hour":20,"minute":51,"second":19,"weekday":3,"dst":1}}
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #395) [Jun 18 18:51:19:548501] DEBUG: socket write succeeded: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":18,"weekday":3,"hour":20,"minute":51,"second":19,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/daemon.c #496) [Jun 18 18:51:19:548668] DEBUG: broadcasted: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":18,"weekday":3,"hour":20,"minute":51,"second":19,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 18 18:51:19:552825] DEBUG: rule #3 zeitschaltuhr1 was parsed in 0.000545 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 18 18:51:19:553721] DEBUG: rule #4 zeitschaltuhr2 was parsed in 0.000454 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 18 18:51:19:554731] DEBUG: rule #5 zeitschaltuhr3 was parsed in 0.000476 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 18 18:51:19:555646] DEBUG: rule #6 zeitschaltuhr4 was parsed in 0.000464 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 18 18:51:19:556545] DEBUG: rule #7 zeitschaltuhr5 was parsed in 0.000491 seconds
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 18 18:51:19:621272] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 18 18:51:19:871995] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 18 18:51:20:121117] DEBUG: lua wiringx on state #0
1: 'pilight.version.current'  2: '.'  3: table  4: function
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #1893) [Jun 18 18:51:20:142059] ERROR: registry:/usr/local/lib/pilight/storage/json/registry.lua /home/pilight/source/daemon-dev/libs/pilight/config/registry.c #127
pilight-daemon: /home/pilight/source/daemon-dev/libs/pilight/config/hardware.c:47: config_hardware_get_type: Assertion `plua_check_stack(state->L, 2, 32, 64) == 0' failed.
1: 'pilight.version.current'  2: '.'  3: table  4: table
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #1893) [Jun 18 18:51:20:142743] ERROR: registry:/usr/local/lib/pilight/storage/json/registry.lua /home/pilight/source/daemon-dev/libs/pilight/config/registry.c #127
pilight-daemon: /home/pilight/source/daemon-dev/libs/pilight/lua_c/common.c:115: plua_common_explode: Assertion `plua_check_stack(L, 1, 32) == 0' failed.
Thread 13 "pilight-daemon" received signal SIGABRT, Aborted.
[Switching to Thread 0xb05f6470 (LWP 6070)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51      ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden.
(gdb) backtrace
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0xb63f4824 in __GI_abort () at abort.c:89
#2  0xb63ec1a4 in __assert_fail_base (fmt=0xb05f6470 "\001",
    assertion=0xb684a2a8 "plua_check_stack(state->L, 2, 32, 64) == 0",
    assertion@entry=0x2 <error: Cannot access memory at address 0x2>,
    file=0xb05f4b8c " ", file@entry=0xb6504078 <lock> "", line=47,
    line@entry=2959041648,
    function=function@entry=0xb684a264 "config_hardware_get_type")
    at assert.c:92
#3  0xb63ec280 in __GI___assert_fail (
    assertion=0x2 <error: Cannot access memory at address 0x2>,
    file=0xb6504078 <lock> "", line=2959041648,
    function=0xb684a264 "config_hardware_get_type") at assert.c:101
#4  0xb67d24c4 in config_hardware_get_type () from /usr/local/lib/libpilight.so
#5  0x00010dfc in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) frame 5
#5  0x00010dfc in ?? ()
(gdb) frame 4
#4  0xb67d24c4 in config_hardware_get_type () from /usr/local/lib/libpilight.so
(gdb) frame 3
#3  0xb63ec280 in __GI___assert_fail (
    assertion=0x2 <error: Cannot access memory at address 0x2>,
    file=0xb6504078 <lock> "", line=2959041648,
    function=0xb684a264 "config_hardware_get_type") at assert.c:101
101     assert.c: Datei oder Verzeichnis nicht gefunden.
(gdb) frame 2
#2  0xb63ec1a4 in __assert_fail_base (fmt=0xb05f6470 "\001",
    assertion=0xb684a2a8 "plua_check_stack(state->L, 2, 32, 64) == 0",
    assertion@entry=0x2 <error: Cannot access memory at address 0x2>,
    file=0xb05f4b8c " ", file@entry=0xb6504078 <lock> "", line=47,
    line@entry=2959041648,
    function=function@entry=0xb684a264 "config_hardware_get_type")
    at assert.c:92
92      in assert.c
(gdb) frame 1
#1  0xb63f4824 in __GI_abort () at abort.c:89
89      abort.c: Datei oder Verzeichnis nicht gefunden.
(gdb) frame 0
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51      ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden.
(gdb)

Now I will also try to disconnect my Receiver.
 
Reply
#37
In the logs 40, 41 I had that message in the vincinity of the crash. In 42 I had it only during startup. In 43 (without receiver) also only in startup

Uli
 
Reply
#38
I strongly believe i found the source. Will push soon.
 
Reply
#39
Any update on this? Anything more to test?

I´m strongly waiting for 8.1.5 ;-)
 
Reply
#40
Latest nightly is already available for a few days.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
Tongue pilight 8.1.5-1-gc0a175e0 Chrashes fleisch 4 142 08-17-2019, 01:04 PM
Last Post: curlymo
  pilight for Raspbian Buster (raspberry pi 4) ? starob 29 1,576 07-15-2019, 08:45 PM
Last Post: curlymo
  pilight-receive Filteroption not working Alex 2 357 07-14-2019, 08:35 AM
Last Post: Alex
  pilight usb nano format conversion ettman8 2 249 07-14-2019, 08:32 AM
Last Post: curlymo
  Raspberry PI, gpio-ir-tx and pilight not starting lordslash 5 554 06-11-2019, 05:19 PM
Last Post: curlymo
  pilight fails starting on boot Alex 5 481 06-09-2019, 06:02 PM
Last Post: curlymo
  Google Assistant coupled to pilight hansrijn2 4 928 05-29-2019, 06:54 PM
Last Post: curlymo
  pilight-send does not stop (terminate) va13 3 474 05-15-2019, 06:06 PM
Last Post: curlymo
  oom_reaper: reaped process pilight-daemon va13 4 538 05-15-2019, 08:03 AM
Last Post: va13
  cant configure or even start pilight on raspi 3b Xvnx23 2 442 05-06-2019, 09:47 PM
Last Post: fourty2

Forum Jump:


Browsing: 1 Guest(s)