• 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
cannot bind to the ssdp multicast network
#1
I am currently monitoring that the pilight service terminates itself without a log entry in syslog. Below you will find a more detailled analysis. The failure of the pilight service is taking place at random intervals. In config.json, log-level is set to 4.

As far as i can see it the error occurs in conjunction with the failing of the ssdp multicast network (in the log files below at 23:35:58).

Symptoms:
pilight terminates itself due to unknow reasons.
At that time no WEBGUI client is connected.
pilight.err has no relevant entries (the last one is from Sept-9).

pilight.log reports the parsing of all 28 rules defined and indicates that there is a problem with the ssdp subsystem (those are the only entries logged in pilight.log, it seems that pilight.log gets overwritten whenever pilight starts).

For the same time period syslog has no unusual log entries. Some explanation regarding my network setup:
- Ethernet lan0 is disabled.
- The pi is connecting to the network using the wlan0 adapter.
- The pi is connecting to a remote network using openVPN and the tun0 adaptor via wlan0
- There is a script file checking the status of the wlan0 and tun0 adapter and in case of failure the pi reboots, messages from that script files are logged with the prefix: md-logger:

The script file is checking the ip address of the wlan adapter in regular intervals of 5 minutes, the loop counter is incremented every 5 minutes, indicating how long the network link was up. If the network link is down for more than 10 minutes, the script is triggering a shutdown/reboot sequence. At the time of the ssdp failure, i can not detect any unusual network conditions in syslog.

I am running my PI using.
- the RASPBIAN wheezy distribution (last update/upgrade on Sept-14th).
- Linux md 4.1.7+ #813 PREEMPT Mon Sep 14 19:14:42 BST 2015 armv6l GNU/Linux
- pilight-daemon version v7.0-46-g31be1bf

I noticed that port 1900 is not defined for the socket call in ssdp.c/117.
@curlymo:
Questions:
1. Is this by intention or a bug ?
2. Any idea where to code to monitor pilight behaviour ?

