Page 1 of 1
New Modem - UMS Refuses to Work [Resolved]
Posted: Fri May 13, 2022 12:39 pm
by GaryMac
I recently switched Internet Companies, which means, the old modem was sent back and new one from the new company has taken its place.
With the old Modem had no issues with UMS. In fact, I used UMS daily with it.
Since changing over Internet Providers and receiving the new Modem (Tuesday), UMS no longer works. I have tried deleting it entirely and doing a clean install and ensuring all Devices are "visible" on my Network. Yes, I checked Windows Firewall, all the appropriate Permissions for UMS are selected. Quite stumped on this one.
The only change was the Modem/Provider. Obvious this is the reason but not sure why it will not work.
Attached a log file though I am not sure how much help it will be.
Regards,
Gary
Re: New Modem - UMS Refuses to Work
Posted: Sat May 14, 2022 12:51 am
by mik_s
I'm not sure what is going wrong here. UMS starts normally and is doing a library scan while waiting for renderers to announce themselves, then something makes it restart a process and reload all the configuration files again. Then there are many errors about a closed socket.
Code: Select all
DEBUG 2022-05-12 20:33:59.650 [background-task-0] net.pms.util.TaskRunner singleton task restart started
DEBUG 2022-05-12 20:33:59.650 [background-task-0-restart(0)] net.pms.util.TaskRunner task started
DEBUG 2022-05-12 20:33:59.650 [background-task-0-restart(0)] net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer Sending BYEBYE...
DEBUG 2022-05-12 20:33:59.650 [UPNP-AliveMessageSender] net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer Sending ALIVE...
INFO 2022-05-12 20:33:59.915 [background-task-0-restart(0)] net.pms.network.mediaserver.nettyserver.NettyServer Stopping server on host 192.168.1.132 and port 5001...
ERROR 2022-05-12 20:33:59.915 [UPNPHelper] net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer UPnP network exception: socket closed
TRACE 2022-05-12 20:33:59.923 [UPNP-AliveMessageSender] net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer Error when sending the ALIVE message: {}
java.net.SocketException: Socket is closed
at java.net.DatagramSocket.send(DatagramSocket.java:658)
at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.sendMessage(SocketSSDPServer.java:324)
at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.sendMessage(SocketSSDPServer.java:296)
at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.sendAlive(SocketSSDPServer.java:261)
at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.lambda$listen$0(SocketSSDPServer.java:477)
at java.lang.Thread.run(Thread.java:750)
TRACE 2022-05-12 20:33:59.923 [UPNPHelper] net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer
java.net.SocketException: socket closed
at java.net.TwoStacksPlainDatagramSocketImpl.receive0(Native Method)
at java.net.TwoStacksPlainDatagramSocketImpl.receive(TwoStacksPlainDatagramSocketImpl.java:114)
at java.net.DatagramSocket.receive(DatagramSocket.java:812)
at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.lambda$listen$1(SocketSSDPServer.java:496)
at java.lang.Thread.run(Thread.java:750)
INFO 2022-05-12 20:33:59.924 [background-task-0-restart(0)] net.pms.network.mediaserver.nettyserver.NettyServer Confirm allChannels is empty: DefaultChannelGroup(name: HTTPServer, size: 0)
TRACE 2022-05-12 20:33:59.924 [UPNPHelper] net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer Final UPnP network exception: Socket is closed
TRACE 2022-05-12 20:33:59.924 [UPNPHelper] net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer
java.net.SocketException: Socket is closed
at java.net.MulticastSocket.leaveGroup(MulticastSocket.java:435)
at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.lambda$listen$1(SocketSSDPServer.java:565)
at java.lang.Thread.run(Thread.java:750)
ERROR 2022-05-12 20:33:59.924 [UPNPHelper] net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer UPnP network exception: Socket closed
TRACE 2022-05-12 20:33:59.924 [UPNPHelper] net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer
java.net.SocketException: Socket closed
at java.net.TwoStacksPlainDatagramSocketImpl.receive0(Native Method)
at java.net.TwoStacksPlainDatagramSocketImpl.receive(TwoStacksPlainDatagramSocketImpl.java:114)
at java.net.DatagramSocket.receive(DatagramSocket.java:812)
at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.lambda$listen$1(SocketSSDPServer.java:496)
at java.lang.Thread.run(Thread.java:750)
INFO 2022-05-12 20:33:59.924 [UPNP-AliveMessageSender] net.pms.util.SystemErrWrapper Exception in thread "UPNP-AliveMessageSender" java.lang.IllegalArgumentException: unsupported address type
INFO 2022-05-12 20:33:59.925 [UPNP-AliveMessageSender] net.pms.util.SystemErrWrapper at java.net.DatagramPacket.setSocketAddress(DatagramPacket.java:313)
INFO 2022-05-12 20:33:59.925 [UPNP-AliveMessageSender] net.pms.util.SystemErrWrapper at java.net.DatagramPacket.<init>(DatagramPacket.java:144)
INFO 2022-05-12 20:33:59.925 [UPNP-AliveMessageSender] net.pms.util.SystemErrWrapper at java.net.DatagramPacket.<init>(DatagramPacket.java:178)
INFO 2022-05-12 20:33:59.925 [UPNP-AliveMessageSender] net.pms.util.SystemErrWrapper at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.sendMessage(SocketSSDPServer.java:315)
INFO 2022-05-12 20:33:59.925 [UPNP-AliveMessageSender] net.pms.util.SystemErrWrapper at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.sendMessage(SocketSSDPServer.java:296)
INFO 2022-05-12 20:33:59.925 [UPNP-AliveMessageSender] net.pms.util.SystemErrWrapper at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.sendAlive(SocketSSDPServer.java:261)
INFO 2022-05-12 20:33:59.926 [UPNP-AliveMessageSender] net.pms.util.SystemErrWrapper at net.pms.network.mediaserver.socketssdpserver.SocketSSDPServer.lambda$listen$0(SocketSSDPServer.java:477)
INFO 2022-05-12 20:33:59.926 [UPNP-AliveMessageSender] net.pms.util.SystemErrWrapper at java.lang.Thread.run(Thread.java:750)
INFO 2022-05-12 20:33:59.931 [background-task-0-restart(0)] net.pms.configuration.RendererConfiguration Loading renderer configurations from C:\Program Files (x86)\Universal Media Server\renderers
There is a possibility of a bug here somewhere. I know little about network stuff but I think something from your new router is causing this.
Could you try connecting to your router with a wire instead of wireless? I remember hearing that some routers separate some of the protocols used by UMS between wired and wireless. There may be options to bridge this or to share them in your router options but I don't know what it could be.
Does it only happen in version 10.21.0.1? have you tried using previous versions? Could you try the 11.0.0-a2 version too as there has been changes to the modules used for network communication.
Re: New Modem - UMS Refuses to Work
Posted: Sat May 14, 2022 10:19 pm
by GaryMac
Yes, this was happening in my old version and then I updated to the current 10.21.01 build. I will try 11 and see what happens.
This new Modem is also affecting other items in my house as I am finding out. Grr, the price we pay for upgrading. Either way, I will inform everyone of my progress.
Thanks for the reply.
Gary
Re: New Modem - UMS Refuses to Work [Resolved]
Posted: Mon May 16, 2022 8:28 am
by GaryMac
Resolved. Was doing a bit of dusting (ugh, how I hate this) around my modem/router area and noticed that ALL the cables are plugged into the Modem. Then a "lightbulb" moment, I moved the TV Ethernet back into the Router Port and UMS started working as intended. I switched my PS4 cable back to the Router with the same effect. Duh.
Seems the Tech that installed the modem put everything into the Modem not back into the Router where it was originally placed.
Something so simple has been bugging me and it was a simple remedy. Thanks mik_s for chiming in.
Gary
Re: New Modem - UMS Refuses to Work
Posted: Mon May 16, 2022 9:18 am
by mik_s
Glad you got it working.
From what you say it sounds like they have a separate modem and a network switch instead of the usual all in one router that most ISPs use, but I think this is becoming the norm for fibre to the home if that is what you have. I am surprised the tech made that mistake though.
That error message makes more sense too if it was connected that way as the modem did not know what to do with the connection so was closing it.
Re: New Modem - UMS Refuses to Work [Resolved]
Posted: Mon May 16, 2022 9:55 am
by GaryMac
Exactly. I feel so silly.
Either way, all fixed up and back to normal. I will admit, UMS is used daily here.
Gary