Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Socket Error
#1
I am getting socket.error: No socket could be created after installing sip.  The error seems almost identical to "Socket Issue After forcing Exit Issue 112" posted by Tails86 on June 30.  I've tried removing the SIP directories, rebooting, recloning, but same results.  Any help/suggestions greatly appreciated - Thank you, 

pi@raspberrypi ~/SIP $ sudo python sip.py
plugins loaded:
  mobile_app
  plugin_manager
  signaling_examples
  system_update
zones changed
[0, 0, 0, 0, 0, 0, 0, 0]
Starting timing loop

http://0.0.0.0:80/
Traceback (most recent call last):
  File "sip.py", line 229, in <module>
    app.run()
  File "sip.py", line 163, in run
    return web.httpserver.runsimple(func, ('0.0.0.0', port))
  File "/home/pi/SIP/web/httpserver.py", line 157, in runsimple
    server.start()
  File "/home/pi/SIP/web/wsgiserver/__init__.py", line 1753, in start
    raise socket.error(msg)
socket.error: No socket could be created
Reply
#2
That error usually indicates that either the program is already running in the background or some other server is using the same port which is now 80 by default.

If the program is already running in the background you should be able to clear it with the command

Code:
sudo service sip stop

or reboot the Pi.

If another server is using port 80, which is a default web site port, you can try editing the file SIP/data/sd.json .
You will need to find the part

Code:
 "htp": 80,

and change 80 to something like 8080. Then you will need to add
":8080" (without the quotes) to the url of your SIP installation.
Reply
#3
(2015 Aug 21, 04:18 AM)dan Wrote: That error usually indicates that either the program is already running in the background or some other server is using the same port which is now 80 by default.

If the program is already running in the background you should be able to clear it with the command

Code:
sudo service sip stop

or reboot the Pi.

If another server is using port 80, which is a default web site port, you can try editing the file SIP/data/sd.json .
You will need to find the part

Code:
 "htp": 80,

and change 80 to something like 8080. Then you will need to add
":8080" (without the quotes) to the url of your SIP installation.
Changing to 8080 fixed the problem.  I am playing with Apache which is probably causing the conflict.  Thank you for your fast response.
Reply
#4
Glad you were able to get things working.

I should also mention that if SIP is running you can set the port number on the Options page under system.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)