Server stopping

[Thor.2 1]

FYI

I updated to 4.6.3.0 Saturday morning.

Today Emby crashed, I ran systemctl status emby-server

Jun 22 07:52:31 example.emby.com systemd[1]: emby-server.service: systemd-oomd killed 4 process(es) in this unit.
Jun 22 07:52:31 example.emby.com systemd[1]: emby-server.service: Main process exited, code=killed, status=9/KILL
Jun 22 07:52:34 example.emby.com systemd[1]: emby-server.service: Failed with result 'signal'.
Jun 22 07:52:34 example.emby.com systemd[1]: emby-server.service: Consumed 3d 2h 49min 20.300s CPU time.

 

restarted and running again

Edited June 23, 2021 by Thor.2

[Luke 42078]

6 hours ago, Thor.2 said:

FYI

I updated to 4.6.3.0 Saturday morning.

Today Emby crashed, I ran systemctl status emby-server

Jun 22 07:52:31 example.emby.com systemd[1]: emby-server.service: systemd-oomd killed 4 process(es) in this unit.
Jun 22 07:52:31 example.emby.com systemd[1]: emby-server.service: Main process exited, code=killed, status=9/KILL
Jun 22 07:52:34 example.emby.com systemd[1]: emby-server.service: Failed with result 'signal'.
Jun 22 07:52:34 example.emby.com systemd[1]: emby-server.service: Consumed 3d 2h 49min 20.300s CPU time.

 

restarted and running again

Hi there, please attach the emby server log from when that happened. thanks.

[Thor.2 1]

Maybe database corruption during update?

Last night, Scan Media and Refresh Guide tasks would not run and failed every time tried. 
 

Also marking shows watched was not working.

 

reboot cleared the errors.

I’ll look up for the clean database tool.

[Luke 42078]

@Thor.2 

I've split your postings into a separate topic. You could take a look at this:

https://support.emby.media/support/solutions/articles/44002210894-corrupt-database

But please attach the emby server log so that we can confirm. Thanks.

[thegrunge 29]

@Luke From my side sometimes the .service crashes, but does not restart automatically. I would like to modify the .service file so that it restarts in the event of a crash.

[Unit]
Description=Emby Server is a personal media server with apps on just about every device.
After=network.target

[Service]
EnvironmentFile=/etc/emby-server.conf
WorkingDirectory=/opt/emby-server
ExecStart=/opt/emby-server/bin/emby-server
RestartForceExitStatus=3
User=emby

[Install]
WantedBy=multi-user.target

 

I wonder if I could add:

Restart=on-failure
RestartSec=5s

Edited July 1, 2021 by thegrunge

[Luke 42078]

Have you tried it?

[thegrunge 29]

I have already modified the .service file a few times, because I had this problem. for some time I haven't had to do it, because we have to modify the service every time there is an update, and the server was stable.

[Unit]
Description=Emby Server is a personal media server with apps on just about ever>
After=network.target

[Service]
EnvironmentFile=/etc/emby-server.conf
WorkingDirectory=/opt/emby-server
ExecStart=/opt/emby-server/bin/emby-server
RestartForceExitStatus=3
User=emby
Restart=on-failure
RestartSec=5s

[Install]
WantedBy=multi-user.target

 

I don't know if we can afford to remove: RestartForceExitStatus=3

I also tried: Restart=always  this way every time I stop the service it restarts automatically after 5 seconds.

But It seems to me that I no longer had this problem by modifying the .service in this way. I speak about it today because the problem occurred. I simply did systemctl restart emby-server to restart the .service

 

 

Edited February 27, 2022 by thegrunge

[thegrunge 29]

I'll give it a try and let you know if the problem comes back.

[Unit]
Description=Emby Server is a personal media server with apps on just about every device
After=network.target

[Service]
EnvironmentFile=/etc/emby-server.conf
WorkingDirectory=/opt/emby-server
ExecStart=/opt/emby-server/bin/emby-server
User=emby
Restart=on-failure
RestartSec=3s

[Install]
WantedBy=multi-user.target

[thegrunge 29]

There was no error with the service I remember that it had simply stopped. So I did like this. This way when the service stops for no reason and without errors it restarts immediately Using Restart=always is ideal in this case when the service closes, whether without or with error, it restarts immediately, even if we turn off the server in the dashbord. with systemctl stop emby-server it stays closed so it's perfect like that.  Usually Restart=on-failure is used

 

[Unit]
Description=Emby Server is a personal media server with apps on just about every device
After=network.target
StartLimitIntervalSec=60
StartLimitBurst=3

[Service]
Type=simple
User=emby
Group=emby
EnvironmentFile=/etc/emby-server.conf
WorkingDirectory=/opt/emby-server
ExecStart=/opt/emby-server/bin/emby-server
Restart=always

[Install]
WantedBy=multi-user.target