Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
sip3.service fail
#1
Hello again,
Since I had some problems after the last update, I want to start over with a clean install.
I already have it installed and working, except for the automatic start of sip.py.
following the instructions I have done these steps:

Code:
sudo cp SIP/sip3.service /etc/systemd/system/
sudo systemctl enable sip3.service
sudo reboot
after restarting, the web doesn't work.
Quote:pi@Riego:~ $ systemctl status sip3
● sip3.service - SIP for Python3
    Loaded: loaded (/etc/systemd/system/sip3.service; enabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Sun 2021-12-05 11:12:23 CET; 3min 42s ago
    Process: 336 ExecStart=/usr/bin/python3 -u /home/pi/SIP/sip.py (code=exited, status=1/FAILURE)
  Main PID: 336 (code=exited, status=1/FAILURE)
        CPU: 4.944s

dic 05 11:12:23 Riego sip[336]:  File "/home/pi/SIP/web/httpserver.py", line 178, in runsimple
dic 05 11:12:23 Riego sip[336]:    server.start()
dic 05 11:12:23 Riego sip[336]:  File "/home/pi/SIP/cheroot/server.py", line 1820, in start
dic 05 11:12:23 Riego sip[336]:    self.prepare()
dic 05 11:12:23 Riego sip[336]:  File "/home/pi/SIP/cheroot/server.py", line 1779, in prepare
dic 05 11:12:23 Riego sip[336]:    raise socket.error(msg)
dic 05 11:12:23 Riego sip[336]: OSError: No socket could be created -- (('192.168.1.60', 80): [Errno 99] Cannot assign requested address)
dic 05 11:12:23 Riego systemd[1]: sip3.service: Main process exited, code=exited, status=1/FAILURE
dic 05 11:12:23 Riego systemd[1]: sip3.service: Failed with result 'exit-code'.
dic 05 11:12:23 Riego systemd[1]: sip3.service: Consumed 4.944s CPU time.

if I execute  'sudo systemctl restart sip3.service' then works ok.
Quote:pi@Riego:~ $ sudo systemctl restart sip3.service
pi@Riego:~ $ systemctl status sip3
● sip3.service - SIP for Python3
    Loaded: loaded (/etc/systemd/system/sip3.service; enabled; vendor preset: enabled)
    Active: active (running) since Sun 2021-12-05 11:38:24 CET; 1s ago
  Main PID: 715 (python3)
      Tasks: 1 (limit: 415)
        CPU: 1.736s
    CGroup: /system.slice/sip3.service
            └─715 /usr/bin/python3 -u /home/pi/SIP/sip.py

dic 05 11:38:24 Riego systemd[1]: Started SIP for Python3.

Could it be that the network is not ready yet?
Thank you
Reply
#2
The error "OSError: No socket could be created" usually indicates that port 80 is already being used by another process.
Not sure what is causing this.

The sip3.service file waits for the network to start so that should not be a problem.

Dan
<p><br></p>
Reply
#3
Hello I have exactly the same issue, any solution on this?
Reply
#4
(2022 May 24, 02:35 PM)md666 Wrote: Hello I have exactly the same issue, any solution on this?

If the problem is caused by another program using port 80, you can try editing SIP's settings file.
Log into the SIP directory and use e.g.
nano data/sd.json

scroll down a few lines to one that says 
"htp": 80,
and change it to e.g. "htp": 8080,

when you try to access SIP's web UI you will need to add :8080 to the url.

Dan
<p><br></p>
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)