Page 1 of 1

WDTV Live Hub and Serviio

PostPosted: Mon Feb 03, 2014 7:29 pm
by bubbabyte
Hi guys,

I've read through everything i can possibly read through on this forum but I can't figure this out. I have a D-Link router (826L) and Upnp is enabled and ipv4 multicast is enabled as well which was done about a month ago and seemed to resolve the issue. Then just a few days ago i noticed i kept getting dropped (content source has been removed) message, and i check my pc and the server is still running, even stopping it and restarting the service wouldn't bring it back someitmes. This is what is shown in my log and i have no idea what it means or what i should do to correct it.

2014-02-02 22:20:54,437 INFO [WebServer] WebServer shutting down
2014-02-02 22:20:54,438 INFO [DiscoveryAdvertisementNotifier] Leaving DiscoveryAdvertisementNotifier
2014-02-02 22:20:54,438 INFO [EventSubscriptionExpirationChecker] Leaving EventSubscriptionExpirationChecker, removing all event subscriptions
2014-02-02 22:20:54,439 INFO [DiscoverySSDPMessageListener] Leaving DiscoverySSDPMessageListener
2014-02-02 22:20:54,439 INFO [EventDispatcher] Leaving EventDispatcher
2014-02-02 22:20:54,517 INFO [WebServer] WebServer starting on port 8895
2014-02-02 22:20:54,590 INFO [Device] Updated bound IP address of Device with UUID: 52f87b40-3dc2-3196-b089-5640e5a2fa57, bound address: 192.168.0.104
2014-02-02 22:20:54,591 INFO [EventDispatcher] Starting EventDispatcher
2014-02-02 22:20:54,591 INFO [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2014-02-02 22:20:54,591 INFO [EventSubscriptionExpirationChecker] Starting EventSubscriptionExpirationChecker
2014-02-02 22:20:54,678 INFO [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth3 (Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Controller) and address 192.168.0.104, timeout = 0
2014-02-02 22:20:54,722 INFO [RendererSearchSender] Searching for Renderer devices
2014-02-02 22:22:23,879 INFO [RendererManager] Stored a new renderer: uuid='1476dc56-bae6-4c3b-a3b9-f0fbffa7fd6c', name = 'Unrecognized device', ipAddress='192.168.0.104', profile = '1'
2014-02-02 22:23:18,084 INFO [MediaServer] Serviio server instance is already running


I've made my ip static on the WDTV hub, and that didn't help. I'm not sure what else to do.

Re: WDTV Live Hub and Serviio

PostPosted: Mon Feb 03, 2014 9:08 pm
by bubbabyte
Just fyi, its not linked to the whole 30 minute issue that others had, as it seems completely random. Sometimes hours, sometimes 10 minutes etc.

Re: WDTV Live Hub and Serviio

PostPosted: Mon Feb 03, 2014 9:20 pm
by bubbabyte
Happened again now after about 2 hours of watching it.

2014-02-03 14:26:55,860 INFO [WebServer] WebServer shutting down
2014-02-03 14:26:55,882 INFO [DiscoverySSDPMessageListener] Leaving DiscoverySSDPMessageListener
2014-02-03 14:26:55,882 INFO [EventSubscriptionExpirationChecker] Leaving EventSubscriptionExpirationChecker, removing all event subscriptions
2014-02-03 14:26:55,882 INFO [EventDispatcher] Leaving EventDispatcher
2014-02-03 14:26:55,936 INFO [WebServer] WebServer starting on port 8895
2014-02-03 14:26:56,294 INFO [Device] Updated bound IP address of Device with UUID: 52f87b40-3dc2-3196-b089-5640e5a2fa57, bound address: 192.168.0.104
2014-02-03 14:26:56,294 INFO [EventSubscriptionExpirationChecker] Starting EventSubscriptionExpirationChecker
2014-02-03 14:26:56,294 INFO [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2014-02-03 14:26:56,294 INFO [EventDispatcher] Starting EventDispatcher
2014-02-03 14:26:56,347 INFO [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth3 (Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Controller) and address 192.168.0.104, timeout = 0
2014-02-03 14:26:56,348 INFO [RendererSearchSender] Searching for Renderer devices
2014-02-03 14:26:56,510 INFO [RendererExpirationChecker] Leaving RendererExpirationChecker

Re: WDTV Live Hub and Serviio

PostPosted: Mon Feb 03, 2014 10:43 pm
by DenyAll
Please post a detailed log (click link) showing some of the messages leading up to the server restarting. It may shed some light.