Bound IP Address issue

I upgraded to version 1.2.1 after having been on older version for a while (I don't remember which one though). I have been having problems with Serviio not being recognizable to the network as running (even though console says it is) after the computer comes out of sleep. I had seen other postings about this, but simply stopping/restarting the server doesn't fix it.

To fix it, I have to change the Bound IP address back to automatically detected then everything sees it again. This doesn't make a lot of sense to me as my router has the Serviio computer set to always have the same IP address anyway, but I am assuming something in the automatic setting refreshes the connection in some way.

Is there any way to set the Bound IP to REMAIN on automatically detected on wake up? I am running Vista 64 if it makes a difference.

[zip]

So the Stop server and Start server don't help? It's basically what happens when you select the autodetect from the dropdown.

[Illico]

"parenthesis"

So the Stop server and Start server don't help? It's basically what happens when you select the autodetect from the dropdown.

I never use this feature (stop/start server), Do you think it's really necessary (confusing)?
But stop/start service is widely used for me (profile modification...)

[slyguy42o]

so in the serviio console, do you have the network adapter you want to use selected? you can either use the server control button in the console or restart services after you set the proper network option.

Sorry for delay in responding.

No, the stop/start server do not seem to fix the problem although I guess I could do more tests on it. Seems like the only thing I could get to work was my changing the bound IP. May just be easier to downgrade, but I thought I would check. Thanks for the assist.

[slyguy42o]

please post detailed logs.

I have the same problem. Stop/Start in the Console doesn't help, but Restarting the Service using Windows Services interface works and Serviio is detected right away (5 seconds after Restart of service). Currently, this is what I do whenever I take my pc out of sleep.

Too much personal information in the log file, but this happened right after my pc came out of sleep:

2013-04-12 18:31:23,505 INFO [UpdateChecker] Checking if a new version is available
2013-04-12 18:31:23,809 WARN [DiscoveryAdvertisementNotifier] Cannot acquire NIC for current bound IP address 192.168.1.108, will re-acquire new IP
2013-04-12 18:31:23,809 INFO [EventSubscriptionExpirationChecker] Leaving EventSubscriptionExpirationChecker, removing all event subscriptions
2013-04-12 18:31:23,809 INFO [EventDispatcher] Leaving EventDispatcher
2013-04-12 18:31:23,810 INFO [DiscoverySSDPMessageListener] Leaving DiscoverySSDPMessageListener
2013-04-12 18:31:24,204 INFO [Device] Updated bound IP address of Device with UUID: 846be3a6-e7a8-3d4a-b261-e1933d0510a0, bound address: 169.254.15.30
2013-04-12 18:31:24,204 INFO [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2013-04-12 18:31:24,210 INFO [EventSubscriptionExpirationChecker] Starting EventSubscriptionExpirationChecker
2013-04-12 18:31:24,213 INFO [EventDispatcher] Starting EventDispatcher
2013-04-12 18:31:26,458 INFO [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth9 (VirtualBox Host-Only Ethernet Adapter) and address 169.254.15.30, timeout = 0
2013-04-12 18:31:28,502 INFO [RendererExpirationChecker] Leaving RendererExpirationChecker

At this point I restarted the Serviio service using Windows Services interface. Shortly after this, this is what Serviio detected (and what works):

2013-04-12 18:35:04,291 INFO [UpdateChecker] Checking if a new version is available
2013-04-12 18:35:04,354 INFO [AbstractTranscodingDeliveryEngine] Cleaning transcode engine and its data
2013-04-12 18:35:04,374 INFO [WebServer] WebServer starting on port 8895
2013-04-12 18:35:04,379 INFO [EventSubscriptionExpirationChecker] Starting EventSubscriptionExpirationChecker
2013-04-12 18:35:04,379 INFO [EventDispatcher] Starting EventDispatcher
2013-04-12 18:35:04,379 INFO [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2013-04-12 18:35:04,384 INFO [RendererExpirationChecker] Starting RendererExpirationChecker
2013-04-12 18:35:04,637 INFO [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth3 (Intel(R) PRO/1000 MT Desktop Adapter) and address 192.168.1.108, timeout = 0

According to the Event Viewer, the network was not available until 18:31:34 (Serviio tried to connect already at 18:31:23)

I don't like the "plan B" that Serviio uses (connects to any available network it finds instead of the configured one). My reason is that my pc has 2 physical networks, one public and one private. I _never_ want to have Serviio connect/advertise itself on my public NIC, only the private. With the fallback handler as it is now, I have no control over where Serviio connects. I am just fortunate that I have a virtual unrouted NIC that it decides to attach itself to.

Maybe it should rather connect to 127.0.0.1 and try to connect to the configured network every 10 seconds for a minute and then maybe every minute for 10 minutes and then every hour for 24 hours and so on... or register to listen for NIC events (windows does have this, don't know if it is exposed to Java).

[zip]

let me check the code.

What did your search reveal?

[zip]

I put some more resilient code in. Will be included in 1.3.

Great! Looking forward to it.

I had this issue for the last couple of months and got so frustrated I just stopped using it. Removing my static IP resolved it. Thank you so much for the post!!!

[DenyAll]

@Fix - am curious, was your static address assigned by your router, or was it done at the PC. See: viewtopic.php?f=5&t=10336&p=68829&hilit=weird+ip+address#p68829

For me the problem went away (it was never prevalent anyway) but I have since set the service dependency for other reasons, so that may have something to do with it. Also, zip seems to have this one resolved for the next release: https://bitbucket.org/xnejp03/serviio/i ... ring-bound

<as an aside> @zip - have you considered making the service dependency standard when installing the Windows service (ie. dependant on ssdpsrv - see viewtopic.php?f=5&t=10410&p=69355&hilit=ssdpsrv#p69355)? This cannot hurt, it simply delays Serviio service start-up until after ssdp discovery services which is critical anyway, and seems to aid quite a few issues.

[zip]

<as an aside> @zip - have you considered making the service dependency standard when installing the Windows service (ie. dependant on ssdpsrv - see viewtopic.php?f=5&t=10410&p=69355&hilit=ssdpsrv#p69355)? This cannot hurt, it simply delays Serviio service start-up until after ssdp discovery services which is critical anyway, and seems to aid quite a few issues.

I've done it, just need to make sure it works on all Windows versions, during beta.

It's funny, in the last 24 since making my post the problem came back. When I try to manually stop the "Serviio" service, it will get stuck at "stopping" in the services.msc UI. My IP was set static through the PC's NIC settings, not the router (but it's been on automatic since my post). To further troubleshoot, I began considering other changes that may be causing it and I remembered I got a different NIC about the same time my Serviio became unstable: a Realtek PCI GBE Family Controller. I never actually downloaded the driver for it - I allowed Windows 8 to find it for me and all seemed well. I checked the Realtek site and got their specific driver. I restarted the service a few more times and still couldn't get the Serviio console to open. I then did a ipconfig /release and /renew and the console immediately opened. It was like magic and everything was up and running smoothly - even though it was still getting the same 10. DHCP address after the renew. Maybe it just needed a refresh. The Serviio console froze on me a couple of times when it was gathering media data. Here's some of those errors below (I wish I had saved the ones prior to the driver update as they seem to have been overwritten?). I am not sure I've actually found the cause yet. It does seem to respond well to the /release /renew though. Maybe in changing from static to DHCP a a few days ago, I was really just benefiting from the address renewal? I will probably just make a batch that renews the ip and restarts the service when I start the OS from Sleep mode. I will try going back to static after work today and see if simply refreshing the address was the original cure.

2013-06-03 18:46:43,846 WARN [PresentationView] Cannot connect to server: Connection Error (1000) - Connection refused: connect

2013-06-03 22:15:33,298 WARN [RepositoryView$LibraryStatusCheckerThread] Error retrieving library update status: Connection Error (1000) - Connection refused: connect

2013-06-03 22:15:50,871 WARN [RepositoryView$LibraryStatusCheckerThread] Error retrieving library update status: Connection Error (1000) - Connection refused: connect

EDIT: additionally, I would like to add that I've been using Serviio for a couple of years now and never had a problem when using the same static IP address that whole time. It wasn't until the Win 7 to Win 8 upgrade that I starting having issues. I changed the NIC around the same time though so I cannot rule one thing over the other. The "Start Serviio Service" and "Stop Serviio Service" batches from the start menu don't do what their title suggests. I have had to restart the service through the services.msc GUI. My account is an admin account and running as administrator makes no difference.

[DenyAll]

The IP address renewal is simply triggering Serviio's new binding recovery strategy. You should be able to see this in the log - when Serviio loses the IP address it shuts down its DiscoverySSDPMessageListener service (which is I believe the culprit - it fails when the PC awakes from sleep), reacquires a new IP address (in this case the same one) and then restarts the SDDPListener.

In the log file it will look something like:

  Code:

2013-06-01 21:34:23,732 WARN  [DiscoveryAdvertisementNotifier] Cannot acquire NIC for current bound IP address 192.168.0.2, will re-acquire new IP
2013-06-01 21:34:23,732 INFO  [DiscoverySSDPMessageListener] Leaving DiscoverySSDPMessageListener
2013-06-01 21:34:23,732 INFO  [EventSubscriptionExpirationChecker] Leaving EventSubscriptionExpirationChecker, removing all event subscriptions
2013-06-01 21:34:23,748 INFO  [DiscoveryAdvertisementNotifier] Leaving DiscoveryAdvertisementNotifier
2013-06-01 21:34:23,780 WARN  [MultiCastUtils] Could not find NIC with name 'eth6-0'
2013-06-01 21:34:23,780 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth6-0, will try again 9 times
2013-06-01 21:34:23,824 INFO  [EventDispatcher] Leaving EventDispatcher
2013-06-01 21:34:28,826 WARN  [MultiCastUtils] Could not find NIC with name 'eth6-0'
2013-06-01 21:34:28,948 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth6-0, will try again 8 times
2013-06-01 21:34:34,009 WARN  [MultiCastUtils] Could not find NIC with name 'eth6-0'
2013-06-01 21:34:34,009 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth6-0, will try again 7 times
2013-06-01 21:34:39,082 WARN  [MultiCastUtils] Could not find NIC with name 'eth6-0'
2013-06-01 21:34:39,082 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth6-0, will try again 6 times
2013-06-01 21:34:44,201 INFO  [Device] Updated bound IP address of Device with UUID: c41c5514-0d79-3774-967b-023b9e31d01f, bound address: 192.168.0.2
2013-06-01 21:34:44,202 INFO  [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2013-06-01 21:34:44,202 INFO  [EventDispatcher] Starting EventDispatcher
2013-06-01 21:34:44,203 INFO  [EventSubscriptionExpirationChecker] Starting EventSubscriptionExpirationChecker
2013-06-01 21:34:44,342 INFO  [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth6 (Intel(R) 82566DM-2 Gigabit Network Connection) and address 192.168.0.2, timeout = 0

If you are looking to create a batch file, you need not worry about renewing the IP address - the restart of the Serviio service will do the trick. You may want to implement this sleep workaround from jammoblammo: viewtopic.php?f=5&t=8393#p67123.

For some reason I do not get this sleep issue, even though its prevalent with many other Win users - Serviio always goes thru the above address binding recovery for me after awakening from sleep. I wish I could work out why - it may help others.

To that end I wonder if you could help me confirm a theory, by checking your event log (Windows System log, type Event in the start menu to get to the Event Viewer) - I get the following after awakening from sleep:

  Code:

Information   4/06/2013 6:12:03 PM   e1express   32   None
Warning       4/06/2013 6:12:03 PM   e1express   27   None
Information   4/06/2013 6:12:00 PM   Service Control Manager   7036   None
Information   4/06/2013 6:11:58 PM   e1express   32   None
Warning       4/06/2013 6:11:56 PM   e1express   27   None
Information   4/06/2013 6:11:57 PM   Service Control Manager   7036   None
Information   4/06/2013 6:11:57 PM   Service Control Manager   7036   None
Information   4/06/2013 6:11:50 PM   Kernel-General   1   None
Information   4/06/2013 5:34:50 PM   Service Control Manager   7036   None
Information   4/06/2013 5:34:50 PM   Service Control Manager   7042   None
Information   4/06/2013 5:34:40 PM   Kernel-Power   42   (64)

reading from bottom to top, I get a Kernel-Power 42 message (this is the system going to sleep), followed later by a Kernel-General 1 message (effectively the system waking up). Can you find the same sort of combination in your log, and then confirm whether you get a pair of e1express messages (or similar) after that. These messages relate to my ethernet port being shut down and then restarted.

I get this ethernet restart twice (not sure if that's relevant) but I think this is why I don't see the awakening from sleep problem - my ethernet shuts down momentarily, losing and then re-acquiring its IP address which then causes the bound address strategy in Serviio to be triggered. This strategy restarts the listener service and the world is a nice place again.

Hope the above makes sense. Given that your PC is not recovering from sleep, I wonder if you could explore your windows system event log and see if your ethernet port is being restarted after sleep. If it isn't, this would confirm my theory... then we just have to work out why the ethernet port restarts in my PC and not others.

Of course a nicer solution would be that the Serviio listener service survived sleep so it didn't need to be restarted, (if that is indeed the problem - I thought sleep was meant to preserve all application states so that they recovered seamlessly) but that is in zip's domain, which I know he is working through.

Thanks in advance.

I am at work now so I am unable to check my logs (I will update that later), but in the meantime I have some questions. I'm curious why the service freezes on me when I restart it. The Start and Stop Service batches that come with Serviio do not work. Ever. When I restart the service, I need to do it from the Windows gui (or a net start in cmd would probably work). In task manager I usually have two processes for "Serviio Service", one of which has a sub-process for "Serviio" (the Win 8 task manage has this view). When I "End Process" on the parent of the one with the sub-process, it closes immediately. But, when I "End Process" on the lone "Serviio Service" process, it does not go away for several minutes. If I try to stop the service from the services gui, it freezes at "stopping" for a similar amount of time. If I choose "restart" on the "Serviio" service, I will get the progress bar which freezes toward the end and doesn't do anything. This is the problem I've been experiencing for the last couple of months. I have to keep restarting the service, launching Serviio Console, and waiting several minutes for it to either fail or open - it usually fails without any feedback. I only get failed launch feedback when the service isn't started. And that's another issue. Sometimes when I try starting the service from the gui, it says "starting" for about 1 second, then goes back to "stopped". I've been going through this pretty much routinely for months, so I may have missed some details.

[DenyAll]

Hi Fix
Froggzy has just posted this: viewtopic.php?f=10&t=10629&p=70628#p70628
This may be related to your issues. While checking your event log you may also wish to explore this.

[DenyAll]

I have had a chance to work thru some of the issues in your post:

• I have never (until today) run the "Start Serviio Service" or "Stop Serviio Service" from the start menu item, but you are correct - they do not work for me either. I have always used Services.msc for this. I am on Win7-32 bit. @zip - any thoughts?
• When you say you are restarting from the GUI, do you mean task manager?. You should only abort tasks as a last resort. I also have two tasks, a larger one and smaller one. As a test I aborted these tasks - they shut down immediately.
• Using the Services.msc (or the net start and net stop commands in a command window) works as expected. Check the event log as suggested in my post above and try the suggestion from Froggzy - it may be coming into play?