Emby server 4.0.0.2 crashed

[tdiguy 99]

Some time overnight emby crashed.

This was the output from memby-server status:

● emby-server.service - Emby Server is a personal media server with apps on just about every device.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Fri 2019-01-18 22:10:16 EST; 6h ago
  Process: 1030 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT)
Main PID: 1030 (code=killed, signal=ABRT)

Jan 18 17:09:20 media-server emby-server[1030]: Info App: SyncRepository Initialize write lock taken
Jan 18 17:09:20 media-server emby-server[1030]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Du
Jan 18 17:09:20 media-server emby-server[1030]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Jan 18 17:09:20 media-server emby-server[1030]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoin
Jan 18 17:09:20 media-server emby-server[1030]: Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
Jan 18 17:09:20 media-server emby-server[1030]: Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Dur
Jan 18 17:09:20 media-server emby-server[1030]: Info App: All entry points have started
Jan 18 22:08:40 media-server emby-server[1030]: Process is terminating due to StackOverflowException.
Jan 18 22:10:16 media-server systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT
Jan 18 22:10:16 media-server systemd[1]: emby-server.service: Failed with result 'signal'.

 

I have also attached the server log

 

I made the text i think that is the issue red, but how i might correct that I do not know.

emby.txt

Edited January 19, 2019 by tdiguy

[tdiguy 99]

I think i did this before, and honestly I dont know what emby is using for startups maybe systemV? I had problems finding much information on it and it seems its been depreciated in ubuntu 18 because the information i did find on it points to files that dont exist like initab.

Anyway what i ended up doing was renaming /etc/init/emby-server.conf to emby-server.conf.bak ( because in linux i hate removing anything that looks important and renaming to something thats invalid is just as good purpose wise )

 

I then created:

/etc/systemd/system/emby-server.service

[Unit]
Description=Emby Server service NOW with auto restart
[Service]
User=emby
# The configuration file application.properties should be here:
#change this to your workspace
WorkingDirectory=/var/lib/emby/cache
#path to executable.
#executable is a bash script which calls jar file
ExecStart=/opt/emby-server/bin/emby-server
#SuccessExitStatus=143
#TimeoutStopSec=10
Restart=always
RestartSec=3
[Install]
WantedBy=multi-user.target

make it executable with sudo chmod +x emby-server.service

restart sudo systemctl daemon-reload

enable the service sudo systemctl enable emby-server

 

Now emby will happily just reload itself if there is an error or if its terminated.

Do this only if you dont really care why emby stops or if you like spending time digging through logs to see if emby stopped. I do this because honestly when i am at work i dont like being bothered with starting emby because it terminated for some reason. It will happily just restart on its own, hopefully faster than my family notices there is a problem and calls me

[Luke 42079]

Can you try removing any plugins you may have added? Thanks

[tdiguy 99]

Can you try removing any plugins you may have added? Thanks

I think the only one outside the emby official plugins is the kodi companion. I will pull that one and see how it goes.

Seems light right now guide refresh and library scan are stuck, they have both been at 99% for over an hour.

[Luke 42079]

Thanks. I would just be patient and allow them to finish.

[tdiguy 99]

Ok, something probably needed to be restarted after modifying the service or something was locked for editing maybe. Either way it seems to be just fine now after rebooting.

[Luke 42079]

Thanks for the feedback.