• 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:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[solved] another pilight ssdp missed connection on RPI
#1
Sometimes, when raspberry pi (jessy) reboot, pilight restart without ssdp conenction. As I use piSchedule, after a reboot sometimes I miss my schedule because of this ssdp. I had to manually restart pilight in order to get ssdp right

I was investigating and seems that is because of dhcp (pilight start before IP is assigned), and the solutions here is disable dhcp and configure static IP. For other reasons this is not able for my configuration.

I have read some about init, systemd, rc stuff and seems that I have found a solution that seems to work.

This is what I have made:


Code:
sudo mkdir /etc/systemd/system/pilight.service.d
sudo nano /etc/systemd/system/pilight.service.d/pilight.conf

and put into this config file this text:


Code:
[Unit]
Require = network-online.target
After = network-online.target

I want to share this if it can help other people.
 
Reply
#2
This would be good to have in pilight by default, can you make a pull request on the pilight repository on GitHub?
 
Reply
#3
I have similar issues (using pilight V 7.0 also running on Raspbian Jessie) but if I make the provided fix I get

Code:
systemd[1]: Started LSB: Starts pilight-daemon.
systemd[1]: [/etc/systemd/system/pilight.service.d/pilight.conf:2] Unknown lvalue 'Require' in section 'Unit'

I then changed "Require" to "Requires" and then this error message is gone (maybe a typo in your code?) but then I get for sudo service pilight status
Code:
Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended.
I get get rid of this warning if I run the recommended command but after an reboot of the Pi the warning is back again.
Do you also have this warning? Is there something I should do about it?
piSchedule still did not work from automatic start (I'm not sure if this is because of the warning or other issues).

I fixed the issue in my case by not using
/etc/systemd/system/pilight.service.d/pilight.conf
but instead activating "Wait for network at boot" in raspi-config and adding $named $network in /etc/init.d/pilight (and /etc/init.d/piSchedule )

Code:
# Required-Start:    $named $network $remote_fs $syslog
# Required-Stop:     $named $network $remote_fs $syslog
I'm not sure if this is a real fix or just causes the pilight service to state later which then works (I read that others used a "sleep 10")
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  update pilight Traeumer 0 26 07-29-2021, 09:41 PM
Last Post: Traeumer
  problem publish to pilight MQTT server Emiks5 8 1,561 07-24-2021, 06:46 PM
Last Post: Emiks5
  Hardware Switch and pilight-send/-control iTommix 3 546 02-14-2021, 09:25 PM
Last Post: iTommix
  pilight error after update to 8.1.5 on Odroid C2 WitchDoctor 4 1,720 02-07-2021, 09:50 PM
Last Post: pilightalpine
  pilight in Docker not accepting connections due to possible SYN flooding akloeckner 3 471 02-07-2021, 04:22 PM
Last Post: akloeckner
  pilight-debug format Rschnauzer 2 454 12-17-2020, 07:09 PM
Last Post: Rschnauzer
  pilight-flash not working danny 14 3,383 12-12-2020, 10:00 AM
Last Post: tox
  pilight does not start, Deamon is not found. Dekkertje 6 772 12-08-2020, 06:55 PM
Last Post: Dekkertje
  Failed pilight-send that say they succeeded hepcat72 2 493 12-05-2020, 05:30 PM
Last Post: hepcat72
  apt.pilight.org/dists/stable/main/binary 301 Moved Permanently Rschnauzer 6 851 11-23-2020, 01:49 PM
Last Post: Rschnauzer

Forum Jump:


Browsing: 1 Guest(s)