• 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
[v6.0 > v7.0] Errors with the latest nightly
#1
There are new commits on github. Eager to hear all issues!


10-03-'15
FYI my goal is to release a new pilight version very soon so i can also officially release the Windows version with the pilight usb nano.

@Everybody, please let me know what fixes / features should absolutely be implemented. Bugfixes are ofc most important. My list contains:
- mail plugin
- extended dim

I would also really like to implement the S0mfy protocol.

What won't be implemented still are:
- Timer protocol
- Eventing improvement
- Time math
 
#2
I get this error with my XBMC pc turned off:

Code:
[ Feb 27 23:07:20:50286] pilight-daemon: NOTICE: could not connect to XBMC/Kodi server @192.168.137.101
-- STACKTRACE (3 FRAMES) --
__default_sa_restorer_v2       ip = 0xb6c16b20, sp = 0xadb298c8
strcpy                         ip = 0xb6c60244, sp = 0xadb29bb8
segmentation fault
 
#3
Can you post debug output. I can't seem to replicate it Crying
 
#4
pilight-daemon -D shows:

Code:
root@raspbian:~# pilight-daemon -D
[Feb 28 01:47:45:107839] pilight-daemon: INFO: version 6.0, commit v6.0-4-gaf4f2c0
[Feb 28 01:47:45:110645] pilight-daemon: DEBUG: ssdp sent search
[Feb 28 01:47:45:209724] pilight-daemon: NOTICE: no pilight daemon found, daemonizing
[Feb 28 01:47:45:210798] pilight-daemon: INFO: daemon listening to port: 50927
[Feb 28 01:47:45:213535] pilight-daemon: DEBUG: running on a raspberrypi
[Feb 28 01:47:45:220781] pilight-daemon: DEBUG: new thread lirc, 1 thread running
[Feb 28 01:47:45:223438] pilight-daemon: DEBUG: new thread cpu_temp, 2 threads running
[Feb 28 01:47:45:224540] pilight-daemon: DEBUG: new thread ds18b20, 3 threads running
[Feb 28 01:47:45:225816] pilight-daemon: DEBUG: new thread ds18b20, 4 threads running
[Feb 28 01:47:45:226955] pilight-daemon: DEBUG: new thread xbmc, 5 threads running
[Feb 28 01:47:45:228356] pilight-daemon: DEBUG: new thread sunriseset, 6 threads running
[Feb 28 01:47:45:232747] pilight-daemon: DEBUG: new thread openweathermap, 7 threads running
[Feb 28 01:47:45:240188] pilight-daemon: DEBUG: new thread wunderground, 8 threads running
[Feb 28 01:47:45:241452] pilight-daemon: DEBUG: new thread datetime, 9 threads running
[Feb 28 01:47:45:242882] pilight-daemon: DEBUG: new thread arping, 10 threads running
[Feb 28 01:47:45:244970] pilight-daemon: DEBUG: new thread arping, 11 threads running
[Feb 28 01:47:45:246419] pilight-daemon: DEBUG: new thread arping, 12 threads running
[Feb 28 01:47:45:249949] pilight-daemon: DEBUG: new thread arping, 13 threads running
[Feb 28 01:47:45:254192] pilight-daemon: DEBUG: new thread arping, 14 threads running
[Feb 28 01:47:45:257457] pilight-daemon: DEBUG: new thread arping, 15 threads running
[Feb 28 01:47:45:260962] pilight-daemon: DEBUG: new thread arping, 16 threads running
[Feb 28 01:47:45:264694] pilight-daemon: DEBUG: new thread arping, 17 threads running
[Feb 28 01:47:45:266611] pilight-daemon: DEBUG: new thread arping, 18 threads running
[Feb 28 01:47:45:269337] pilight-daemon: DEBUG: new thread socket, 19 threads running
[Feb 28 01:47:45:275179] pilight-daemon: DEBUG: new thread ssdp, 20 threads running
[Feb 28 01:47:45:277462] pilight-daemon: INFO: new client, ip: 127.0.0.1, port: 49370
[Feb 28 01:47:45:279367] pilight-daemon: DEBUG: client fd: 7
[Feb 28 01:47:45:298333] pilight-daemon: DEBUG: client id: 1
[Feb 28 01:47:45:297560] pilight-daemon: DEBUG: new thread sender, 21 threads running
[Feb 28 01:47:45:304216] pilight-daemon: DEBUG: new thread broadcaster, 22 threads running
[Feb 28 01:47:45:315894] pilight-daemon: DEBUG: webserver listening to port 5001
[Feb 28 00:47:45:338364] pilight-daemon: DEBUG: new thread 433gpio, 23 threads running
[Feb 28 00:47:45:353626] pilight-daemon: DEBUG: new thread receive parser, 24 threads running
[Feb 28 00:47:45:354852] pilight-daemon: DEBUG: broadcasted: {"message":{"action":"shutdown","media":"none","server":"192.168.137.101","port":9090},"origin":"receiver","protocol":"xbmc","uuid":"0000-00-00-43-8f62a1"}
[Feb 28 00:47:45:373768] pilight-daemon: DEBUG: new thread events client, 25 threads running
[Feb 28 00:47:45:385191] pilight-daemon: DEBUG: new thread events loop, 26 threads running
[Feb 28 00:47:45:387038] pilight-daemon: DEBUG: new thread webserver worker #0, 27 threads running
[Feb 28 00:47:45:397368] pilight-daemon: DEBUG: cpu: 0.000000%, ram: 2.544069%
[Feb 28 00:47:45:405996] pilight-daemon: DEBUG: ssdp sent notify
[Feb 28 00:47:45:408041] pilight-daemon: DEBUG: ssdp sent notify
[Feb 28 00:47:45:411902] pilight-daemon: DEBUG: ssdp sent search
[Feb 28 00:47:45:399112] pilight-daemon: DEBUG: new thread webserver client, 28 threads running
[Feb 28 00:47:45:419023] pilight-daemon: DEBUG: ssdp sent notify
[Feb 28 00:47:45:451711] pilight-daemon: DEBUG: ssdp sent notify
[Feb 28 00:47:45:449489] pilight-daemon: DEBUG: new thread webserver broadcast, 29 threads running
[Feb 28 00:47:45:418466] pilight-daemon: DEBUG: ssdp sent search
[Feb 28 00:47:45:467623] pilight-daemon: DEBUG: new thread firmware upgrader, 30 threads running
[Feb 28 00:47:45:515478] pilight-daemon: INFO: new client, ip: 192.168.137.120, port: 39819
[Feb 28 00:47:45:516634] pilight-daemon: DEBUG: client fd: 13
[Feb 28 00:47:45:520092] pilight-daemon: DEBUG: client id: 2
[Feb 28 00:47:45:524698] pilight-daemon: DEBUG: socket write succeeded: {"action":"identify","options":{"config":1},"media":"all"}

