• 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
#21
The main branch is a known issue that has been fixed in the nightlies Smile

The current nightly issue is one in the 433gpio hardware module, but i still haven't found why.
 
Reply
#22
(06-12-2019, 06:55 PM)Alex Wrote: Yes. The nightly Pi uses Filter with Sender &Receiver from you, the Main Branch Pi uses a PCB Full Kit.

Caught another crash today on the Nightly and on the Main Branch:

Nightly:

Code:
[Jun 12 14:09:57:589878] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":8,"uuid":"0000-74-da-38-382f5f","devices":["zeit"],"values":{"timestamp":1560348597,"year":2019,"month":6,"day":12,"hour":16,"minute":9,"second":57,"weekday":4,"dst":1}}
[Jun 12 14:09:57:590668] pilight-daemon: DEBUG: socket write succeeded: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":12,"weekday":4,"hour":16,"minute":9,"second":57,"dst":1},"uuid":"0000-74-da-38-382f5f"}
[Jun 12 14:09:57:590830] pilight-daemon: DEBUG: broadcasted: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":12,"weekday":4,"hour":16,"minute":9,"second":57,"dst":1},"uuid":"0000-74-da-38-382f5f"}
[Jun 12 14:09:57:595155] pilight-daemon: DEBUG: rule #3 zeitschaltuhr1 was parsed in 0.000500 seconds
[Jun 12 14:09:57:596042] pilight-daemon: DEBUG: rule #4 zeitschaltuhr2 was parsed in 0.000427 seconds
[Jun 12 14:09:57:597024] pilight-daemon: DEBUG: rule #5 zeitschaltuhr3 was parsed in 0.000554 seconds
[Jun 12 14:09:57:597894] pilight-daemon: DEBUG: rule #6 zeitschaltuhr4 was parsed in 0.000433 seconds
[Jun 12 14:09:57:598755] pilight-daemon: DEBUG: rule #7 zeitschaltuhr5 was parsed in 0.000434 seconds
Thread 13 "pilight-daemon" received signal SIGABRT, Aborted.
[Switching to Thread 0xb05f6470 (LWP 909)]
__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) Quit
(gdb) backtrace
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0xb63fb824 in __GI_abort () at abort.c:89
#2  0xb63f31a4 in __assert_fail_base (fmt=0xb05f6470 "\001",
    assertion=0xb684b810 "plua_check_stack(state->L, 2, 32, 64) == 0",
    assertion@entry=0x2 <error: Cannot access memory at address 0x2>, file=0xb05f4b94 " ", file@entry=0xb650b078 <lock> "",
    line=47, line@entry=2959041648, function=function@entry=0xb684b7cc "config_hardware_get_type") at assert.c:92
#3  0xb63f3280 in __GI___assert_fail (assertion=0x2 <error: Cannot access memory at address 0x2>,
    file=0xb650b078 <lock> "", line=2959041648, function=0xb684b7cc "config_hardware_get_type") at assert.c:101
#4  0xb67d6e7c in config_hardware_get_type () from /usr/local/lib/libpilight.so
#5  0x00010330 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Main Branch: 

