• 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
Raspbian jessie - pilight 7 - no pilight ssdp connections found
#11
In this thread, we are discussing jessie related setup issues.

I assume thet your hardware is a Pi2.
What OS (distribution) are you using ?

There are spelling errors in the interface file.
- interfaces.d is a directory, not a file.
- The ip address is wrong, address has one d only, and 255 is the broadcast address.

Why do you configure:
Code:
iface default inet dhcp
If there is no need for it, please try out what happens if you remove it.
The pilight manual states some requirements for dhcpcd. Have you followed those ?
 
Reply
#12
Lightbulb 
Pls. read my post at
https://forum.pilight.org/Thread-pilight-7-0?page=9

MfG Angie
 
Reply
#13
Lightbulb 
Don't start pilight-daemon in runlevel 2 !
Runlevel 2 is defined as multiuser without network
Wikipedia: Linux-Runlevel

pls. edit the startscript /etc/init.d/pilight

Code:
### BEGIN INIT INFO
# Provides:          pilight-daemon
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     3 4 5  
# Default-Stop:      0 1 2 6
# Short-Description: Starts pilight-daemon
# Description:       Starts pilight-daemon
#                  
### END INIT INFO
# Author: sweet pi & CurlyMo & AngieSoft

then
Code:
insserv pilight

MfG Angie
 
Reply
#14
Do you want to do a PR about this?
 
Reply
#15
As this issue is a long term dragging one and no one is doing it, and other users on other operating systems, do not have difficulties any longer either after applying this patch, i have issued the PR and would appreciate that one being incorporated.

@curlymo
I did assume that res/init is the correct directory for this modification.
 
Reply
#16
Exclamation 
If that solves the problem with no pilight ssdp connections found generally that would be great! No question I made that correction immediately.

For piSchedule users it would be important to change also the script
/etc/init.d/piSchedule with same change, the following line should be
Code:
# Default-Start:     3 4 5
without the 2 !

Also of interest: which OS is in use with pilight/piSchedule.
Maybe this detail could help for further error analysis:
At the terminal prompt do the following:
Code:
pi@raspberrypi ~ $ python
Python 2.7.3 (default, Mar 18 2014, 05:13:23)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import platform
>>> platform.uname()[1] + " -- " + str(platform.platform()).replace("'","")
'raspberrypi -- Linux-3.18.11-v7+-armv7l-with-debian-7.8'

Please post the last line you get to understand your environment
(Use exit() at the python prompt to terminate Python)

Thanks for the cooperation Wink
 
Reply
#17
Exclamation 
Just checked with a fresh installation of Jessie Light for pilight and piSchedule.

The good news it's working .. no more complains with ssdp connection ...

BUT ...

.. the /etc/init.d/pilight needs a manual edit to delete the 2 so the first lines should be:
Code:
### BEGIN INIT INFO
# Provides:          pilight-daemon
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     3 4 5
# Default-Stop:      0 1 6
# Short-Description: Starts pilight-daemon
# Description:       Starts pilight-daemon
#                  
### END INIT INFO
Please note the line with # Default-Start:
has NO number 2 !

It would be great if the installation code directly has that change already.

Thanks
 
Reply
#18
Which pilight version are you using ?
Did you do an update of your development branch recently ?
We do not want to start pilight without the network being up and running, however we still want to ensure that the kill scripts are handled, i recommend to add runlevel 2 related scripts to the Default Stop.
 
Reply
#19
(01-29-2017, 08:21 PM)wo_rasp Wrote: Which pilight version are you using ?
As the title say vers.7 (plain)
Quote:Did you do an update of your development branch recently ? ?
Which dev pilight or piSchedule? With pilight I'm using not the dev version at all because it's not backwards compatible! And I don't have a "your development branch".
Quote:And what happens with runlevel 2 when you stop the system ?
Do you speak about "service pilight stop" or "sudo shutdown"?
 
Reply
#20
The reason why I was asking, those changes are part of the development branch.
The master branch won't get updated, if patches are required, users do need to do that based on their individual needs, otherwise we will discussing here too many variants.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight bugs Ascenion 1 204 03-23-2020, 06:29 PM
Last Post: curlymo
  [Solved] pilight service crashing on first webserver access after reboot VrahoK 20 1,678 12-21-2019, 09:46 AM
Last Post: curlymo
  pilight-control modify values coolinx 16 1,465 11-13-2019, 08:02 PM
Last Post: curlymo
  Bug: double free or corruption in pilight-send blackzombie 12 1,330 10-07-2019, 08:15 PM
Last Post: blackzombie
  [Fixed] High CPU usage when pilight usb nano disconnects DieterK 1 520 08-13-2019, 05:43 PM
Last Post: curlymo
  pilight Nano USB interface curlymo 228 117,315 07-10-2019, 06:14 PM
Last Post: curlymo
  problems compiling pilight on Odroid C2 WitchDoctor 101 17,102 03-14-2019, 09:01 PM
Last Post: curlymo
  pilight 8 what chages for custom protocols? polo 11 4,424 02-15-2019, 06:22 PM
Last Post: polo
  pilight-debug shows nothing minhdomanh 3 986 10-18-2018, 07:01 AM
Last Post: felfert
  pilight-send and pilight-daemon DieterK 0 889 06-20-2018, 12:44 AM
Last Post: DieterK

Forum Jump:


Browsing: 1 Guest(s)