[Feb 28 00:47:45:527736] pilight-daemon: DEBUG: socket recv: {"action":"identify","options":{"config":1},"media":"all"}
[Feb 28 00:47:45:531375] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}

[Feb 28 00:47:45:562473] pilight-daemon: INFO: new client, ip: 192.168.137.120, port: 39820
[Feb 28 00:47:45:564058] pilight-daemon: DEBUG: client fd: 14
[Feb 28 00:47:45:565341] pilight-daemon: DEBUG: client id: 3
[Feb 28 00:47:45:572318] pilight-daemon: DEBUG: socket write succeeded: {"action":"identify","options":{"config":1,"core":1},"media":"web"}

[Feb 28 00:47:45:585547] pilight-daemon: DEBUG: socket recv: {"action":"identify","options":{"config":1,"core":1},"media":"web"}
[Feb 28 00:47:45:588395] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}

[Feb 28 00:47:45:783052] pilight-daemon: DEBUG: loading timezone database...
[Feb 28 00:47:46:233991] pilight-daemon: ERROR: 1-wire device /sys/bus/w1/devices/28-00000534a840/ does not exists
[Feb 28 00:47:46:242279] pilight-daemon: ERROR: 1-wire device /sys/bus/w1/devices/28-000005359eb7/ does not exists
[Feb 28 00:47:46:257827] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":3,"uuid":"0000-00-00-43-8f62a1","devices":["rpitemp"],"values":{"timestamp":1425084466,"temperature":66.984}}

