Emby shutdown

[marciomaiden 3]

Good Morning.

I have a problem on my emby server, it sometimes the emby process shuts down. I've already eliminated plugins. I've tried everything I can think of but it's still having problems. I've the debug log active.

Is there any way to catch the error that causes the process to shut down?

Edited November 18, 2021 by marciomaiden

[marciomaiden 3]

Sorry, but I put it in the wrong section, it should be in the linux section.

[Luke 42077]

Hi there @marciomaiden can you please attach the emby server log from when this happens:

Thanks !

[marciomaiden 3]

Ok, however today I updated the version. but when it happens I'll copy the log to put it here.

[Luke 42077]

Great, thanks.

[marciomaiden 3]

Here is the log. it gave an error even now when using the app on android tv

embyserver.txt

[marciomaiden 3]

after starting generated a new log, I'll leave it in attach

embyserverNEW.txt

[marciomaiden 3]

By the way, to save the files I use a sharepoint account and to access it I use rclone

[Luke 42077]

What exactly happened?

[marciomaiden 3]

The service stops and I can't access it. Neither by browser nor by apps.

 

I have to do an emby-service restart to be able to access the service again

[marciomaiden 3]

As you can see on the picture

[Luke 42077]

Have you customized any emby server network settings?

[marciomaiden 3]

No. all the default

[marciomaiden 3]

so what i do was:

edit with nano /usr/lib/systemd/system/emby-server.service

 

and add on [Service]
Restart=on-failure
RestartSec=5s

for now is restarting the service on failure, i will investigate more on the reason of the service stop

Edited November 18, 2021 by marciomaiden

[uk_philip 0]

On 18/11/2021 at 17:20, marciomaiden said:

so what i do was:

edit with nano /usr/lib/systemd/system/emby-server.service

 

and add on [Service]
Restart=on-failure
RestartSec=5s

for now is restarting the service on failure, i will investigate more on the reason of the service stop

Same has been happening for me. I'll try your solutions. Thanks!

[Q-Droid 989]

Signal 9/KILL is a deliberate kill, not sign of a crash. You didn't post any details about your server so check the syslog and look for signs of memory exhaustion and oom killer or other activity killing processes.

 

[marciomaiden 3]

53 minutes ago, Q-Droid said:

Signal 9/KILL is a deliberate kill, not sign of a crash. You didn't post any details about your server so check the syslog and look for signs of memory exhaustion and oom killer or other activity killing processes.

 

You're right. I attach the server specifications. The point is that this problem only started happening with 2 or 3 versions, it always worked well.

I think the problem is with Ubuntu's oom, it seems to me. I don't have much experience with servers.

[Q-Droid 989]

Software in general isn't known for getting smaller and more efficient with each release...

Emby on your server might have been just below the threshold of memory usage and the latest update pushed it over the edge. If you can try it then another GB of RAM might get things back on track.

 

[marciomaiden 3]

For now, the service restart solution is working. I don't upgrade the service, as it would be more expensive, and honestly it's not worth it. I've also thought about rebuilding the server, but this time with debian instead of ubuntu.

[Luke 42077]

If you want to try and find the root cause, then as a test you could try removing the dlna plugin, and then restart the server and see how that compares. thanks.

[marciomaiden 3]

I have already removed this plugin and the problem remains.

The strange thing is that the machine's resources have always been these, and there has never been a problem. for now I'll leave it at that, with the command to restart the service, you don't even notice that the service fails, but later I'll have to reinstall the machine to see if it improves.