socket.error...but changing port didn't help, nor did reboot

[noequus]

Hi Dan:



Now upgrading from buster to bullseye and having exactly the same problem as I did two years ago (in this thread: OSError: No socket could be created). It appears regardless of what port I use. Unfortunately, no idea how it was fixed!




In this case I just now enabled SIP as a service hoping that would help but it didn't solve the problem (it is active and running). Prior to that I could successfully run SIP from the command line but not as a @reboot line in crontab (that's how it was in buster). Here's the crontab line I used with the result below. 




@reboot sudo python3 /home/pi/SIP/sip.py  >> /home/pi/SIP-OUT.txt 2>&1




Not sure how to run SIP from the command line when running as a service...can't do that now; suggestions welcome.



Messge from Signaling plugin!: Just an example!

plugins loaded:

  mobile_app

  plugin_manager

  signaling_examples

  system_update

Starting timing loop



A new day has started.

zones changed

[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

http://192.168.1.10:8099/

Traceback (most recent call last):

  File "/home/pi/SIP/sip.py", line 342, in <module>

    app.run()

  File "/home/pi/SIP/sip.py", line 260, in run

    return web.httpserver.runsimple(func, (ip, port))

  File "/home/pi/SIP/web/httpserver.py", line 178, in runsimple

    server.start()

  File "/home/pi/SIP/cheroot/server.py", line 1820, in start

    self.prepare()

  File "/home/pi/SIP/cheroot/server.py", line 1779, in prepare

    raise socket.error(msg)

OSError: No socket could be created -- (('192.168.1.10', 8099): [Errno 99] Cannot assign requested address)