[Feb 28 00:47:46:260414] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":3,"uuid":"0000-00-00-43-8f62a1","devices":["rpitemp"],"values":{"timestamp":1425084466,"temperature":66.984}}
[Feb 28 00:47:46:272116] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":3,"uuid":"0000-00-00-43-8f62a1","devices":["rpitemp"],"values":{"timestamp":1425084466,"temperature":66.984}}

[Feb 28 00:47:46:275138] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":3,"uuid":"0000-00-00-43-8f62a1","devices":["rpitemp"],"values":{"timestamp":1425084466,"temperature":66.984}}
[Feb 28 00:47:46:286148] pilight-daemon: DEBUG: broadcasted: {"message":{"id":1,"temperature":66.984},"origin":"receiver","protocol":"cpu_temp","uuid":"0000-00-00-43-8f62a1"}
[Feb 28 00:47:46:429424] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":3,"devices":["outsideOW"],"values":{"timestamp":1425084466,"temperature":3.92,"humidity":98.00,"sunrise":7.27,"sunset":18.18,"sun":"set","update":0}}

[Feb 28 00:47:46:431209] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":3,"devices":["outsideOW"],"values":{"timestamp":1425084466,"temperature":3.92,"humidity":98.00,"sunrise":7.27,"sunset":18.18,"sun":"set","update":0}}
[Feb 28 00:47:46:435556] pilight-daemon: ERROR: cpu usage too high 77.890933%
[Feb 28 00:47:46:438298] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":3,"devices":["outsideOW"],"values":{"timestamp":1425084466,"temperature":3.92,"humidity":98.00,"sunrise":7.27,"sunset":18.18,"sun":"set","update":0}}

[Feb 28 00:47:46:443085] pilight-daemon: ERROR: checking again in 10 seconds
[Feb 28 00:47:46:445246] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":3,"devices":["outsideOW"],"values":{"timestamp":1425084466,"temperature":3.92,"humidity":98.00,"sunrise":7.27,"sunset":18.18,"sun":"set","update":0}}
[Feb 28 00:47:46:451845] pilight-daemon: DEBUG: broadcasted: {"message":{"location":"woerden","country":"nl","temperature":3.92,"humidity":98.00,"update":0,"sunrise":7.27,"sunset":18.18,"sun":"set"},"origin":"receiver","protocol":"openweathermap","uuid":"0000-00-00-43-8f62a1"}
[Feb 28 00:47:47:335220] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":3,"devices":["outsideWU"],"values":{"timestamp":1425084467,"humidity":91,"temperature":1.20,"sunrise":7.29,"sunset":18.17,"sun":"set","update":0}}

[Feb 28 00:47:47:338078] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":3,"devices":["outsideWU"],"values":{"timestamp":1425084467,"humidity":91,"temperature":1.20,"sunrise":7.29,"sunset":18.17,"sun":"set","update":0}}
[Feb 28 00:47:47:345263] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":3,"devices":["outsideWU"],"values":{"timestamp":1425084467,"humidity":91,"temperature":1.20,"sunrise":7.29,"sunset":18.17,"sun":"set","update":0}}

