emby service breaks after some time

[albertfa 0]

Hi, I have emby running in a LXC container with 2 cores CPU, 8Gb RAM and 2 Gb Swap disk... and after some minutes runnig the service exites. The container still works but emby not. this is the response from container logs:

20:55 emby-server.service: Consumed 14min 15.345s CPU time. systemd

20:55 emby-server.service: Failed with result 'signal'. systemd

20:55 emby-server.service: Main process exited, code=killed, status=9/KILL systemd

20:10 Info App: All entry points have started

 

Any idea?

Thanks!

[Q-Droid 989]

A signal 9/KILL means something external killed the process and need to find what that was.

 

[Luke 42078]

if you want to attach the emby server log we'll let you know if it contains anything obvious that might help you solve the problem:

How to Report a Problem

But as he said, it may have been terminated by the OS.

[albertfa 0]

Hi, thanks for the answers. I think OS kill the process because she puts memory to 98% for too long, see attached picture. But I can't find the reason

I have attached server logs.

 

 

hardware_detection-63834379838.txt embyserver-63834473316.txt

[Q-Droid 989]

Can you post the syslog for the container?

Do you have a large, maybe new photo library and do you know if Emby has scanned those photos yet?

[albertfa 0]

I' start thinking on this, a problem with the library, maybe a corrupted file or somethink like this. If I can't solve the problem, I will probably delete the library files and start again, but If I can not find the reason  who knows it may happends again

Here you have the logs.

journalctl.txt

[Q-Droid 989]

That's a very short log and nothing in there about the Emby process.

I asked about photos specifically because this type of media has been known to cause high workload problems. @Luke would know what to look for specifically and if another Emby release has fixes for the problem.