• 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
[Solved] No ssdp connection found
Hi curlymo,
you are right. I commented/removed the following line:
iface lo inet loopback
Consequently, it did not work; the error message appeared:
pilight-receive: ERROR: no pilight ssdp connections found

Therefore, I added again the line
iface lo inet loopback

Thanks a lot.

So summarizing:
The error could be solved by using adding "iface lo inet loopback" in /etc/network/interfaces
 
Reply
Great. Will add it to the FAQ.
 
Reply
Well my interface file is empty so far.

if i insert iface lo inet loopback

it doesnt work.

the recive command started ( but didnt reived something before i restarted) now i get the ssdp error

ok when i start the deamon recive works, but not raw when i use the start command the raw command work
 
Reply
Hi,
still the same problem!
Code:
pi@raspberrypi ~ $ sudo pilight-receive
pilight-receive: ERROR: no pilight ssdp connections found

New Raspbian (January 2015); instal pilight (apt-get install pilight)

pilight-daemon -V
Code:
pilight-daemon version 5.0, commit v5.0

nano /etc/network/interfaces:
Code:
auto lo

iface lo inet loopback
iface eth0 inet static
address 192.168.0.xx
netmask 255.255.255.0
gateway 192.168.0.1

allow-hotplug wlan0
iface default inet dhcp

iface wlan0 inet dhcp
wpa-ap-scan 1
wpa-scan-ssid 1
wpa-ssid "xxx"
wpa-psk "xxx"
so I still have a loopback.
I also added the IPtables

iptables -L:
Code:
target     prot opt source               destination
ACCEPT     all  --  localhost            anywhere

so, I have no more ideas
 
Reply
I have a similar problem here. I am working with the actual nightly. Daemon is starting and working without problems, means that I can control all stuff from the webgui. pilight-control is also working for some minutes after startup of the daemon, but seem to loos the connection and throws the "No ssdp..." exception. Any idea what could be the problem?
 
Reply
@thebluehill Are you sure you are running a pilight-daemon when starting pilight-receive? It needs to run, otherwise pilight-receive will give you that error
 
Reply
here is the log file: the cpu usage is too high!

pilight-daemon -D
Code:
[Feb 16 18:21:52:351635] pilight-daemon: DEBUG: ssdp sent search
[Feb 16 18:21:52:450654] pilight-daemon: NOTICE: no pilight daemon found, daemonizing
[Feb 16 18:21:52:453760] pilight-daemon: INFO: daemon listening to port: 50397
[Feb 16 18:21:52:461404] pilight-daemon: DEBUG: new thread lirc, 1 thread running
[Feb 16 18:21:52:465673] pilight-daemon: DEBUG: new thread socket, 2 threads running
[Feb 16 18:21:52:473805] pilight-daemon: DEBUG: new thread ssdp, 3 threads running
[Feb 16 18:21:52:476658] pilight-daemon: DEBUG: new thread sender, 4 threads running
[Feb 16 18:21:52:480783] pilight-daemon: [Feb 16 18:21:52:480783] pilight-daemon: INFO: new client, ip: 127.0.0.1, port: 35190
[Feb 16 18:21:52:487080] pilight-daemon: DEBUG: client fd: 9
[Feb 16 18:21:52:488418] pilight-daemon: DEBUG: client id: 1
DEBUG: new thread broadcaster, 5 threads running
[Feb 16 18:21:52:501833] pilight-daemon: DEBUG: new thread updater, 6 threads running
[Feb 16 18:21:52:505379] pilight-daemon: DEBUG: new thread 433gpio, 7 threads running
[Feb 16 18:21:52:509108] pilight-daemon: DEBUG: new thread receive parser, 8 threads running
[Feb 16 18:21:52:513882] pilight-daemon: DEBUG: new thread webserver worker #0, 9 threads running
[Feb 16 18:21:52:517050] pilight-daemon: DEBUG: webserver listening to port 5001
[Feb 16 18:21:52:522689] pilight-daemon: DEBUG: new thread webserver client, 10 threads running
[Feb 16 18:21:52:524390] pilight-daemon: DEBUG: new thread webserver broadcast, 11 threads running
[Feb 16 18:21:52:526585] pilight-daemon: DEBUG: new thread firmware upgrader, 12 threads running
[Feb 16 18:21:52:532142] pilight-daemon: DEBUG: ssdp sent search
[Feb 16 18:21:54:251448] pilight-daemon: DEBUG: no pilight ssdp connections found
[Feb 16 18:21:54:257582] pilight-daemon: INFO: new client, ip: 127.0.0.1, port: 35193
[Feb 16 18:21:54:261697] pilight-daemon: DEBUG: client fd: 16
[Feb 16 18:21:54:262951] pilight-daemon: DEBUG: client id: 2
[Feb 16 18:21:54:264515] pilight-daemon: DEBUG: socket recv: {"message":"client gui"}
[Feb 16 18:21:54:266866] pilight-daemon: DEBUG: socket write succeeded: {"message":"accept client"}

[Feb 16 18:21:54:268136] pilight-daemon: INFO: client recognized as gui
[Feb 16 18:21:54:269860] pilight-daemon: ERROR: ----- Thread Profiling -----
[Feb 16 18:21:54:271854] pilight-daemon: ERROR: - thread lirc: 0.000000%
[Feb 16 18:21:54:273700] pilight-daemon: ERROR: - thread socket: 0.000000%
[Feb 16 18:21:54:274267] pilight-daemon: ERROR: - thread ssdp: 0.000000%
[Feb 16 18:21:54:274267] pilight-daemon: DEBUG: socket write succeeded: {"message":"client gui"}