[Feb 28 00:47:47:349289] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":3,"devices":["outsideWU"],"values":{"timestamp":1425084467,"humidity":91,"temperature":1.20,"sunrise":7.29,"sunset":18.17,"sun":"set","update":0}}
[Feb 28 00:47:47:353352] pilight-daemon: DEBUG: broadcasted: {"message":{"api":"7e606c39f976460d","location":"woerden","country":"nl","temperature":1.20,"humidity":91,"update":0,"sunrise":7.29,"sunset":18.17,"sun":"set"},"origin":"receiver","protocol":"wunderground","uuid":"0000-00-00-43-8f62a1"}
[Feb 28 00:47:48:230640] pilight-daemon: NOTICE: could not connect to XBMC/Kodi server @192.168.137.101
[Feb 28 00:47:49:920689] pilight-daemon: DEBUG: 4.902296:52.078150 seems to be in timezone: Europe/Amsterdam
[ Feb 28 00:47:50:34450] pilight-daemon: DEBUG: 4.902296:52.078150 seems to be in timezone: Europe/Amsterdam
[ Feb 28 00:47:50:73828] pilight-daemon: INFO: datetime 4.902296:52.078150 adjusted by -1 seconds
[ Feb 28 00:47:50:75930] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":8,"devices":["datetime"],"values":{"timestamp":1425084470,"year":2015,"month":2,"day":28,"hour":0,"minute":47,"second":50,"weekday":7}}

[ Feb 28 00:47:50:76088] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":8,"devices":["datetime"],"values":{"timestamp":1425084470,"year":2015,"month":2,"day":28,"hour":0,"minute":47,"second":50,"weekday":7}}
[ Feb 28 00:47:50:78663] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":8,"devices":["datetime"],"values":{"timestamp":1425084470,"year":2015,"month":2,"day":28,"hour":0,"minute":47,"second":50,"weekday":7}}

[ Feb 28 00:47:50:79905] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":8,"devices":["datetime"],"values":{"timestamp":1425084470,"year":2015,"month":2,"day":28,"hour":0,"minute":47,"second":50,"weekday":7}}
[ Feb 28 00:47:50:81509] pilight-daemon: DEBUG: broadcasted: {"message":{"longitude":4.902296,"latitude":52.078150,"year":2015,"month":2,"day":28,"weekday":7,"hour":0,"minute":47,"second":50},"origin":"receiver","protocol":"datetime","uuid":"0000-00-00-43-8f62a1"}
-- STACKTRACE (3 FRAMES) --
__default_sa_restorer_v2       ip = 0xb6c24b20, sp = 0xae9fe8c8
strcpy                         ip = 0xb6c6e244, sp = 0xae9febb8

If you need other commands, please let me know.
 
#5
Debugging guide can be found on the frontpage.
 
#6
run - D:

Code:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb13cc470 (LWP 11821)]
0xb6d02244 in strcpy () from /lib/arm-linux-gnueabihf/libc.so.6

backtrace:

Code:
(gdb) backtrace
#0  0xb6d02244 in strcpy () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0xb6f01ce0 in arp_resolv (if_name=<optimized out>, mac=0xfffe7891 <Address 0xfffe7891 out of bounds>, ip=0x0)
    at /root/pilight/libs/pilight/arp.c:573
#2  0xb6f447a8 in arpingParse (param=0xd0660) at /root/pilight/libs/protocols/arping.c:121
#3  0xb6e34c00 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
#4  0xb6d57348 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
#5  0xb6d57348 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

frames:

