new installed debian 9 strech with new installed emby keep crash in every 15 mins

[tokyohoo 0]

Hi All.

i installed the 4.5.4 armhf.deb in my debian nas sucessful but it keep crashed .

After  enter code in ssh  ----systemctl status emby-server --

● 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 Sat 2021-02-20 01:15:35 +08; 10min ago
  Process: 3769 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV)
 Main PID: 3769 (code=killed, signal=SEGV)

Feb 20 01:00:28 wdmc emby-server[3769]: Info App: SyncRepository Initialize write lock taken
Feb 20 01:00:28 wdmc emby-server[3769]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0178585 seconds
Feb 20 01:00:28 wdmc emby-server[3769]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Feb 20 01:00:28 wdmc emby-server[3769]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0081941 seconds
Feb 20 01:00:28 wdmc emby-server[3769]: Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
Feb 20 01:00:28 wdmc emby-server[3769]: Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0004366 seconds
Feb 20 01:00:28 wdmc emby-server[3769]: Info App: All entry points have started
Feb 20 01:15:35 wdmc systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Feb 20 01:15:35 wdmc systemd[1]: emby-server.service: Unit entered failed state.
Feb 20 01:15:35 wdmc systemd[1]: emby-server.service: Failed with result 'signal'.
                             ***end****

 

 

Attached --------my emby log report ----------

Also there are few hardware detection logs at /var/lib/emby/logs

 

Is it because i manually reboot the service cause this logs generated??

embyserver-63749381530-before crash.txt embyserver-after i restart service.txt

[tokyohoo 0]

one more time crashed today.  error code shows 

 

root@wdmc:/data# systemctl status emby-server
● 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 Sat 2021-02-20 11:19:29 +08; 4min 37s ago
  Process: 3515 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT)
 Main PID: 3515 (code=killed, signal=ABRT)

Feb 20 11:01:31 wdmc emby-server[3515]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Feb 20 11:01:31 wdmc emby-server[3515]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0107129 seconds
Feb 20 11:01:31 wdmc emby-server[3515]: Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
Feb 20 11:01:31 wdmc emby-server[3515]: Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0005358 seconds
Feb 20 11:01:31 wdmc emby-server[3515]: Info App: All entry points have started
Feb 20 11:19:29 wdmc emby-server[3515]: Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Feb 20 11:19:29 wdmc emby-server[3515]:    at Rssdp.SsdpCommunicationsServer+<SendMessage>d__23.MoveNext()
Feb 20 11:19:29 wdmc systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT
Feb 20 11:19:29 wdmc systemd[1]: emby-server.service: Unit entered failed state.
Feb 20 11:19:29 wdmc systemd[1]: emby-server.service: Failed with result 'signal'.

***end***

System logs attached .this time i purge the emby-server and reinstalled it.

this are the initial 2 reports after i reinstall the emby.

 

 

embyserver.txt embyserver-63749415679.txt

[Luke 42079]

Hi, there's an error in this log that I haven't seen before, but it should be easy enough to trap and fix for the next release.

In the meantime, for immediate relief, simply disable all of the server's dlna features, then restart it. If you need Dlna features, I'll have the fix in the next beta server. Thanks.

[tokyohoo 0]

8 minutes ago, Luke said:

Hi, there's an error in this log that I haven't seen before, but it should be easy enough to trap and fix for the next release.

In the meantime, for immediate relief, simply disable all of the server's dlna features, then restart it. If you need Dlna features, I'll have the fix in the next beta server. Thanks.

Thanks for the effort looking into my logs. 

I didn't install Dlna service yet. This today logs is base on fresh install. Even didn't set up homepage configuration yet too. 

I will still trying to find a way to solve. As this debian Deb at download site works very well in my another debian 8 jeisse Nas. 

 

[Luke 42079]

Dlna is enabled by default. you can turn it off in emby server settings.

[tokyohoo 0]

18 minutes ago, Luke said:

Dlna is enabled by default. you can turn it off in emby server settings.

I did apt upgrade of libc-bin(2.28-10) which I saw command line 

Processing triggers for libc-bin (2.28-10)

During the dpkg - i emby. Deb. 

After a bunch of stuff upgraded together. 

With your Dlna settings turned off. 

Service keep on about 25mins till now.hope can see longer result. 

 

 

[Luke 42079]

thanks for the feedback.

[tokyohoo 0]

38 minutes ago, Luke said:

Dlna is enabled by default. you can turn it off in emby server settings.

I would try one more round fresh install debian 9 and emby again with your method.

Because after I upgrade the libc-bin. Emby memory usage increase from 1.7mb to 140mb.

It even works as memory low as 830K.

Is it because of this crashing emby every about 15mins?or doesn't matter. As long as turned off Dlna. 

 

[Luke 42079]

140mb is not that much. Are you still having a problem?