Code:
[Jun 12 09:49:42:569494] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":15,"uuid":"0000-b8-27-eb-521535","devices":["label2"],"values":{"timestamp":1560332982,"label":"ja","color":"black"}}
[Jun 12 09:49:42:569763] pilight-daemon: DEBUG: socket write succeeded: {"origin":"sender","protocol":"generic_label","message":{"id":101,"label":"ja","color":"black"},"repeat":1,"uuid":"0000-b8-27-eb-521535"}
[Jun 12 09:49:42:569823] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"generic_label","message":{"id":101,"label":"ja","color":"black"},"repeat":1,"uuid":"0000-b8-27-eb-521535"}
[Jun 12 09:49:42:572640] pilight-daemon: DEBUG: rule #3 zeitschaltuhr1 was parsed in 0.000194 seconds
[Jun 12 09:49:42:573117] pilight-daemon: DEBUG: rule #4 zeitschaltuhr2 was parsed in 0.000145 seconds
[Jun 12 09:49:42:573547] pilight-daemon: DEBUG: rule #5 zeitschaltuhr3 was parsed in 0.000134 seconds
[Jun 12 09:49:42:573929] pilight-daemon: DEBUG: rule #6 zeitschaltuhr4 was parsed in 0.000133 seconds
[Jun 12 09:49:42:574622] pilight-daemon: DEBUG: rule #7 zeitschaltuhr5 was parsed in 0.000222 seconds
-- REASON_SEND_CODE --
pilight-daemon: /home/pilight/source/daemon-dev/libs/libuv/threadpool.c:313: uv__queue_done: Assertion `(((const QUEUE *) (&(req->loop)->active_reqs) == (const QUEUE *) (*(QUEUE **) &((*(&(req->loop)->active_reqs))[0]))) == 0)' failed.
Thread 1 "pilight-daemon" received signal SIGABRT, Aborted.
__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) Quit
(gdb)  backtrace
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x763c2824 in __GI_abort () at abort.c:89
#2  0x763ba1a4 in __assert_fail_base (fmt=0x76ff5000 "\001", assertion=0x7683957c "(((const QUEUE *) (&(req->loop)->active_reqs) == (const QUEUE *) (*(QUEUE **) &((*(&(req->loop)->active_reqs))[0]))) == 0)", assertion@entry=0x2 <error: Cannot access memory at address 0x2>, file=0x7effaf34 " ",
    file@entry=0x764d2078 <lock> "", line=313, line@entry=1996443648, function=function@entry=0x76839630 "uv__queue_done") at assert.c:92
#3  0x763ba280 in __GI___assert_fail (assertion=0x2 <error: Cannot access memory at address 0x2>, file=0x764d2078 <lock> "", line=1996443648, function=0x76839630 "uv__queue_done") at assert.c:101
#4  0x76761490 in ?? () from /usr/local/lib/libpilight.so
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
I use a cheap china reveiver/sender.
If you like I can do a test with disconnected receiver

Uli
 
Reply
#23
This is really awesome, the help you are giving me. I've updated the pilight code with more debugging information. What i'm looking for is the error that says "attempt to index a number value".

The latest nightly should give us more information as in a file and a line number like this:
Code:
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 12 20:01:18:977947] DEBUG: lua wiringx on state #0
That should tell me exactly where the error happens.

I haven't been able to forcely reproduce it.
 
Reply
#24
And from the Main Branch Pi a complete Backtrace:

Code:
[Jun 12 19:15:02:198635] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"elro_800_switch","message":{"systemcode":23,"unitcode":1,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-521535"}
Thread 1 "pilight-daemon" received signal SIGABRT, Aborted.
__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  0x763c2824 in __GI_abort () at abort.c:89
#2  0x763ba1a4 in __assert_fail_base (fmt=0x76ff5000 "\001", assertion=0x7683957c "(((const QUEUE *) (&(req->loop)->active_reqs) == (const QUEUE *) (*(QUEUE **) &((*(&(req->loop)->active_reqs))[0]))) == 0)", assertion@entry=0x2 <error: Cannot access memory at address 0x2>, file=0x7effaf34 " ",
    file@entry=0x764d2078 <lock> "", line=313, line@entry=1996443648, function=function@entry=0x76839630 "uv__queue_done") at assert.c:92
#3  0x763ba280 in __GI___assert_fail (assertion=0x2 <error: Cannot access memory at address 0x2>, file=0x764d2078 <lock> "", line=1996443648, function=0x76839630 "uv__queue_done") at assert.c:101
#4  0x76761490 in ?? () from /usr/local/lib/libpilight.so
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) frame 4
#4  0x76761490 in ?? () from /usr/local/lib/libpilight.so
(gdb) frame 3
#3  0x763ba280 in __GI___assert_fail (assertion=0x2 <error: Cannot access memory at address 0x2>, file=0x764d2078 <lock> "", line=1996443648, function=0x76839630 "uv__queue_done") at assert.c:101
101     assert.c: Datei oder Verzeichnis nicht gefunden.
(gdb) frame 2
#2  0x763ba1a4 in __assert_fail_base (fmt=0x76ff5000 "\001", assertion=0x7683957c "(((const QUEUE *) (&(req->loop)->active_reqs) == (const QUEUE *) (*(QUEUE **) &((*(&(req->loop)->active_reqs))[0]))) == 0)", assertion@entry=0x2 <error: Cannot access memory at address 0x2>, file=0x7effaf34 " ",
    file@entry=0x764d2078 <lock> "", line=313, line@entry=1996443648, function=function@entry=0x76839630 "uv__queue_done") at assert.c:92
92      in assert.c
(gdb) frame 1
#1  0x763c2824 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
#25
@Alex, that main branch error is already known and already fixed in the latest nightly. No need to post about that one anymore.
 
Reply
#26
(06-12-2019, 09:40 PM)curlymo Wrote: @Alex, that main branch error is already known and already fixed in the latest nightly. No need to post about that one anymore.

I will give the newest nightly a try tomorrow

Uli
 
Reply
#27
Installed the latest nightly yesterday Morning and catched a crash:

Code:
(/home/pilight/source/daemon-dev/daemon.c #405) [Jun 14 22:52:04:293921] DEBUG: broadcasted: {"origi                                                                                                                                                                                                                         n":"update","type":8,"uuid":"0000-74-da-38-382f5f","devices":["zeit"],"values":{"timestamp":15605527                                                                                                                                                                                                                         24,"year":2019,"month":6,"day":15,"hour":0,"minute":52,"second":4,"weekday":7,"dst":1}}
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #395) [Jun 14 22:52:04:294699] DEBUG: so                                                                                                                                                                                                                         cket write succeeded: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"l                                                                                                                                                                                                                         atitude":52.660000,"year":2019,"month":6,"day":15,"weekday":7,"hour":0,"minute":52,"second":4,"dst":                                                                                                                                                                                                                         1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/daemon.c #496) [Jun 14 22:52:04:294863] DEBUG: broadcasted: {"origi                                                                                                                                                                                                                         n":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":201                                                                                                                                                                                                                         9,"month":6,"day":15,"weekday":7,"hour":0,"minute":52,"second":4,"dst":1},"uuid":"0000-74-da-38-382f                                                                                                                                                                                                                         5f"}
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 14 22:52:04:298678] DEBUG:                                                                                                                                                                                                                          rule #3 zeitschaltuhr1 was parsed in 0.000486 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 14 22:52:04:299547] DEBUG:                                                                                                                                                                                                                          rule #4 zeitschaltuhr2 was parsed in 0.000426 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 14 22:52:04:300510] DEBUG:                                                                                                                                                                                                                          rule #5 zeitschaltuhr3 was parsed in 0.000438 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 14 22:52:04:301480] DEBUG:                                                                                                                                                                                                                          rule #6 zeitschaltuhr4 was parsed in 0.000437 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 14 22:52:04:302316] DEBUG:                                                                                                                                                                                                                          rule #7 zeitschaltuhr5 was parsed in 0.000421 seconds
Thread 7 "pilight-daemon" received signal SIGABRT, Aborted.
[Switching to Thread 0xb35fc470 (LWP 4678)]
__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=0xb35fc470 "\001", assertion=0xb684a568 "plua_check_stack(state->L, 2, 32, 64) == 0", assertion@entry=0x2 <error: Cannot access memory at address 0x2>, file=0xb35fab8c " ", file@entry=0xb6504078 <lock> "", line=47, line@entry=3009397872,
    function=function@entry=0xb684a524 "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=3009397872, function=0xb684a524 "config_hardware_get_type") at assert.c:101
#4  0xb67d2308 in config_hardware_get_type () from /usr/local/lib/libpilight.so
#5  0x00010d3c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) frame 5
#5  0x00010d3c in ?? ()
(gdb) frame 4
#4  0xb67d2308 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=3009397872, function=0xb684a524 "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=0xb35fc470 "\001", assertion=0xb684a568 "plua_check_stack(state->L, 2, 32, 64) == 0", assertion@entry=0x2 <error: Cannot access memory at address 0x2>, file=0xb35fab8c " ", file@entry=0xb6504078 <lock> "", line=47, line@entry=3009397872,
    function=function@entry=0xb684a524 "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
#28
Was there no ERROR before the crash?
 
Reply
#29
No, no Error. 
Once agaion from this morning:

Code:
(/home/pilight/source/daemon-dev/daemon.c #405) [Jun 16 05:51:26:791288] DEBUG: broadcasted: {"origin":"update","type":8,"uuid":"0000-74-da-38-382f5f","devices":["zeit"],"values":{"timestamp":1560664286,"year":2019,"month":6,"day":16,"hour":7,"minute":51,"second":26,"weekday":1,"dst":1}}
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #395) [Jun 16 05:51:26:792077] DEBUG: socket write succeeded: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":16,"weekday":1,"hour":7,"minute":51,"second":26,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/daemon.c #496) [Jun 16 05:51:26:792263] DEBUG: broadcasted: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":16,"weekday":1,"hour":7,"minute":51,"second":26,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:26:796307] DEBUG: rule #3 zeitschaltuhr1 was parsed in 0.000621 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:26:797191] DEBUG: rule #4 zeitschaltuhr2 was parsed in 0.000431 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:26:798014] DEBUG: rule #5 zeitschaltuhr3 was parsed in 0.000421 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:26:798836] DEBUG: rule #6 zeitschaltuhr4 was parsed in 0.000419 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:26:799656] DEBUG: rule #7 zeitschaltuhr5 was parsed in 0.000417 seconds
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 16 05:51:26:963588] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 16 05:51:27:213171] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 16 05:51:27:463924] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 16 05:51:27:713528] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #395) [Jun 16 05:51:27:793649] DEBUG: socket write succeeded: {"origin":"update","type":8,"uuid":"0000-74-da-38-382f5f","devices":["zeit"],"values":{"timestamp":1560664287,"year":2019,"month":6,"day":16,"hour":7,"minute":51,"second":27,"weekday":1,"dst":1}}
(/home/pilight/source/daemon-dev/daemon.c #405) [Jun 16 05:51:27:793862] DEBUG: broadcasted: {"origin":"update","type":8,"uuid":"0000-74-da-38-382f5f","devices":["zeit"],"values":{"timestamp":1560664287,"year":2019,"month":6,"day":16,"hour":7,"minute":51,"second":27,"weekday":1,"dst":1}}
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #395) [Jun 16 05:51:27:794653] DEBUG: socket write succeeded: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":16,"weekday":1,"hour":7,"minute":51,"second":27,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/daemon.c #496) [Jun 16 05:51:27:794839] DEBUG: broadcasted: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":16,"weekday":1,"hour":7,"minute":51,"second":27,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:27:798918] DEBUG: rule #3 zeitschaltuhr1 was parsed in 0.000486 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:27:799795] DEBUG: rule #4 zeitschaltuhr2 was parsed in 0.000429 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:27:800768] DEBUG: rule #5 zeitschaltuhr3 was parsed in 0.000440 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:27:801604] DEBUG: rule #6 zeitschaltuhr4 was parsed in 0.000420 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:27:802434] DEBUG: rule #7 zeitschaltuhr5 was parsed in 0.000423 seconds
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 16 05:51:27:963911] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 16 05:51:28:213373] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 16 05:51:28:463220] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/wiringx.c #436) [Jun 16 05:51:28:713826] DEBUG: lua wiringx on state #0
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #395) [Jun 16 05:51:28:796500] DEBUG: socket write succeeded: {"origin":"update","type":8,"uuid":"0000-74-da-38-382f5f","devices":["zeit"],"values":{"timestamp":1560664288,"year":2019,"month":6,"day":16,"hour":7,"minute":51,"second":28,"weekday":1,"dst":1}}
(/home/pilight/source/daemon-dev/daemon.c #405) [Jun 16 05:51:28:796714] DEBUG: broadcasted: {"origin":"update","type":8,"uuid":"0000-74-da-38-382f5f","devices":["zeit"],"values":{"timestamp":1560664288,"year":2019,"month":6,"day":16,"hour":7,"minute":51,"second":28,"weekday":1,"dst":1}}
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #395) [Jun 16 05:51:28:797517] DEBUG: socket write succeeded: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":16,"weekday":1,"hour":7,"minute":51,"second":28,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/daemon.c #496) [Jun 16 05:51:28:797701] DEBUG: broadcasted: {"origin":"receiver","protocol":"datetime","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":16,"weekday":1,"hour":7,"minute":51,"second":28,"dst":1},"uuid":"0000-74-da-38-382f5f"}
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:28:803075] DEBUG: rule #3 zeitschaltuhr1 was parsed in 0.000478 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:28:804085] DEBUG: rule #4 zeitschaltuhr2 was parsed in 0.000554 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:28:804942] DEBUG: rule #5 zeitschaltuhr3 was parsed in 0.000429 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:28:805771] DEBUG: rule #6 zeitschaltuhr4 was parsed in 0.000422 seconds
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2050) [Jun 16 05:51:28:806587] DEBUG: rule #7 zeitschaltuhr5 was parsed in 0.000420 seconds
pilight-daemon: /home/pilight/source/daemon-dev/libs/pilight/lua_c/config.c:175: plua_config: Assertion `plua_check_stack(L, 1, 32) == 0' failed.
Thread 1 "pilight-daemon" received signal SIGABRT, Aborted.
__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=0xb6ff6000 "\001", assertion=0xb68526e4 "plua_check_stack(L, 1, 32) == 0", assertion@entry=0x2 <error: Cannot access memory at address 0x2>, file=0xbefff364 " ", file@entry=0xb6504078 <lock> "", line=175, line@entry=3070189568,
    function=function@entry=0xb6852f38 "plua_config") at assert.c:92