Code:
(gdb) frame 5
#5  0xb6d57348 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
(gdb) frame 4
#4  0xb6d57348 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
(gdb) frame 3
#3  0xb6e34c00 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
(gdb) frame 2
#2  0xb6f447a8 in arpingParse (param=0xd0660) at /root/pilight/libs/protocols/arping.c:121
121                             if(arp_resolv(if_name, srcmac, &p) == 0) {
(gdb) frame 1
#1  0xb6f01ce0 in arp_resolv (if_name=<optimized out>, mac=0xfffe7891 <Address 0xfffe7891 out of bounds>, ip=0x0)
    at /root/pilight/libs/pilight/arp.c:573
573                                     strcpy(*ip, inet_ntoa(helist[i]->addr));
(gdb) frame 0
#0  0xb6d02244 in strcpy () from /lib/arm-linux-gnueabihf/libc.so.6

This mac address is causing the issue:
Code:
"mac": "54:e6:fc:a7:bb:7e"

It's a valid MAC addres, device is a TP-Link TL-WR1042ND.
 
#7
Good to know that it isn't in anyway related to the XBMC protocol because i couldn't find the issue there.

Should be fixed.
 
#8
I can confirm that it's fixed. Thanks!
 
#9
I think that a very nasty bug was injected into the development branch after SHA c7e5366.

Everything is okay until and including SHA c7e5366.
SHA 05272ea and 703af9b won't compile on my machine.
Starting with SHA 227722f the bug is present.

The bug shows up on the WEB GUI within my 5 TFA sensors.

A) Without a config.json file:
pilight-receive reports for all 5 TFA sensors a proper humidity value.

B) Using my standard config.json file:
For the first 2 TFA sensor entries in config.json, no humidity value is reported, for the 3 remaining ones everything is okay.

When i remove the 4th TFA sensor entry from config.json, the values for the 4 remaining sensors are okay.

First i suspected an interference with the device id's, but i tested that and the device id (1, 2, 3) is not problem.

Thus i suspect a memory overwrite.

pilight-daemon -D:
For the 4th sensor in config.json [THS7Bad]:
Code:
[Mar 09 08:36:24:230735] pilight-daemon: DEBUG: caught minimum # of repeats 1 of tfa
[Mar 09 08:36:24:231088] pilight-daemon: DEBUG: called tfa parseCode()
[Mar 09 08:36:24:232666] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":3,"devices":["THS7Bad"],"values":{"timestamp":1425890184,"temperature":20.55,"humidity":39.00,"battery":1}}
....

For the 2nd sensor in config.json [THS5Keller]:
Code:
[Mar 09 08:36:28:540214] pilight-daemon: DEBUG: caught minimum # of repeats 1 of tfa
[Mar 09 08:36:28:540593] pilight-daemon: DEBUG: called tfa parseCode()
[Mar 09 08:36:28:542150] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":3,"devices":["THS5Keller"],"values":{"timestamp":1425890188,"temperature":14.88,"battery":1}}
....
 
#10
Can you move this to the nightly errors thread i already opened?
 
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  hardware module issues in nightly apartmedia 17 1,216 04-05-2019, 06:59 PM
Last Post: curlymo
  Update to v8.0.10-nightly-a1279212 Ulrich.Arnold 3 1,245 06-04-2018, 08:31 PM
Last Post: curlymo
  Updates for nightly Ulrich.Arnold 1 555 01-26-2018, 07:31 PM
Last Post: curlymo
  how to complete remove nightly terrar 8 5,477 04-03-2016, 07:04 PM
Last Post: mvasi90
  new install fails - dev/nightly gneandr 11 9,311 01-29-2016, 11:30 AM
Last Post: WEBcast
  pilight7 from Stable --> Nightly gneandr 10 3,163 01-19-2016, 04:15 PM
Last Post: gneandr
  [v7.0 > v...] Errors with the latest nightly curlymo 20 6,550 07-27-2015, 02:37 PM
Last Post: diman87
  Rest API in nightly Image seems not to work spooniester 2 2,001 06-25-2015, 10:07 AM
Last Post: spooniester
  Nightly upgrades troccolo 2 1,593 04-17-2015, 09:34 AM
Last Post: troccolo
  [v5.0 > v6.0] Errors with install latest Nightly mike 208 43,370 02-23-2015, 10:11 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)