Luke 42077 Posted January 21, 2018 Posted January 21, 2018 Are you able to try changes on the betas? Thanks.
revengineer 142 Posted January 21, 2018 Author Posted January 21, 2018 No, not on the server with the shutdown issue. Sorry.
revengineer 142 Posted January 26, 2018 Author Posted January 26, 2018 Is there a potential fix for this in the current beta?
Luke 42077 Posted January 26, 2018 Posted January 26, 2018 No, but if you had the ability to jump on betas then I will dive back into this.
revengineer 142 Posted January 26, 2018 Author Posted January 26, 2018 I could temporarily disable the stable version and unzipping and running the beta in a temporary folder different from that of the stable installation. Would that work? Or would this overwrite some file in the other installation?
revengineer 142 Posted January 26, 2018 Author Posted January 26, 2018 ok working this now. i have time to test this weekend or next if you have anything. during the week i will be on travel. not sure how complex the code changes are.
revengineer 142 Posted January 26, 2018 Author Posted January 26, 2018 (edited) fyi, to start out I installed v3.2.70 as portable to see if the problem reproduced. I did the basic configuration but did not even define any library. I did install the backup plugin so that I can restore the config of the main server. Even that simple setup would not shut down within 5 minutes, so I rebooted. Result: I can reproduce the issue with a new portable installation, so I am ready for testing betas in this setup. Â EDIT: with "basic configuration" I meant the initial guided configuration. No settings were changed other than entering the emby key and installing the backup plugin. Edited January 27, 2018 by revengineer
Luke 42077 Posted January 27, 2018 Posted January 27, 2018 ok if you're already on the beta and could produce a new log that would be great, thanks.
revengineer 142 Posted January 27, 2018 Author Posted January 27, 2018 (edited) Â New log attached. There seems to be an additional line of info from 3.2.70.3: 2018-01-27 07:46:12.617 Info App: Disposing DlnaEntryPoint 2018-01-27 07:46:12.617 Info Dlna: Disposing DeviceDiscovery 2018-01-27 07:46:12.618 Info Dlna: Disposing SsdpCommunicationsServer 2018-01-27 07:46:12.618 Info Dlna: SsdpCommunicationsServer disposing _BroadcastListenSocket. 2018-01-27 07:46:12.619 Info Dlna: SsdpCommunicationsServer Disposing 2 sendSockets 2018-01-27 07:46:12.619 Info Dlna: SsdpCommunicationsServer disposing sendSocket Log.txt Edited January 27, 2018 by revengineer
revengineer 142 Posted January 28, 2018 Author Posted January 28, 2018 Is there anything wrt to this issue in newly released v3.2.70.4 that I should be testing?
bfir3 117 Posted January 28, 2018 Posted January 28, 2018 I just updated to 3.2.70 and had the same issue with the Emby instance never shutting down. I've had this problem many times in the past as well. My last two log lines are usually related to DLNA as seen here: 2018-01-28 10:34:25.876 Info App: Disposing DlnaProfileEntryPoint 2018-01-28 10:34:25.876 Info App: Disposing DlnaEntryPoint And I have all DLNA features turned off in the settings. I had to restart the machine manually in order to get the update to complete.
revengineer 142 Posted January 28, 2018 Author Posted January 28, 2018 I just updated to 3.2.70 and had the same issue with the Emby instance never shutting down. I've had this problem many times in the past as well. My last two log lines are usually related to DLNA as seen here: 2018-01-28 10:34:25.876 Info App: Disposing DlnaProfileEntryPoint 2018-01-28 10:34:25.876 Info App: Disposing DlnaEntryPoint And I have all DLNA features turned off in the settings. I had to restart the machine manually in order to get the update to complete. Â If the log entries you list are truly the last ones, I would argue that your issue is different from mine. My problem existed since I first started using emby a couple of years ago, and is not new to v3.2.70.
bfir3 117 Posted January 28, 2018 Posted January 28, 2018 (edited) Those are the last entries, and I've been having this issue for years as well. You can check in my post history as I've posted in other threads about this over that time. Don't know if it's the same issue, but it's too bad that it exists either way. For me it doesn't matter that much because it doesn't deter me from using the app, I just find a workaround. But I'm sure it's frustrating for the devs that these issues exist because they definitely deter newer users and less experienced users who make minimal to no extra effort to seek out a solution. They will encounter the issue, and then just potentially stop using the app altogether. Â edit: Also maybe not the same source of the problem, but the symptom that Emby doesn't shut down completely is the same. Edited January 28, 2018 by bfir3
revengineer 142 Posted January 28, 2018 Author Posted January 28, 2018 Interesting. For the longest times the lines you showed were my last ones as well. For v3.2.70, Luke added extra debug log entries and another one appeared in the latest beta. So I was trying to poke at whether you were seeing any difference in recent logs. This would indicate whether there is single issue or multiple problems at play. In any case, I agree that this has been going on for too long and hopefully with our help it can get fixed soon.
bfir3 117 Posted January 28, 2018 Posted January 28, 2018 Ah well I haven't had to restart since updating to 3.2.70 so I guess we'll see what happens when I do.
revengineer 142 Posted January 28, 2018 Author Posted January 28, 2018 It would be great if you could try and posted the last lines in your log.
Luke 42077 Posted January 28, 2018 Posted January 28, 2018 can you attach a new log from the latest beta? thanks.
revengineer 142 Posted January 28, 2018 Author Posted January 28, 2018 Log from v3.2.70.5 attached. end log lines are: 2018-01-28 14:39:56.065 Info App: Disposing DlnaProfileEntryPoint 2018-01-28 14:39:56.065 Info App: Disposing DlnaEntryPoint 2018-01-28 14:39:56.066 Info Dlna: Disposing DeviceDiscovery 2018-01-28 14:39:56.067 Info Dlna: Disposing SsdpCommunicationsServer 2018-01-28 14:39:56.068 Info Dlna: SsdpCommunicationsServer disposing _BroadcastListenSocket. 2018-01-28 14:39:56.068 Info Dlna: SsdpCommunicationsServer Disposing 2 sendSockets 2018-01-28 14:39:56.068 Info Dlna: SsdpCommunicationsServer disposing sendSocket from 0.0.0.0 Looks like it tries to dispose an invalid DLNA IP. Log (6).txt
revengineer 142 Posted January 28, 2018 Author Posted January 28, 2018 Happy to be wrong here. Any suspicion 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