#3  0xb63ec280 in __GI___assert_fail (assertion=0x2 <error: Cannot access memory at address 0x2>, file=0xb6504078 <lock> "", line=3070189568, function=0xb6852f38 "plua_config") at assert.c:101
#4  0xb6810798 in plua_config () from /usr/local/lib/libpilight.so
#5  0xb6555708 in ?? () from /usr/lib/arm-linux-gnueabihf/libluajit-5.1.so.2
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) frame 5
#5  0xb6555708 in ?? () from /usr/lib/arm-linux-gnueabihf/libluajit-5.1.so.2
(gdb) frame 4
#4  0xb6810798 in plua_config () 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=3070189568, function=0xb6852f38 "plua_config") at assert.c:101
101     assert.c: Datei oder Verzeichnis nicht gefunden.
(gdb) frame 2
#2  0xb63ec1a4 in __assert_fail_base (fmt=0xb6ff6000 "\001", assertion=0xb68526e4 "plua_check_stack(L, 1, 32) == 0", assertion@entry=0x2 <error: Cannot access memory at address 0x2>, file=0xbefff364 " ", file@entry=0xb6504078 <lock> "", line=175, line@entry=3070189568,
    function=function@entry=0xb6852f38 "plua_config") 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
#30
Please install the latest nightly tomorrow to see even more debug information. That should tell us which modules corrupted the stack.