[Feb 16 18:21:54:276103] pilight-daemon: ERROR: - thread sender: 0.000000%
[Feb 16 18:21:54:277780] pilight-daemon: ERROR: - thread broadcaster: 0.000000%
[Feb 16 18:21:54:278227] pilight-daemon: ERROR: - thread updater: 0.000000%
[Feb 16 18:21:54:278737] pilight-daemon: ERROR: - thread 433gpio: 0.000000%
[Feb 16 18:21:54:280018] pilight-daemon: ERROR: - thread receive parser: 0.000000%
[Feb 16 18:21:54:280766] pilight-daemon: ERROR: - thread webserver worker #0: 0.000000%
[Feb 16 18:21:54:282358] pilight-daemon: ERROR: - thread webserver client: 0.000000%
[Feb 16 18:21:54:282804] pilight-daemon: ERROR: - thread webserver broadcast: 0.000000%
[Feb 16 18:21:54:283263] pilight-daemon: ERROR: - thread firmware upgrader: 0.000000%
[Feb 16 18:21:54:284515] pilight-daemon: ERROR: ----- Thread Profiling -----
[Feb 16 18:21:54:284912] pilight-daemon: ERROR: cpu usage way too high 99.228212
[Feb 16 18:21:54:286372] pilight-daemon: ERROR: checking again in 10 seconds
[Feb 16 18:22:05:288539] pilight-daemon: ERROR: ----- Thread Profiling -----
[Feb 16 18:22:05:292248] pilight-daemon: ERROR: - thread lirc: 0.017640%
[Feb 16 18:22:05:294249] pilight-daemon: ERROR: - thread socket: 0.000000%
[Feb 16 18:22:05:294662] pilight-daemon: ERROR: - thread ssdp: 0.000000%
[Feb 16 18:22:05:295855] pilight-daemon: ERROR: - thread sender: 0.000000%
[Feb 16 18:22:05:296873] pilight-daemon: ERROR: - thread broadcaster: 0.000000%
[Feb 16 18:22:05:298945] pilight-daemon: ERROR: - thread updater: 0.100311%
[Feb 16 18:22:05:299416] pilight-daemon: ERROR: - thread 433gpio: 94.912219%
[Feb 16 18:22:06:252468] pilight-daemon: ERROR: - thread receive parser: 0.035274%
[Feb 16 18:22:06:259890] pilight-daemon: ERROR: - thread webserver worker #0: 0.019801%
[Feb 16 18:22:06:261558] pilight-daemon: ERROR: - thread webserver client: 0.000000%
[Feb 16 18:22:06:261991] pilight-daemon: ERROR: - thread webserver broadcast: 0.000000%
[Feb 16 18:22:06:262351] pilight-daemon: ERROR: - thread firmware upgrader: 0.011904%
[Feb 16 18:22:06:263568] pilight-daemon: ERROR: ----- Thread Profiling -----
[Feb 16 18:22:06:263967] pilight-daemon: ERROR: cpu usage still way too high 95.114272%, exiting
 
Reply
And for CPU too high, check the CPU too high thread Smile
 
Reply
(02-15-2015, 03:49 PM)degenar Wrote: I have a similar problem here. I am working with the actual nightly. Daemon is starting and working without problems, means that I can control all stuff from the webgui. pilight-control is also working for some minutes after startup of the daemon, but seem to loos the connection and throws the "No ssdp..." exception. Any idea what could be the problem?

Hi,

I have exact the same problem as degenar, i checked my interfaces, added the 127.0.0.1 entry to my iptables, but nothing fixed the problem Unsure

Im using pilight 6 stable
removed the v5 with apt-get purge -> reboot -> installed v6 via apt
i edited the config.json and added the "port": 5000 attribute

are there any bugfixes for this problem?
 
Reply
@takaze Have you tried the nightly version?
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  [Solved] pilight service crashing on first webserver access after reboot VrahoK 20 2,287 12-21-2019, 09:46 AM
Last Post: curlymo
  Connection lost, trying to reconnect — loop apartmedia 5 1,319 03-16-2019, 09:41 AM
Last Post: curlymo
  [solved] Webgui 404-Error PT-Biker 2 1,455 11-11-2017, 09:49 AM
Last Post: PT-Biker
  [solved] Hardware not compatible ccc.ggg73 1 1,847 06-10-2017, 09:10 AM
Last Post: curlymo
  Standalone but SSDP brenner23 6 3,186 04-16-2017, 11:34 PM
Last Post: brenner23
  [Solved] pilight ssdp celle 6 9,143 02-23-2017, 03:22 PM
Last Post: gneandr
  Raspbian jessie - pilight 7 - no pilight ssdp connections found shirocko 20 19,193 01-29-2017, 10:23 PM
Last Post: gneandr
  [solved] No signal with raw data andies 6 3,824 12-25-2016, 09:11 AM
Last Post: andies
  pilight without internet connection terrar 5 4,037 08-12-2016, 09:47 PM
Last Post: terrar
  ssdp discovery clach04 5 5,533 05-23-2016, 04:23 PM
Last Post: pilino1234

Forum Jump:


Browsing: 1 Guest(s)