[DiscoverySSDPMessageListener] Cannot open multicast socket

System: Slackware Linux (-current) x86, kernel 4.9.x, Java 1.8.0_121

I was successfully running serviio 1.5 for a long time and never bothered to upgrade until just recently. I am not sure when it began, but my logs are completely full of this message repeated frequently:

  Code:

2017-04-04 20:08:17,841 ERROR [DiscoverySSDPMessageListener] Cannot open multicast socket,will try again
java.net.SocketException: No buffer space available
        at java.net.PlainDatagramSocketImpl.join(Native Method)
        at java.net.AbstractPlainDatagramSocketImpl.joinGroup(AbstractPlainDatagramSocketImpl.java:202)
        at java.net.MulticastSocket.joinGroup(MulticastSocket.java:406)
        at org.serviio.util.MultiCastUtils.startMultiCastSocketForListening(MultiCastUtils.java:52)
        at org.serviio.upnp.discovery.DiscoverySSDPMessageListener.run(DiscoverySSDPMessageListener.java:89)
        at java.lang.Thread.run(Thread.java:745)
2017-04-04 20:08:18,851 ERROR [DiscoverySSDPMessageListener] Cannot open multicast socket,will try again
java.net.SocketException: No buffer space available
        at java.net.PlainDatagramSocketImpl.join(Native Method)
        at java.net.AbstractPlainDatagramSocketImpl.joinGroup(AbstractPlainDatagramSocketImpl.java:202)
        at java.net.MulticastSocket.joinGroup(MulticastSocket.java:406)
        at org.serviio.util.MultiCastUtils.startMultiCastSocketForListening(MultiCastUtils.java:52)
        at org.serviio.upnp.discovery.DiscoverySSDPMessageListener.run(DiscoverySSDPMessageListener.java:89)
        at java.lang.Thread.run(Thread.java:745)


I have tried googling and searching the forums, but I haven't found any reports of similar issues. Figuring my serviio install was old, I just updated from version 1.5 to version 1.8 and still the problem persists. Does anyone have any tips on how to debug this issue?

Well, I haven't changed my kernel configuration in a long time, but something in the kernel or JRE must have changed over the years. To correct this issue, I had to enable CONFIG_IP_MULTICAST=y in my kernel configuration.