gleep52 17 Posted March 16, 2017 Posted March 16, 2017 The DNLA service part of Emby works fine upon a total server hardware restart. But when I do a manual restart of the Emby service via the webpage dashboard, the DNLA service doesn't appear on my network anymore. I have to reboot the hardware server to get it back up and running again. What can I provide to diagnose this?
Happy2Play 9784 Posted March 17, 2017 Posted March 17, 2017 I always thought stopping and starting DLNA server required "server" restart. You just don't get a pop-up say you have to. Just like if you enable debug logging you have to restart server once enabled or disable to start or stop debug logging.
gleep52 17 Posted March 17, 2017 Author Posted March 17, 2017 So does that mean if we do a dashboard "restart" it kills DNLA and doesn't come back up until I reboot the physical hardware? Is this expected? Seems like a plot flaw and don't recall seeing that in the past. I have a few devices in my home that stream pictures via DNLA as a screensaver, and they work all the time until after the recent update. Now when I restart the Emby service via the dashboard, it kills DNLA until I reboot the physical hardware.
Happy2Play 9784 Posted March 17, 2017 Posted March 17, 2017 So does that mean if we do a dashboard "restart" it kills DNLA and doesn't come back up until I reboot the physical hardware? Is this expected? Seems like a plot flaw and don't recall seeing that in the past. I have a few devices in my home that stream pictures via DNLA as a screensaver, and they work all the time until after the recent update. Now when I restart the Emby service via the dashboard, it kills DNLA until I reboot the physical hardware. No, restarting the server should restore all features, you should not have to restart the system/hardware to restore features. My test of just disabling and re-enabling DLNA server, showed Windows 10 could no longer see the DLNA server until the server was restarted not the machine. Did not check on any other DLNA device.
Luke 42085 Posted March 17, 2017 Posted March 17, 2017 For some devices, depending on what detection methods they use, it could take a minute or so before they see Emby Server after a restart.
gleep52 17 Posted March 17, 2017 Author Posted March 17, 2017 Well I just restarted the server from dashboard again and the problem didn't happen this time. DNLA restarted properly. However, when DNLA crashed earlier today (restarted for collecting fresh logs), I left it alone for about 4 hours and it didn't ever come back to life. I tried restarting from dashboard many times, and also went to the DNLA settings and unchecked the option to enable the service, and saved, then waited a bit and re-checked it to turn it back on. Still didn't fix the problem. Same thing happened yesterday as well - I guess I don't know what's triggering the scenario, but it's always after I use the restart in dashboard function. So for some reason DNLA doesn't start back up sometimes... Is there a command I can type or do that will restart the DNLA service?
Luke 42085 Posted March 17, 2017 Posted March 17, 2017 You could also try restarting the apps you're trying to connect from.
gleep52 17 Posted March 17, 2017 Author Posted March 17, 2017 Oh I did - about every 15 minutes on my nVidia Shield, and a few times from my Kindle. As soon as I reboot the hardware, it all starts working again.
gleep52 17 Posted March 17, 2017 Author Posted March 17, 2017 Anyway - so is there a way to manually start the DNLA process? Just incase it doesn't start sometime in the future again?
Luke 42085 Posted March 17, 2017 Posted March 17, 2017 It does start. I realize you are perceiving this as dlna not starting but the issue is something else that we're not seeing yet.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now