Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Autostart after boot failing
#3
(2019 Apr 13, 12:38 AM)dan Wrote: The error "socket.error: No socket could be created" indicates that there is already something using the default port (port 80).

Do you have another server program like apache running?

Once you get SIP to start you can change the port it uses from the Options page. Change "HTTP port:" from 80 to something like 8080. This may help.

I have seen this happen after starting SIP manually and then trying to start it using systemctl.

Thanks dan.
I stopped autostart and rebooted.
sudo netstat -pln, nothing on port 80
started sip
port 80 now in use.
changed port to 8080 and tested ok.
set up auto start
rebooted, error still there even though now on 8080.
start sip and web page responds on 8080

I am inclined to think it is a timing issue but I don't know how to delay the service start.
Reply


Messages In This Thread
Autostart after boot failing - by Gazmac52 - 2019 Apr 12, 11:20 PM
RE: Autostart after boot failing - by dan - 2019 Apr 13, 12:38 AM
RE: Autostart after boot failing - by Gazmac52 - 2019 Apr 13, 12:54 AM
RE: Autostart after boot failing - by dan - 2019 Apr 13, 01:04 AM
RE: Autostart after boot failing - by dan - 2019 Apr 13, 01:09 AM
RE: Autostart after boot failing - by Gazmac52 - 2019 Apr 13, 01:10 AM
RE: Autostart after boot failing - by dan - 2019 Apr 13, 01:45 AM

Forum Jump:


Users browsing this thread: 2 Guest(s)