Please find below an extract (.... denotes lines removed) from the log files:
pilight.log:
Code:
[Sep 21 23:35:58:537054] pilight-daemon: INFO: rule #1 RuleCheckalarmEG_On was parsed in 0.005558 seconds
....
[Sep 21 23:35:58:627950] pilight-daemon: INFO: rule #27 RuleLatchMovementEG was parsed in 0.001314 seconds
[Sep 21 23:35:58:629440] pilight-daemon: INFO: rule #28 RuleLatchMovementOG2Re was parsed in 0.001355 seconds
[Sep 21 23:35:58:764604] pilight-daemon: ERROR: cannot bind to the ssdp multicast network
syslog:
Code:
Sep 21 23:19:08 md logger: wlan0 -----> 0.01 Loop cnt: 0 - 84
Sep 21 23:19:08 md logger: wlan0 -----> 0.10 Check wlan0 IP Adresse: 192.168.43.101 10.8.0.18
Sep 21 23:19:08 md logger: wlan0 -----> 1.10 - IP okay.
Sep 21 23:21:23 md init: Id "U0" respawning too fast: disabled for 5 minutes
Sep 21 23:24:08 md logger: wlan0 -----> 0.01 Loop cnt: 1 - 85
Sep 21 23:24:08 md logger: wlan0 -----> 0.10 Check wlan0 IP Adresse: 192.168.43.101 10.8.0.18
Sep 21 23:24:08 md logger: wlan0 -----> 1.10 - IP okay.
Sep 21 23:28:04 md init: Id "U0" respawning too fast: disabled for 5 minutes
Sep 21 23:29:08 md logger: wlan0 -----> 0.01 Loop cnt: 2 - 86
Sep 21 23:29:08 md logger: wlan0 -----> 0.20 Wait 5 Min
Sep 21 23:34:07 md logger: wlan0 -----> 0.00 Loop
Sep 21 23:34:07 md logger: wlan0 -----> 0.10 Check wlan0 IP Adresse: 192.168.43.101 10.8.0.18
Sep 21 23:34:07 md logger: wlan0 -----> 1.10 - IP okay.
Sep 21 23:34:46 md init: Id "U0" respawning too fast: disabled for 5 minutes
Sep 21 23:34:48 md wpa_supplicant[2701]: wlan0: WPA: Group rekeying completed with f4:06:8d:39:6c:40 [GTK=CCMP]
Sep 21 23:39:01 md /USR/SBIN/CRON[5738]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Sep 21 23:39:07 md logger: wlan0 -----> 0.01 Loop cnt: 0 - 87
Sep 21 23:39:07 md logger: wlan0 -----> 0.10 Check wlan0 IP Adresse: 192.168.43.101 10.8.0.18
Sep 21 23:39:07 md logger: wlan0 -----> 1.10 - IP okay.
Sep 21 23:41:28 md init: Id "U0" respawning too fast: disabled for 5 minutes
Sep 21 23:44:07 md logger: wlan0 -----> 0.01 Loop cnt: 1 - 88
Sep 21 23:44:07 md logger: wlan0 -----> 0.10 Check wlan0 IP Adresse: 192.168.43.101 10.8.0.18
Sep 21 23:44:07 md logger: wlan0 -----> 1.10 - IP okay.
Sep 21 23:48:09 md init: Id "U0" respawning too fast: disabled for 5 minutes
Sep 21 23:49:07 md logger: wlan0 -----> 0.01 Loop cnt: 2 - 89
Sep 21 23:49:07 md logger: wlan0 -----> 0.20 Wait 5 Min
Sep 21 23:54:06 md logger: wlan0 -----> 0.00 Loop
Sep 21 23:54:06 md logger: wlan0 -----> 0.10 Check wlan0 IP Adresse: 192.168.43.101 10.8.0.18
Sep 21 23:54:06 md logger: wlan0 -----> 1.10 - IP okay.
Sep 21 23:54:50 md init: Id "U0" respawning too fast: disabled for 5 minutes
Sep 21 23:59:06 md logger: wlan0 -----> 0.01 Loop cnt: 0 - 90
Sep 21 23:59:06 md logger: wlan0 -----> 0.10 Check wlan0 IP Adresse: 192.168.43.101 10.8.0.18
Sep 21 23:59:06 md logger: wlan0 -----> 1.10 - IP okay.
Sep 22 00:01:32 md init: Id "U0" respawning too fast: disabled for 5 minutes
Sep 22 00:04:06 md logger: wlan0 -----> 0.01 Loop cnt: 1 - 91
Sep 22 00:04:06 md logger: wlan0 -----> 0.10 Check wlan0 IP Adresse: 192.168.43.101 10.8.0.18
Sep 22 00:04:06 md logger: wlan0 -----> 1.10 - IP okay.
Sep 22 00:08:13 md init: Id "U0" respawning too fast: disabled for 5 minutes
Sep 22 00:09:02 md /USR/SBIN/CRON[5890]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Sep 22 00:09:06 md logger: wlan0 -----> 0.01 Loop cnt: 2 - 92
....
Sep 22 01:09:04 md logger: wlan0 -----> 0.01 Loop cnt: 2 - 101
Sep 22 01:09:04 md logger: wlan0 -----> 0.20 Wait 5 Min
Sep 22 01:14:03 md logger: wlan0 -----> 0.00 Loop
Sep 22 01:14:03 md logger: wlan0 -----> 0.10 Check wlan0 IP Adresse: 192.168.43.101 10.8.0.18
Sep 22 01:14:03 md logger: wlan0 -----> 1.10 - IP okay.
Sep 22 01:15:12 md init: Id "U0" respawning too fast: disabled for 5 minutes
Sep 22 01:15:23 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:15:31 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:15:38 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:15:53 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:16:02 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:16:17 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:16:26 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:16:35 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:16:50 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:17:02 md /USR/SBIN/CRON[6206]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 22 01:17:08 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:17:16 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:17:26 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:17:46 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:18:00 md dhclient: DHCPREQUEST on wlan0 to 192.168.43.1 port 67
Sep 22 01:18:16 md ovpn-client[2251]: 38 variation(s) on previous 20 message(s) suppressed by --mute
Sep 22 01:18:16 md ovpn-client[2251]: [Alix-Board] Inactivity timeout (--ping-restart), restarting
Sep 22 01:18:16 md ovpn-client[2251]: TCP/UDP: Closing socket
Sep 22 01:18:16 md ovpn-client[2251]: SIGUSR1[soft,ping-restart] received, process restarting
 
Reply
#2
We have to see if the error still occurs in the pilight rewrite.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Issue send actions over Socket API in AdHoc network ggtrts 10 526 03-13-2019, 06:32 AM
Last Post: curlymo
  [Solved] No ssdp connection found Hexcode 145 139,704 12-23-2017, 02:10 PM
Last Post: HuberDe
  AdHoc network with 2 Raspberry and 2 GPIO transmitter not working webdandy 29 5,920 09-06-2017, 02:39 PM
Last Post: wseifert
  Standalone but SSDP brenner23 6 2,136 04-16-2017, 11:34 PM
Last Post: brenner23
  [Solved] pilight ssdp celle 6 7,722 02-23-2017, 03:22 PM
Last Post: gneandr
  Raspbian jessie - pilight 7 - no pilight ssdp connections found shirocko 20 15,118 01-29-2017, 10:23 PM
Last Post: gneandr
  BUG: BMP180 in AdHoc Network Alex 5 1,466 06-19-2016, 02:24 PM
Last Post: Alex
  ssdp discovery clach04 5 4,430 05-23-2016, 04:23 PM
Last Post: pilino1234
  AdHoc network with different senders Mr.Montesa 6 2,583 02-11-2016, 01:29 PM
Last Post: Karel
  Disable adhoc network? heikoh81 5 3,326 09-17-2015, 09:01 PM
Last Post: heikoh81

Forum Jump:


Browsing: 1 Guest(s)