Service Inactive After Upgrade

[ChancellorSuda 0]

Upgraded to 4.7 - no longer able to access emby - log below - I'm sure there is something simple to be missed here. 

 

● emby-server.service - Emby Server is a personal media server with apps on just about every device
     Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Tue 2022-05-24 15:07:02 EDT; 13min ago
    Process: 811 ExecStart=/opt/emby-server/bin/emby-server (code=exited, status=0/SUCCESS)
   Main PID: 811 (code=exited, status=0/SUCCESS)

May 24 15:07:02 Lord-of-Shaft-III emby-server[811]:    at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
May 24 15:07:02 Lord-of-Shaft-III emby-server[811]:    at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallo>
May 24 15:07:02 Lord-of-Shaft-III emby-server[811]:    at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocati>
May 24 15:07:02 Lord-of-Shaft-III emby-server[811]:    at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream fileStream, String path, FileMode mode, FileAccess access, FileShare share, Int32 buf>
May 24 15:07:02 Lord-of-Shaft-III emby-server[811]:    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
May 24 15:07:02 Lord-of-Shaft-III emby-server[811]:    at Emby.Server.Implementations.Logging.FileLogger..ctor(String path)
May 24 15:07:02 Lord-of-Shaft-III emby-server[811]:    at Emby.Server.Implementations.Logging.SimpleLogManager.ReloadLogger(LogSeverity severity, CancellationToken cancellationToken)
May 24 15:07:02 Lord-of-Shaft-III emby-server[811]: InnerException: System.IO.IOException: Permission denied
May 24 15:07:02 Lord-of-Shaft-III emby-server[811]: Source:
May 24 15:07:02 Lord-of-Shaft-III emby-server[811]: TargetSite:

 

[ChancellorSuda 0]

UPDATE - when performing restart of the service, the status shows active for a moment, than goes to inactive after another status check - log shown below:

tkg2609@Lord-of-Shaft-III:~$ sudo systemctl restart emby-server
tkg2609@Lord-of-Shaft-III:~$ sudo systemctl status emby-server
● emby-server.service - Emby Server is a personal media server with apps on just about every device
     Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2022-05-24 15:27:19 EDT; 3s ago
   Main PID: 1302 (EmbyServer)
      Tasks: 11 (limit: 38263)
     Memory: 9.1M
     CGroup: /system.slice/emby-server.service
             └─1302 /opt/emby-server/system/EmbyServer -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexit>

May 24 15:27:19 Lord-of-Shaft-III systemd[1]: Started Emby Server is a personal media server with apps on just about every device.

tkg2609@Lord-of-Shaft-III:~$ sudo systemctl status emby-server
● emby-server.service - Emby Server is a personal media server with apps on just about every device
     Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Tue 2022-05-24 15:27:24 EDT; 4s ago
    Process: 1302 ExecStart=/opt/emby-server/bin/emby-server (code=exited, status=0/SUCCESS)
   Main PID: 1302 (code=exited, status=0/SUCCESS)

May 24 15:27:24 Lord-of-Shaft-III emby-server[1302]:    at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preall>
May 24 15:27:24 Lord-of-Shaft-III emby-server[1302]:    at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocat>
May 24 15:27:24 Lord-of-Shaft-III emby-server[1302]:    at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream fileStream, String path, FileMode mode, FileAccess access, FileShare share, Int32 bu>
May 24 15:27:24 Lord-of-Shaft-III emby-server[1302]:    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
May 24 15:27:24 Lord-of-Shaft-III emby-server[1302]:    at Emby.Server.Implementations.Logging.FileLogger..ctor(String path)
May 24 15:27:24 Lord-of-Shaft-III emby-server[1302]:    at Emby.Server.Implementations.Logging.SimpleLogManager.ReloadLogger(LogSeverity severity, CancellationToken cancellationToken)
May 24 15:27:24 Lord-of-Shaft-III emby-server[1302]: InnerException: System.IO.IOException: Permission denied
May 24 15:27:24 Lord-of-Shaft-III emby-server[1302]: Source:
May 24 15:27:24 Lord-of-Shaft-III emby-server[1302]: TargetSite:
May 24 15:27:24 Lord-of-Shaft-III systemd[1]: emby-server.service: Succeeded.
lines 1-16/16 (END)

 

[ChancellorSuda 0]

UPDATE - RESOLUTION

after upgrade to latest version (4.7) - there was a reset of the following file:  /lib/systemd/system/emby-server.service

It reverted the User line back to 'emby' - once I changed back to my own user ID (and rebooted), Emby server came right back up. 

Thank you whomever read through my personal therapy session to resolve this. 

[Luke 42078]

Thanks for following up.

[jrbt123 2]

On 25/05/2022 at 06:34, ChancellorSuda said:

UPDATE - RESOLUTION

after upgrade to latest version (4.7) - there was a reset of the following file:  /lib/systemd/system/emby-server.service

It reverted the User line back to 'emby' - once I changed back to my own user ID (and rebooted), Emby server came right back up. 

Thank you whomever read through my personal therapy session to resolve this. 

Thanks! Exactly the same issue. Your answer saved my life!