2024-12-02 -- Recursive log errors ----- ERROR [DiscoverySSD

Getting these all day long, every day.

Tried rebooting systedm, no change. Any Ideas?

-------------------------------------------------------------------------------------------------------------------------------


2024-12-02T11:34:06,132 ERROR [DiscoverySSDPMessageListener] Cannot open multicast socket,will try again
java.net.BindException: Address already in use: Cannot bind
at java.net.TwoStacksPlainDatagramSocketImpl.bind0(Native Method) ~[?:1.8.0_352]
at java.net.TwoStacksPlainDatagramSocketImpl.bind0(TwoStacksPlainDatagramSocketImpl.java:107) ~[?:1.8.0_352]
at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93) ~[?:1.8.0_352]
at java.net.TwoStacksPlainDatagramSocketImpl.bind(TwoStacksPlainDatagramSocketImpl.java:97) ~[?:1.8.0_352]
at java.net.DatagramSocket.bind(DatagramSocket.java:392) ~[?:1.8.0_352]
at java.net.MulticastSocket.<init>(MulticastSocket.java:172) ~[?:1.8.0_352]
at java.net.MulticastSocket.<init>(MulticastSocket.java:136) ~[?:1.8.0_352]
at org.serviio.util.MultiCastUtils.startMultiCastSocketForListening(MultiCastUtils.java:47) ~[serviio.jar:?]
at org.serviio.upnp.discovery.DiscoverySSDPMessageListener.run(DiscoverySSDPMessageListener.java:82) ~[serviio.jar:?]
at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_352]
2024-12-02T11:34:07,186 ERROR [DiscoverySSDPMessageListener] Cannot open multicast socket,will try again
java.net.BindException: Address already in use: Cannot bind
at java.net.TwoStacksPlainDatagramSocketImpl.bind0(Native Method) ~[?:1.8.0_352]
at java.net.TwoStacksPlainDatagramSocketImpl.bind0(TwoStacksPlainDatagramSocketImpl.java:107) ~[?:1.8.0_352]
at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93) ~[?:1.8.0_352]
at java.net.TwoStacksPlainDatagramSocketImpl.bind(TwoStacksPlainDatagramSocketImpl.java:97) ~[?:1.8.0_352]
at java.net.DatagramSocket.bind(DatagramSocket.java:392) ~[?:1.8.0_352]
at java.net.MulticastSocket.<init>(MulticastSocket.java:172) ~[?:1.8.0_352]
at java.net.MulticastSocket.<init>(MulticastSocket.java:136) ~[?:1.8.0_352]
at org.serviio.util.MultiCastUtils.startMultiCastSocketForListening(MultiCastUtils.java:47) ~[serviio.jar:?]
at org.serviio.upnp.discovery.DiscoverySSDPMessageListener.run(DiscoverySSDPMessageListener.java:82) ~[serviio.jar:?]
at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_352]
2024-12-02T11:34:08,236 ERROR [DiscoverySSDPMessageListener] Cannot open multicast socket,will try again
java.net.BindException: Address already in use: Cannot bind
at java.net.TwoStacksPlainDatagramSocketImpl.bind0(Native Method) ~[?:1.8.0_352]
at java.net.TwoStacksPlainDatagramSocketImpl.bind0(TwoStacksPlainDatagramSocketImpl.java:107) ~[?:1.8.0_352]
at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93) ~[?:1.8.0_352]
at java.net.TwoStacksPlainDatagramSocketImpl.bind(TwoStacksPlainDatagramSocketImpl.java:97) ~[?:1.8.0_352]
at java.net.DatagramSocket.bind(DatagramSocket.java:392) ~[?:1.8.0_352]
at java.net.MulticastSocket.<init>(MulticastSocket.java:172) ~[?:1.8.0_352]
at java.net.MulticastSocket.<init>(MulticastSocket.java:136) ~[?:1.8.0_352]
at org.serviio.util.MultiCastUtils.startMultiCastSocketForListening(MultiCastUtils.java:47) ~[serviio.jar:?]
at org.serviio.upnp.discovery.DiscoverySSDPMessageListener.run(DiscoverySSDPMessageListener.java:82) ~[serviio.jar:?]
at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_352]

[atc98092]

Judging by this error line: java.net.BindException: Address already in use: Cannot bind you are having a networking issue. Is Serviio installed on a computer with more than one network adapter (either multiple Ethernet connections or WiFi and/or Bluetooth adapters)?

Since it's a Java issue, there might be something already installed on your computer that uses Java and is using the same command to bind to the IP address. Or perhaps some other DLNA software that is interfering with the port Serviio is trying to use. I can say that Plex and Emby run just fine on a computer that also runs Serviio. But other than those I have not tested any other product.

I ran a netstat -a -o and discovered UDP port 1900 is associated with two instances of node.exe
Did a task manmager kill of the two instances.
The loggings stopped.
Rebooted my Windows 21016 server.
Everything cane up fine.
Still no more loggings.
However I can no loinmger run the StorageView web to check the ststus of my Adaptec RAID adapters.
I assume it had one of the node.exe instances.
Who knows who had trhe other one.

Which brings up the question... why cpould these inmstances run and Serviio could not.
Perhaps it should use note.exe too.

[atc98092]

UDP port 1900 is used by DLNA/uPnP, and I had thought multiple applications could use it. But perhaps not. It would seem odd that Adaptec would use that port for monitoring the RAID array, but it's been many, many years since I've messed with RAID adapters.

I think I have a proper fix for this.

I discovered two services that both use port 1900 at the same time and both seem to work just fine.
These services use node.exe to access the port.
Serviio wants exclusive control and cannot get it and recursively fails in it's reattempt.

This is how I fixed it and it appears to work, with my RAID administration, the other service (another RAID monitor that uses port 1900 that I hardly ever use) and Serviio.

I changed the two RAID administrastion services to saartup automatic/delayed. This allows Serviio to get port 1600 for exclusive control.
After two minutes (according to Microsoft documentation), the other two services start up, both successfully getting the port.

I tested Serviio and it works fine. I exasmined the logs and the error message no longer appear.
I tested my RAID administration and it too now works fine.

I am sure this will work for other people that run into this issue. You have to knbow what procresses are requesting port 1600 and condition them.
netstat -a -o