• 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
communication between main daemon and clientized daemon stops
#21
Are you using the pilight-gdb package?
 
Reply
#22
(02-11-2019, 09:30 PM)curlymo Wrote: Are you using the pilight-gdb package?

Not yet, will do it and trace again.
Bye
Tom
 
Reply
#23
Hi

just a side note: pilight-gdb is now running since >1 day. strange is that pilight-control can't be executed by user pi any more, although the filesystem execute rights are correct:

Code:
pi@rpi3bp:~ $ sudo ls -lsiah /usr/local/bin/pilight-control
284285 44K -rwxrwxrwx 1 root root 42K Dez  1 20:42 /usr/local/bin/pilight-control
pi@rpi3bp:~ $ sudo /usr/local/bin/pilight-control
Usage: pilight-control -d device -s state
pi@rpi3bp:~ $ /usr/local/bin/pilight-control
-bash: /usr/local/bin/pilight-control: Keine Berechtigung
"no access"
some of my scripts are using pilight-control and they are running with user pi. I hat experienced that pilight-control does not exit in 0.1% when it is executed.


Bye
Tom
 
Reply
#24
What does this say?
Code:
ldd /usr/local/bin/pilight-control
 
Reply
#25
Code:
pi@rpi3bp:~ $ ldd /usr/local/bin/pilight-control
ldd: /usr/local/bin/pilight-control: Datei oder Verzeichnis nicht gefunden
pi@rpi3bp:~ $ sudo ldd /usr/local/bin/pilight-control
    linux-vdso.so.1 (0x7efb5000)
    /usr/lib/arm-linux-gnueabihf/libarmmem.so (0x76f63000)
    libpilight.so => /usr/local/lib/libpilight.so (0x766f3000)
    libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0x766cc000)
    libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0x7664d000)
    libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0x76624000)
    librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0x7660d000)
    libwiringx.so => /usr/lib/libwiringx.so (0x765e0000)
    libmbedtls.so.10 => /usr/lib/arm-linux-gnueabihf/libmbedtls.so.10 (0x765ab000)
    libmbedcrypto.so.0 => /usr/lib/arm-linux-gnueabihf/libmbedcrypto.so.0 (0x76553000)
    libmbedx509.so.0 => /usr/lib/arm-linux-gnueabihf/libmbedx509.so.0 (0x76532000)
    libluajit-5.1.so.2 => /usr/lib/arm-linux-gnueabihf/libluajit-5.1.so.2 (0x764c7000)
    libpcap.so.0.8 => /usr/lib/arm-linux-gnueabihf/libpcap.so.0.8 (0x7647f000)
    libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x76340000)
    /lib/ld-linux-armhf.so.3 (0x76f79000)
    libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0x76313000)


Thanks
Tom
 
Reply
#26
Are you sure you installed the package through apt?
Code:
xbian@xbian /root $ pilight-control
Usage: pilight-control -d device -s state
xbian@xbian /root $ sudo ls -lsiah /usr/local/bin/pilight-control
[sudo] password for xbian:
Sorry, try again.
[sudo] password for xbian:
116450 44K -rwxr-xr-x 1 root root 42K Feb 15 04:03 /usr/local/bin/pilight-control
xbian@xbian /root $
 
Reply
#27
Hi curlymo

