Shutting down Emby server

[JustEric78 24]

Hello,

Recently I have run into a minor challenge where it appears the shut down server button within the server manager UI no longer actually stops the server. I do not know if this is specific to the fact I run this as a service or not, but I do not know how else to shut down the server to restart it. Any help is appreciated. 

[MBSki 1114]

It's likely related to running it as a service. The shutdown should still work, but you shouldn't use it. Instead, go to services and find the service that you created. I called mine EmbyServer. From services, just right click the service and choose restart.  

[JustEric78 24]

49 minutes ago, mbarylski said:

It's likely related to running it as a service. The shutdown should still work, but you shouldn't use it. Instead, go to services and find the service that you created. I called mine EmbyServer. From services, just right click the service and choose restart.  

Unfortunately the service method does not work as this is what I see after a few minutes after the service starts, meaning it has no status. I think it just starts up the executable and that is it. Actually, as I just typed that it dawned on me that I bet I can just killed the executable. The button on the UI has worked for years though. 

Edit: Yeah killing the executable worked, but that is obviously not ideal. 

Edited August 2, 2021 by JustEric78

[MBSki 1114]

21 minutes ago, JustEric78 said:

Unfortunately the service method does not work as this is what I see after a few minutes after the service starts, meaning it has no status. I think it just starts up the executable and that is it. Actually, as I just typed that it dawned on me that I bet I can just killed the executable. The button on the UI has worked for years though. 

Edit: Yeah killing the executable worked, but that is obviously not ideal. 

It's possible the executable was running, in which case the service wouldn't start. Do you have "Run at Server Startup" unchecked? Make sure that's unchecked and then start the service.

[JustEric78 24]

3 minutes ago, mbarylski said:

It's possible the executable was running, in which case the service wouldn't start. Do you have "Run at Server Startup" unchecked? Make sure that's unchecked and then start the service.

Edit: writing that first line again as it could have been confusing.

No, I do not have that checked, I have had this setup for years. There is nothing in the in the tray like showing the server is running, this is in the task manager. The EmbyServer executable is what the service starts up there. 

Edited August 2, 2021 by JustEric78

[MBSki 1114]

Hmmm, strange. Are you able to get the service started again? Maybe it hung for some reason.

[JustEric78 24]

6 minutes ago, mbarylski said:

Hmmm, strange. Are you able to get the service started again? Maybe it hung for some reason.

Yes, no problems at all. Just that button used to shut the server down and now it does not any longer. I killed EmbyServer.exe in the task manager and started the service again no problem. Just looking for a better way then have to kill the executable. 

[MBSki 1114]

I just tested mine and it does shut down, so there might be something different about your setup, or there's a bug for a particular configuration. I also haven't updated to 4.6.0.3 yet. Maybe it's a bug in 4.6.0.4? 

@cayars Are you using the service? Can you test shutdown?

[Carlo 4561]

I'm not currently using Emby Server running as a service so I can't test this.

[JustEric78 24]

8 minutes ago, mbarylski said:

I just tested mine and it does shut down, so there might be something different about your setup, or there's a bug for a particular configuration. I also haven't updated to 4.6.0.3 yet. Maybe it's a bug in 4.6.0.4? 

@cayars Are you using the service? Can you test shutdown?

I am on 4.6.4.0 so there could be something there. 

[Luke 42079]

It's probably just taking a little longer to shut down. I would not kill the process as that could end up causing you other problems.

[JustEric78 24]

1 minute ago, Luke said:

It's probably just taking a little longer to shut down. I would not kill the process as that could end up causing you other problems.

Took me two hours to think of killing it in the task manager brotha, how long do you want me to wait to appease the fact there is a problem there?

[Carlo 4561]

Can you try a scheduled task->rotate log job.

Use the shutdown button from the UI and if nothing happens in 5 minutes upload the server log for us to look at.

BTW, does the "Restart Emby Server" on the same menu work?

[JustEric78 24]

14 minutes ago, cayars said:

Can you try a scheduled task->rotate log job.

Use the shutdown button from the UI and if nothing happens in 5 minutes upload the server log for us to look at.

BTW, does the "Restart Emby Server" on the same menu work?

The restart never worked for the service, I do not know how it could to be honest thinking from a programming perspective. Is it starting the service or the program running in the "hidden icons". The shutdown used to work to kill the executable in the task manager is all I know which I do not think should make a difference if it were started from the service or the tray icon, no?

[Luke 42079]

18 hours ago, JustEric78 said:

Took me two hours to think of killing it in the task manager brotha, how long do you want me to wait to appease the fact there is a problem there?

Thanks.

[pwhodges 2012]

On 02/08/2021 at 17:52, JustEric78 said:

Just looking for a better way then have to kill the executable. 

You're running it as a Windows service?  Then why not simply use the Windows facilities (GUI or command line) for shutting down a service?  E.g. the really tricky: "net stop EmbyService".  I take it that the service is not set to automatically restart if it stops?

I presume you are not using nssm to control your service, as recommended by the documentation; if you were the command to stop the service would be the equally complicated: "nssm stop EmbyService" - that's the way I do it; nssm provides an easy way to set up all the parameters that a service might need.

If the behaviour of your service has changed, you need to think of what might have changed in your system to cause this.  Have you, for instance, made any changes in security settings or user rights?

Paul

[JustEric78 24]

9 minutes ago, pwhodges said:

You're running it as a Windows service?  Then why not simply use the Windows facilities (GUI or command line) for shutting down a service?  E.g. the really tricky: "net stop EmbyService".  I take it that the service is not set to automatically restart if it stops?

I presume you are not using nssm to control your service, as recommended by the documentation; if you were the command to stop the service would be the equally complicated: "nssm stop EmbyService" - that's the way I do it; nssm provides an easy way to set up all the parameters that a service might need.

If the behaviour of your service has changed, you need to think of what might have changed in your system to cause this.  Have you, for instance, made any changes in security settings or user rights?

Paul

Nothing has changed if you scroll up you will see it starts the service, then the status goes away. I am using the recommended solution and I followed the guide that was provided to do so. Nothing in my environment has been modified in a very long time. 

edit: I just went to get the log and I noticed the service status was still there from yesterday. So it must stay there for a period of time and eventually go away. It is also possible as I have learned not to check the status that the UI button is stopping it, but the exe is not being killed. I will investigate more and post a log soon. 

Edited August 3, 2021 by JustEric78

[JustEric78 24]

Update to the above post. So I am really confused now, and I will have to let the server run until that status goes away in the service manager as that appears to be what the problem is (guessing). I went to recreate the problem and it was actually killing the server when I hit the button. The status is still there so I am wondering again, if there is some kind of correlation there. Not sure why there would be, but it is working so there has to be something to do with how long the server is up since it was previously shut down as I generally leave it up until there is a server update for Emby. 

No log attached as I am currently unable to recreate the problem, we are IT this stuff does not fix itself..

I will revive this post with a log when I am able to recreate the problem.  

[gateway786 4]

Hi everyone 

i am face this issue for few days

so i am solved this problem 

1 chq your firewall 

disable your firewall 

2 chq ur windows update 

3 device manager 

and scan the software 

4 chang the server port

the restart your computer 

and enjoy the Emby server 

last maybe you are use the

rd client 

Anydask

teamviwer

run the server then cloes the remote access and server is shutdown