I'm though still amazed there is no error before that.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Strange receive problem with 433Mhz Receiver and pilight 8.1.5 vanillaice30 11 136 9 hours ago
Last Post: curlymo
  pilight error after update to 8.1.5 on Odroid C2 WitchDoctor 3 153 11-29-2019, 09:56 PM
Last Post: curlymo
  pilight crashing randomly PatiB 7 278 11-16-2019, 10:50 PM
Last Post: curlymo
  [Fixed] RaspberryPi4 pilight 8.1.5 - Send isn't working DominikB1993 4 317 10-18-2019, 10:25 PM
Last Post: DominikB1993
  Real 433Mhz Remote is disturbed by pilight service henne111 2 331 10-06-2019, 06:18 PM
Last Post: wo_rasp
Tongue (solved) pilight 8.1.5-1-gc0a175e0 Chrashes fleisch 5 764 10-03-2019, 01:15 PM
Last Post: fleisch
  Starting pilight on boot: "cannot bind to the SSDP multicast network" pilino1234 4 550 09-29-2019, 02:08 PM
Last Post: tomk
  pilight for Raspbian Buster (raspberry pi 4) ? starob 29 3,406 07-15-2019, 08:45 PM
Last Post: curlymo
  pilight-receive Filteroption not working Alex 2 699 07-14-2019, 08:35 AM
Last Post: Alex
  pilight usb nano format conversion ettman8 2 578 07-14-2019, 08:32 AM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)