it took a little longer to debug again. pilight ran 4 days before crashing. here is the gdb output:
Code:
[May 06 05:43:03:624297] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"generic_label","message":{"id":100,"label":"file_chg_roof: 2019-05-06_05:42 | file_chg_bw: error | ws_roof: 3.2 | ws_buttwil: 19 | tempr_roof: 2.2 | age_bw: 999min","color":"black"},"repeat":1,"uuid":"0000-b8-27-eb-caec10"}
[May 06 05:43:03:637044] pilight-daemon: DEBUG: new client, ip: 10.23.6.26, port: 55070
[May 06 05:43:03:637118] pilight-daemon: DEBUG: client fd: 29
[May 06 05:43:03:648638] pilight-daemon: DEBUG: new client, ip: 10.23.6.26, port: 55072
[May 06 05:43:03:648718] pilight-daemon: DEBUG: client fd: 29
[May 06 05:43:03:660438] pilight-daemon: DEBUG: new client, ip: 10.23.6.26, port: 55076
[May 06 05:43:03:660541] pilight-daemon: DEBUG: client fd: 29

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)
(gdb)
(gdb)
(gdb)
(gdb) backtrace
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x763c1824 in __GI_abort () at abort.c:89
#2  0x7676ee50 in uv__io_poll (loop=0x76fa7298 <default_loop_struct>,
   timeout=565)
   at /home/pilight/source/daemon-dev/libs/libuv/unix/linux-core.c:245
#3  0x767655f4 in uv_run (loop=0x76fa7298 <default_loop_struct>,
   mode=UV_RUN_DEFAULT)
   at /home/pilight/source/daemon-dev/libs/libuv/unix/core.c:362
#4  0x00014fd8 in main (argc=2, argv=0x7efff744)
   at /home/pilight/source/daemon-dev/daemon.c:3519
(gdb) frame 4
#4  0x00014fd8 in main (argc=2, argv=0x7efff744)
   at /home/pilight/source/daemon-dev/daemon.c:3519
3519    /home/pilight/source/daemon-dev/daemon.c: Datei oder Verzeichnis nicht gefunden.
(gdb) frame 3
#3  0x767655f4 in uv_run (loop=0x76fa7298 <default_loop_struct>,
   mode=UV_RUN_DEFAULT)
   at /home/pilight/source/daemon-dev/libs/libuv/unix/core.c:362
362     /home/pilight/source/daemon-dev/libs/libuv/unix/core.c: Datei oder Verzeichnis nicht gefunden.
(gdb) frame 2
#2  0x7676ee50 in uv__io_poll (loop=0x76fa7298 <default_loop_struct>,
   timeout=565)
   at /home/pilight/source/daemon-dev/libs/libuv/unix/linux-core.c:245
245     /home/pilight/source/daemon-dev/libs/libuv/unix/linux-core.c: Datei oder Verzeichnis nicht gefunden.
(gdb) frame 1
#1  0x763c1824 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)

Code:
pilight-daemon version v8.1.4


Bye
Tom
 
Reply
#28
So, was pilight version 8.0.0 the last known working version. Sadly, that debug output doesn't give me much to go through on.
 
Reply
#29
gdb is still running... would it help you to have a look directly onto it?
 
Reply
#30
No, the only thing that would help at this point is to know what the last working version was. Than i can check what changes where made between those versions to have a more narrow search area to pinpoint the issue.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight-send and pilight-daemon DieterK 0 558 06-20-2018, 12:44 AM
Last Post: DieterK
Bug Bug report: WIFI dongle stops when gpio_switch.gpio = 20 woutput 16 5,039 01-03-2018, 10:11 PM
Last Post: zackdvd
  Service doesn´t stop the daemon Alex 18 4,264 08-08-2017, 08:17 PM
Last Post: curlymo
  Chasing a Bug in daemon.c curlymo 2 1,166 12-13-2016, 12:48 AM
Last Post: wo_rasp
  pilight-daemon client in other subnet PT-Biker 1 868 12-11-2016, 09:42 PM
Last Post: curlymo
  pilight-daemon fails to start 2 of 3 times tietze111 4 1,737 12-11-2016, 09:06 PM
Last Post: tietze111
  pilight-daemon answers json request with html page michib 5 2,895 04-22-2016, 10:25 PM
Last Post: curlymo
Question [SOLVED]pilight-daemon: ERROR: config is not in a valid json format herrmeier 4 7,215 11-28-2015, 11:28 PM
Last Post: herrmeier
  Daemon hanging after sending raw derfrink 4 2,220 03-13-2015, 02:43 PM
Last Post: wo_rasp
  pilight - emulating api?, custom daemon as a data input sirkubax 2 2,900 01-25-2015, 08:24 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)