• 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
#11
@Alex, then revert back to 8.1.3 to see if that works better.
 
Reply
#12
Just this Moment my Pi running on 8.1.14 Main Branch chrashed, but gdb stays empty.
Code:
root@raspberrypi:/home/pi# service pilight start
root@raspberrypi:/home/pi# gdb --args pilight-daemon -D
GNU gdb (Raspbian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from pilight-daemon...(no debugging symbols found)...done.
(gdb) q


root@raspberrypi:/home/pi# tail -f /var/log/pilight.log
[Jun 11 04:57:44:260352] pilight-daemon: INFO: rule #6 zeitschaltuhr4 was parsed in 0.006821 seconds
[Jun 11 04:57:44:267159] pilight-daemon: INFO: rule #7 zeitschaltuhr5 was parsed in 0.006770 seconds
[Jun 11 04:57:44:271113] pilight-daemon: INFO: rule #8 Oktolabel was parsed in 0.003931 seconds
[Jun 11 04:57:44:276239] pilight-daemon: INFO: version v8.1.4
[Jun 11 04:57:44:384184] pilight-daemon: INFO: no pilight daemon found, daemonizing
[Jun 11 04:57:44:395334] pilight-daemon: INFO: daemon listening to port: 39759
[Jun 11 04:57:44:406790] pilight-daemon: INFO: secured webserver started on port: 5002 (fd 16)
[Jun 11 04:57:44:406886] pilight-daemon: INFO: regular webserver started on port: 5001 (fd 17)
[Jun 11 04:57:44:407301] pilight-daemon: INFO: new client, ip: 127.0.0.1, port: 37166
[Jun 11 04:57:44:514565] pilight-daemon: INFO: new client, ip: 192.168.1.118, port: 41016


root@raspberrypi:/home/pi# service pilight status
● pilight.service - pilight
   Loaded: loaded (/etc/systemd/system/pilight.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Tue 2019-06-11 10:40:39 CEST; 40min ago
  Process: 8315 ExecStart=/usr/local/sbin/pilight-daemon (code=exited, status=0/SUCCESS)
 Main PID: 8316 (code=killed, signal=ABRT)[/font][/size]

Jun 11 06:57:44 raspberrypi systemd[1]: Starting pilight...
Jun 11 06:57:44 raspberrypi systemd[1]: Started pilight.
Jun 11 10:40:39 raspberrypi pilight-daemon[8315]: pilight-daemon: /home/pilight/source/daemon-dev/libs/libuv/threadpool.c:313: uv__queue_done: Assertion `(((const QUEUE *)
Jun 11 10:40:39 raspberrypi pilight-daemon[8315]: -- REASON_SEND_CODE --
Jun 11 10:40:39 raspberrypi systemd[1]: pilight.service: Main process exited, code=killed, status=6/ABRT
Jun 11 10:40:39 raspberrypi systemd[1]: pilight.service: Unit entered failed state.
Jun 11 10:40:39 raspberrypi systemd[1]: pilight.service: Failed with result 'signal'.
lines 1-13/13 (END)
[/font][/size]
 
Reply
#13
You have to run pilight inside gdb, not besides a running pilight instances. Check this page for a howto:
https://manual.pilight.org/development/debugging.html
 
Reply
#14
(06-11-2019, 05:18 PM)curlymo Wrote: You have to run pilight inside gdb, not besides a running pilight instances. Check this page for a howto:
https://manual.pilight.org/development/debugging.html

Ah. understood. Now I´m running two pi´s with the same configuration and waiting for a crash...;-)
 
Reply
#15
recorded a crash Tonight:

Code:
[Jun 11 23:30:29:744519] pilight-daemon: DEBUG: broadcasted: {"origin":"receiver","protocol":"date                                                                                                                                                                                                                           time","message":{"longitude":13.150000,"latitude":52.660000,"year":2019,"month":6,"day":12,"weekda                                                                                                                                                                                                                           y":4,"hour":1,"minute":30,"second":29,"dst":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.
But unfortunately, I forgot to set my Main Branch pi to Standalone=1. This Output is of the main branch pi (with standalone=0), while the other pi died completely Tonight. Probably not helpful...
 
Reply
#16
Next time, can you post more of the debug output? And also follow the other steps written in the manual? Now, sadly, the actual error is off screen.
 
Reply
#17
So i got an error myself again and i tracked it down to the 433gpio. Now i have to find the exact location inside 433gpio that errors. Continuing the search  Cool
 
Reply
#18
Hi curlymo!

I now have the logs of 3 crashes. I first started with "service pilight start" and the webserver-connectivity was lost after some seconds. Then I did 3 runs with pilight-daemon -D. First one ran for 3 hours, second for 8.5 hours und the third crashed after 15 hours.

I append the 3 stripped-down logs 30, 31 and 32. Each contains the start and the end of original logs, which where some 100 MB big

Uli


Attached Files
.zip   30+31+32Stripped.zip (Size: 14.57 KB / Downloads: 3)
 
Reply
#19
Are you both using the 433gpio hardware module?
 
Reply
#20
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)
 
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)