v3.2.60 doesn't fully quit

[ChrisJ60 10]

The best thing to do right now is to keep frequent backups of the ~./config/data folder.

I do, but I am not confident of them; backing up database files while they are open typically yields a backup that when restored cannot be used. I am also using the Emby backup plugin but for me that is at the moment an untested situation. I need to verify that I can restore from those backups. Hence my desire to avoid potential database corruptions.

[Luke 38533]

The next release of Emby Server will be updating to .NET Core 2.1. It may help with this issue. Thanks.

[vangeliis 8]

The next release of Emby Server will be updating to .NET Core 2.1. It may help with this issue. Thanks.

 

 

Hi Luke,

 

Can you build the beta for macOS so we can test it?

[Luke 38533]

Here you go:

https://github.com/MediaBrowser/Emby.Releases/releases/download/3.4.1.10/embyserver-osx-x64-3.4.1.10.zip

 

Just be aware of this:

https://emby.media/community/index.php?/topic/58633-3403-virtualized-paths/&do=findComment&comment=574220

 

Thanks.

[vangeliis 8]

Hi @@Luke,

 

Initial testing with the above build shows it does not solve the problem with the lingering EmbyServer processes. How does it behave on your test machine?

 

Edited May 31, 2018 by vangeliis

[Luke 38533]

It's always been fine for me but i think i will need to test on another machine.

[vangeliis 8]

Ok, that's good to know.

[vangeliis 8]

Hi @@Luke,

 

Initial testing with the above build shows it does not solve the problem with the lingering EmbyServer processes. How does it behave on your test machine?

 

Screen Shot 2018-05-31 at 06.58.48.png

 

 

Hi @@Luke

 

Just to let you know v.3.5.0.0 does not solve the problem with lingering EmbyServer processes after quitting the app.

[Luke 38533]

Thanks for the info. We'll do additional testing on it.

[ChrisJ60 10]

Problem is still there with 3.5.0.0 which I just updated to.

 

Side note: I was prompted to update to this version but after doing so I see that it is marked as 'beta'. That's quite disturbing; I don't expect the software to recommend me to update to a beta version nor that the beta version is what one downloads from the main Emby download site. Wad this an oversight? Is 3.5.0.0 really a beta version?

[Luke 38533]

No it's not a beta, that's just a tagging mistake. You won't see that in 3.5.1. Thanks.

[vangeliis 8]

Thanks for the info. We'll do additional testing on it.

 

 

Hi Luke,

 

Same problem with v3.5.2.0. 

[Luke 38533]

Thanks for the info.

[sfatula 189]

Yep, same problem here. Would a dump or trace of some sort help? 

 

ps waux | grep -i emby

sfatula          56536   0.0  0.5  6644768 118956   ??  S     9:43AM   0:12.41 /Applications/EmbyServer.app/Contents/MacOS/EmbyServer

Edited August 31, 2018 by sfatula

[Luke 38533]

We are still looking into it, thanks.

[Luke 38533]

Here's the latest beta server for MacOS, for those interested:

https://emby.media/community/index.php?/topic/65165-emby-server-beta-for-macos/

 

Thanks.

[Luke 38533]

The shutdown problem will be resolved in Emby Server 4.1. Thanks.

[SamES 955]

I'm still seeing this in beta 4.1.0.24.  Let me know if you want a log

[BananaManCJ 0]

If I press "Exit," I still see the EmbyServer process running in activity monitor and cant start the server again. If I quit the process and then try to restart the server, It'll say that the program is unresponsive. It will only start again if I log out of my Mac and log in again. Is that the same problem?

P.S. I don't have any problems when I press "Restart Emby Server."

[hstamas 162]

Just as an FYI, as of beta 4.1.0.24 I still cant shut down cleanly. My routine is to shut down the server normally. Go into Activity Monitor and shut down the lingering Emby instance thats still running. Restart Emby. Maybe 40% of the time at this stage Emby will not start back up so I need to restart my Mac to make this happen.

[ChrisJ60 10]

I've investigated this in some detail and at least in my experience this problem is caused because sometimes the Emby 'helper' process (Electron) does not quit when the server is stopped and if it remains running then Emby will not start. You can just kill that process manually or if you prefer you can just use a script that I wrote to stop and start the server from the command line; the script takes care of this problem and when using this script I have not yet had any issues with Emby failing to stop or start as expected. The script (called 'emby') is attached to this post.

 

Chris

 

[hstamas 162]

I've investigated this in some detail and at least in my experience this problem is caused because sometimes the Emby 'helper' process (Electron) does not quit when the server is stopped and if it remains running then Emby will not start. You can just kill that process manually or if you prefer you can just use a script that I wrote to stop and start the server from the command line; the script takes care of this problem and when using this script I have not yet had any issues with Emby failing to stop or start as expected. The script (called 'emby') is attached to this post.

 

Chris

 

Thanks for pointing this out and offering a workaround! Just note that I am aware of the helper app not quitting but find that even if I shut that down via Activity Monitor so there is nothing Emby still running, very often Emby will just not start back up unless I restart my Mac. This as been going on quite some time.

[thebnich 5]

This is still an issue for me as of 4.2.1.0.

 

I created a simple launcher app as a workaround: https://github.com/thebnich/EmbyLauncher.

 

This can be launched from Spotlight/Launchpad, and ensures that Emby Server starts (and terminates) properly. It works by launching Emby via shell script (thanks to this comment), and monitors the embytray process to terminate the EmbyServer process accordingly.

 

Hope it helps!

[yiding 0]

Thanks for the launcher. I'm also seeing this issue in 4.2.1.0

[RobbyBobby 16]

I've been manually quitting the ophaned helper since version 3.x of Emby. I'll take a look at launcher, thank you @thebinch.