Got this weird error since upgrading to 0.9.8

Did I forget to do prework prior to upgrading?...

------

Starting plugin "Sonos 0.9.8" (pid 95248)
Started plugin "Sonos 0.9.8"
Sonos Your plugin version, v0.9.8, is current.
Sonos Loaded Sonos Favorites... [18]
Sonos Loaded Playlists... [9]
Sonos Loaded RadioTime Favorite Stations... [0]
Sonos Serving HTTP Streamer on 192.168.109.200 [0.0.0.0], port 8888
Sonos Loaded Pandora Stations... [68]
Sonos [Sun Jul 3 10:14:01 2016] Processed plugin preferences.
Sonos Error Error in plugin execution startup:

Traceback (most recent call last):
File "plugin.py", line 36, in startup
File "/Library/Application Support/Perceptive Automation/Indigo 6/Plugins/Sonos.indigoPlugin/Contents/Server Plugin/Sonos.py", line 260, in startup
File "./lib/twisted/internet/posixbase.py", line 387, in listenMulticast
File "./lib/twisted/internet/udp.py", line 175, in startListening
File "./lib/twisted/internet/udp.py", line 195, in _bindSocket
CannotListenError: Couldn't listen on any:1900: [Errno 48] Address already in use.

Is it possible you might have some other plugin or app that has locked port 1900? The Sonos plugin will try to open the socket in a shared mode.

Did I forget to do prework prior to upgrading?...

------

Starting plugin "Sonos 0.9.8" (pid 95248)
Started plugin "Sonos 0.9.8"
Sonos Your plugin version, v0.9.8, is current.
Sonos Loaded Sonos Favorites... [18]
Sonos Loaded Playlists... [9]
Sonos Loaded RadioTime Favorite Stations... [0]
Sonos Serving HTTP Streamer on 192.168.109.200 [0.0.0.0], port 8888
Sonos Loaded Pandora Stations... [68]
Sonos [Sun Jul 3 10:14:01 2016] Processed plugin preferences.
Sonos Error Error in plugin execution startup:

Traceback (most recent call last):
File "plugin.py", line 36, in startup
File "/Library/Application Support/Perceptive Automation/Indigo 6/Plugins/Sonos.indigoPlugin/Contents/Server Plugin/Sonos.py", line 260, in startup
File "./lib/twisted/internet/posixbase.py", line 387, in listenMulticast
File "./lib/twisted/internet/udp.py", line 175, in startListening
File "./lib/twisted/internet/udp.py", line 195, in _bindSocket
CannotListenError: Couldn't listen on any:1900: [Errno 48] Address already in use.

I am now getting this too when I restart the plugin.

Code: Select all

Started plugin "Sonos 0.9.10"
  Sonos                           Your plugin version, v0.9.10, is current.
  Sonos                           Loaded Sonos Favorites... [14]
  Sonos                           Loaded Playlists... [5]
  Sonos                           Loaded RadioTime Favorite Stations... [2]
  Sonos                           Loaded Sound Files... [1]
  Sonos                           Serving HTTP Streamer on 192.168.0.X [0.0.0.0], port 8888
  Sonos                           Loaded Pandora Stations for ... [26]
  Sonos                           [Mon Oct 10 14:49:31 2016] Processed plugin preferences.
  Sonos Error                     Error in plugin execution startup:

Traceback (most recent call last):
  File "plugin.py", line 36, in startup
  File "/Library/Application Support/Perceptive Automation/Indigo 6/Plugins/Sonos.indigoPlugin/Contents/Server Plugin/Sonos.py", line 265, in startup
  File "./lib/twisted/internet/posixbase.py", line 387, in listenMulticast
  File "./lib/twisted/internet/udp.py", line 175, in startListening
  File "./lib/twisted/internet/udp.py", line 195, in _bindSocket
CannotListenError: Couldn't listen on any:1900: [Errno 48] Address already in use.


And from Terminal... Doesn't look like anything on port 1900.

Code: Select all

sudo lsof -i -P | grep -i "listen"
launchd       1           root   19u  IPv4 0x3be3e58f21b0ba77      0t0    TCP *:445 (LISTEN)
launchd       1           root   20u  IPv6 0x3be3e58f1f01c307      0t0    TCP *:445 (LISTEN)
launchd       1           root   24u  IPv4 0x3be3e58f21b1836f      0t0    TCP *:5900 (LISTEN)
launchd       1           root   26u  IPv4 0x3be3e58f21b1836f      0t0    TCP *:5900 (LISTEN)
launchd       1           root   29u  IPv6 0x3be3e58f1c1f5307      0t0    TCP *:5900 (LISTEN)
launchd       1           root   31u  IPv4 0x3be3e58f21b0ba77      0t0    TCP *:445 (LISTEN)
launchd       1           root   37u  IPv6 0x3be3e58f167cd847      0t0    TCP *:22 (LISTEN)
launchd       1           root   38u  IPv4 0x3be3e58f167d036f      0t0    TCP *:22 (LISTEN)
launchd       1           root   40u  IPv6 0x3be3e58f167cd847      0t0    TCP *:22 (LISTEN)
launchd       1           root   42u  IPv4 0x3be3e58f167d036f      0t0    TCP *:22 (LISTEN)
launchd       1           root   45u  IPv6 0x3be3e58f1f01c307      0t0    TCP *:445 (LISTEN)
launchd       1           root   49u  IPv6 0x3be3e58f1c1f5307      0t0    TCP *:5900 (LISTEN)
hdhomerun   110     _HDHomeRun   12u  IPv4 0x3be3e58f167d155f      0t0    TCP *:49152 (LISTEN)
node        346           user   11u  IPv6 0x3be3e58f167cd307      0t0    TCP *:51826 (LISTEN)
node        346           user   14u  IPv6 0x3be3e58f1a167307      0t0    TCP *:62161 (LISTEN)
node        346           user   20u  IPv6 0x3be3e58f21a56307      0t0    TCP *:62537 (LISTEN)
node        346           user   24u  IPv6 0x3be3e58f21a55dc7      0t0    TCP *:62002 (LISTEN)
IndigoSer   385           user    7u  IPv4 0x3be3e58f1c450c67      0t0    TCP *:1176 (LISTEN)
IndigoPlu   422           user    8u  IPv4 0x3be3e58f1dabe55f      0t0    TCP mac.user.net:8177 (LISTEN)
Python      444           user    3u  IPv4 0x3be3e58f1dcf2c67      0t0    TCP *:8176 (LISTEN)
awacsd    43030           root    7u  IPv6 0x3be3e58f1c1f4dc7      0t0    TCP [ip v 6]:4488 (LISTEN)
kdc       43063           root    5u  IPv6 0x3be3e58f1a166dc7      0t0    TCP *:88 (LISTEN)
kdc       43063           root    7u  IPv4 0x3be3e58f1e38b74f      0t0    TCP *:88 (LISTEN)
Sonos     53782           user   18u  IPv4 0x3be3e58f21bb8e57      0t0    TCP *:3400 (LISTEN)
IndigoPlu 56338           user   10u  IPv4 0x3be3e58f21b9674f      0t0    TCP *:1400 (LISTEN)
IndigoPlu 56338           user   12u  IPv4 0x3be3e58f2905374f      0t0    TCP *:8888 (LISTEN)


You have some other application that is using port 1900 in a non-sharing mode.

Yep. it was HDhomerun. Not sure how it was able to grab that port. It's been fine for a month now.

I think I have this resolved now. Thanks

Great... sorry for being absent... in London on business if any locals want to hunt me down for the shortage up updates.