Jump to content

Emby seems to hang up complete server (linux)


Marc0
Go to solution Solved by Marc0,

Recommended Posts

Hi,

This is somewhat hard to tackle and to get 100% certainty, but I have a feeling EMBY hangs a complete linux node running on Docker.

Setup:

- Intel NUC, 16GB, 512GB SSD, CPU i5

- OS latest Alpine Linux distribution 

- Emby (latest production version) running in Docker (tried official image, tried Linuxserver.io image)

- Running in a headless setup

Problem:

Runnng Emby in the setup (see above), keeps hanging the Intel NUC so that the NUC in complete unresponsive. No SSH, no Network responses.

The server doesn't crash when:

1. Emby container is stopped (tested this for days)

2. Emby container is running but NO ONE connects (tested this for days)

The server does crash when: People are watching video and after a while the server just stops responding. (within the same evening)

 

I did memory tests, CPU tests on the NUC, but the hardware seems fine.

 

Question:

Can you help and point out ways to investigate this some more??

Edited by Marc0
Link to comment
Share on other sites

Q-Droid

Where is your media kept? How much free space on the root volume?

If it hangs again and you have to restart the server then attach the previous log (embyserver-nnnn.txt), not the latest (embyserver.txt). Might have to go back a log or two to find something.

I suspect resource exhaustion, likely storage but will have to see the emby log and maybe the syslog too.

Link to comment
Share on other sites

EODCrafter
2 hours ago, Marc0 said:

Hi,

This is somewhat hard to tackle and to get 100% certainty, but I have a feeling EMBY hangs a complete linux node running on Docker.

Setup:

- Intel NUC, 16GB, 256GB SSD, CPU i5

- OS latest Alpine Linux distribution 

- Emby (latest production version) running in Docker (tried official image, tried Linuxserver.io image)

- Running in a headless setup

Problem:

Runnng Emby in the setup (see above), keeps hanging the Intel NUC so that the NUC in complete unresponsive. No SSH, no Network responses.

The server doesn't crash when:

1. Emby container is stopped (tested this for days)

2. Emby container is running but NO ONE connects (tested this for days)

The server does crash when: People are watching video and after a while the server just stops responding. (within the same evening)

 

I did memory tests, CPU tests on the NUC, but the hardware seems fine.

 

Question:

Can you help and point out ways to investigate this some more??

@Lukewill suggest https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Link to comment
Share on other sites

  • Solution
20 minutes ago, Q-Droid said:

Where is your media kept? How much free space on the root volume?

If it hangs again and you have to restart the server then attach the previous log (embyserver-nnnn.txt), not the latest (embyserver.txt). Might have to go back a log or two to find something.

I suspect resource exhaustion, likely storage but will have to see the emby log and maybe the syslog too.

Root volume /dev/nvme0n1p3          452.9G      8.7G    421.2G   2% /

media is kept om 12TB volume Synology 1513+

If it crashes again I will atach this file!

Edited by Marc0
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

I changed to a Plex setup... no crashes what so ever,...

In the logging it seems Emby comes in all endless wait for a synology, where as Plex doesn't

Link to comment
Share on other sites

On 12/24/2022 at 7:07 AM, Marc0 said:

I changed to a Plex setup... no crashes what so ever,...

In the logging it seems Emby comes in all endless wait for a synology, where as Plex doesn't

Why, wouldn't you prefer a personal media server that is actually personal?

  • Like 1
Link to comment
Share on other sites

Q-Droid

You have at least one resource issue - you're reaching the inotify instance limit on your system and it keeps Emby from being able to monitor changes in the library (RTM). The logs also show that something is shutting down the Emby server. It could be Docker or the OS doing it so more logs would be needed.

Many of these for your libraries:

Quote

      System.IO.IOException: System.IO.IOException: The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.
           at System.IO.FileSystemWatcher.StartRaisingEvents()

Check/increase the values of:

fs.inotify.max_user_instances - increase to a value around 4096

fs.inotify.max_user_watches - no errors from this one but low instances could be masking it. target value of 131,072 if current is lower.

 

Link to comment
Share on other sites

You could also try turning off the realtime monitor for each of your emby libraries and then restart the server and see if that helps.

Link to comment
Share on other sites

2 hours ago, Q-Droid said:

You have at least one resource issue - you're reaching the inotify instance limit on your system and it keeps Emby from being able to monitor changes in the library (RTM). The logs also show that something is shutting down the Emby server. It could be Docker or the OS doing it so more logs would be needed.

Many of these for your libraries:

Check/increase the values of:

fs.inotify.max_user_instances - increase to a value around 4096

fs.inotify.max_user_watches - no errors from this one but low instances could be masking it. target value of 131,072 if current is lower.

 

Thanks Q-Droid: But How can I change this persistently in a Docker container and not losing it when "watchtower" is auto-updating the image and restarting the container?

Or do I have to set the values on the Docker Host?

 

 

[EDIT : Some testing shows that changing on the HOST, affects the containers.... correct?]

Edited by Marc0
Link to comment
Share on other sites

1 hour ago, Luke said:

You could also try turning off the realtime monitor for each of your emby libraries and then restart the server and see if that helps.

Thanks Luc, I try that as well.... 

 

(btw. Plex account is killed again, data was hosted in USA. I thought Swiss.... hate myself that I uploaded my whole meta to USA... stupid boy)

Link to comment
Share on other sites

Q-Droid
5 hours ago, Marc0 said:

Thanks Q-Droid: But How can I change this persistently in a Docker container and not losing it when "watchtower" is auto-updating the image and restarting the container?

Or do I have to set the values on the Docker Host?

 

 

[EDIT : Some testing shows that changing on the HOST, affects the containers.... correct?]

It's a host OS level setting or at the VM if using virtualization, not docker container level.

 

Link to comment
Share on other sites

5 minutes ago, Q-Droid said:

It's a host OS level setting or at the VM if using virtualization, not docker container level.

 

I had set it on the host. But Emby crashed again. 

Link to comment
Share on other sites

3 hours ago, Luke said:

Let us know how you get on. Thanks.

Hi Luke. Same. Server crashed with 3 hours again. Just out of the blue. No one was watching. I noticed it when I came home. 

Link to comment
Share on other sites

Happy2Play

Not really seeing anything in the log at the time it looks like it Gracefully shuts down, not a Crash.

2022-12-22 19:50:38.051 Info Server: http/1.1 Response 204 to ‌‍‍192.168.178.201‌. Time: 0ms. http://‌‍‍192.168.178.202‌:8097/Emby/Library/Refresh
2022-12-22 20:06:19.988 Info Server: Stopping HttpListener...
2022-12-22 20:06:19.992 Info Server: HttpListener stopped
2022-12-23 01:04:40.772 Info Server: http/1.0 Response 200 to ‌‍‍94.246.7.88‌. Time: 0ms. http://‌‍‍xxxxxxxxxxxxxxxxx/Sync/Data?X-Emby-Client=Emby for Windows&X-Emby-Device-Name=DESKTOP-FJ2LCGK&X-Emby-Device-Id=YimSvMKnUOdIKLVaLLVG8WX7nHpyxJuboW9uvglQBo&X-Emby-Client-Version=1.1.464.0&reqformat=json
2022-12-23 01:10:20.327 Info Server: Stopping HttpListener...
2022-12-23 01:10:20.331 Info Server: HttpListener stopped

Maybe enable debug logging would show more?

  • Like 1
Link to comment
Share on other sites

Q-Droid
2 hours ago, Happy2Play said:

Not really seeing anything in the log at the time it looks like it Gracefully shuts down, not a Crash.

2022-12-22 19:50:38.051 Info Server: http/1.1 Response 204 to ‌‍‍192.168.178.201‌. Time: 0ms. http://‌‍‍192.168.178.202‌:8097/Emby/Library/Refresh
2022-12-22 20:06:19.988 Info Server: Stopping HttpListener...
2022-12-22 20:06:19.992 Info Server: HttpListener stopped
2022-12-23 01:04:40.772 Info Server: http/1.0 Response 200 to ‌‍‍94.246.7.88‌. Time: 0ms. http://‌‍‍xxxxxxxxxxxxxxxxx/Sync/Data?X-Emby-Client=Emby for Windows&X-Emby-Device-Name=DESKTOP-FJ2LCGK&X-Emby-Device-Id=YimSvMKnUOdIKLVaLLVG8WX7nHpyxJuboW9uvglQBo&X-Emby-Client-Version=1.1.464.0&reqformat=json
2022-12-23 01:10:20.327 Info Server: Stopping HttpListener...
2022-12-23 01:10:20.331 Info Server: HttpListener stopped

Maybe enable debug logging would show more?

Right. The logs posted so far show Emby being shutdown, stopped, not crashed.  AFAIK Emby doesn't shut itself down so something on the host appears to be doing this. Without other logs from the host like syslog and logs from Docker (if separate) it's hard to know what might be stopping Emby.

 

  • Like 1
Link to comment
Share on other sites

Q-Droid

You also appear to be triggering library refreshes from a script or scheduled job. Any reason for this? If you fix RTM then shouldn't need to run manual or scheduled refresh.

Quote

embyserver-63807336382.txt:2022-12-22 16:15:00.918 Info Server: http/1.1 POST http://‌‍‍192.168.178.202‌:8097/Emby/Library/Refresh. UserAgent: curl/7.87.0
embyserver-63807336382.txt:2022-12-22 16:15:00.918 Info Server: http/1.1 POST http://‌‍‍192.168.178.202‌:8097/Emby/Library/Refresh. UserAgent: curl/7.87.0
embyserver-63807336382.txt:2022-12-22 17:15:00.169 Info Server: http/1.1 POST http://‌‍‍192.168.178.202‌:8097/Emby/Library/Refresh. UserAgent: curl/7.87.0
embyserver-63807336382.txt:2022-12-22 17:15:00.170 Info Server: http/1.1 POST http://‌‍‍192.168.178.202‌:8097/Emby/Library/Refresh. UserAgent: curl/7.87.0

 

Link to comment
Share on other sites

4 hours ago, Q-Droid said:

You also appear to be triggering library refreshes from a script or scheduled job. Any reason for this? If you fix RTM then shouldn't need to run manual or scheduled refresh.

 

Hi Q-Droid, this is because I sometimes add MP3 manually I downloaded. Then there is no trigger from a "download manager" and the library is not update. I need to trigger it by hand.

But you are right, it's nuts to trigger it scheduled every 15 minutes for the "5" mp3 I add in a week.

I killed the crontab entries.

Link to comment
Share on other sites

5 hours ago, Q-Droid said:

Right. The logs posted so far show Emby being shutdown, stopped, not crashed.  AFAIK Emby doesn't shut itself down so something on the host appears to be doing this. Without other logs from the host like syslog and logs from Docker (if separate) it's hard to know what might be stopping Emby.

 

Thanks for helping me out. I really appreciated this... I don't know how to express it other than here in the forum! THANKS!

 

The server "crashed" the NUC again last night. attached is the last logs it wrote.

The NUC is not shutdown, but just is unresponsive to connections (it's a headless one).

All other (not many) container (like my website) is also unresponsive.

The last three days when I had EMBY container complete shutdown, the NUC never up.

Within 3 hours of the EMBY container being up, NUC is unresponsive 

embyserver-63807776412.txt

Link to comment
Share on other sites

7 hours ago, Happy2Play said:

Not really seeing anything in the log at the time it looks like it Gracefully shuts down, not a Crash.

2022-12-22 19:50:38.051 Info Server: http/1.1 Response 204 to ‌‍‍192.168.178.201‌. Time: 0ms. http://‌‍‍192.168.178.202‌:8097/Emby/Library/Refresh
2022-12-22 20:06:19.988 Info Server: Stopping HttpListener...
2022-12-22 20:06:19.992 Info Server: HttpListener stopped
2022-12-23 01:04:40.772 Info Server: http/1.0 Response 200 to ‌‍‍94.246.7.88‌. Time: 0ms. http://‌‍‍xxxxxxxxxxxxxxxxx/Sync/Data?X-Emby-Client=Emby for Windows&X-Emby-Device-Name=DESKTOP-FJ2LCGK&X-Emby-Device-Id=YimSvMKnUOdIKLVaLLVG8WX7nHpyxJuboW9uvglQBo&X-Emby-Client-Version=1.1.464.0&reqformat=json
2022-12-23 01:10:20.327 Info Server: Stopping HttpListener...
2022-12-23 01:10:20.331 Info Server: HttpListener stopped

Maybe enable debug logging would show more?

Thansk you also for helping me out on this... This is so much appreciated!!!

I rebooted the NUC and applied "Q-Droid" changes... If it hangs again, I will switch on Debug, and upload here.!

Thank you, for your time so far!!

 

Link to comment
Share on other sites

Happy2Play

Something is gracefully shutting down Emby as shown in the log but hopefully debugging shows more info as currently I don't see any shutdown calls.

Spoiler

2022-12-27 22:15:57.466 Info HttpClient: GET https://api.themoviedb.org/3/search/movie?api_key=‌f6bd687ffa63cd282b6ff2c6877f2669‌&query=Woman King&language=nl&year=2022
2022-12-27 22:20:12.622 Info Server: Stopping HttpListener...
2022-12-27 22:20:12.626 Info Server: HttpListener stopped
2022-12-27 22:20:12.626 Info App: Disposing CoreAppHost
2022-12-27 22:20:12.626 Info App: Disposing LoopUtilEntryPoint
2022-12-27 22:20:12.626 Info App: Disposing SyncNotificationEntryPoint
2022-12-27 22:20:12.627 Info App: Disposing SyncManagerEntryPoint
2022-12-27 22:20:12.627 Info App: DisposeConnection
2022-12-27 22:20:12.627 Info App: Disposing ConnectEntryPoint
2022-12-27 22:20:12.627 Info App: Disposing Notifications
2022-12-27 22:20:12.628 Info App: Disposing EncodingManagerEntryPoint
2022-12-27 22:20:12.628 Info App: Disposing ActivityLogEntryPoint
2022-12-27 22:20:12.632 Info App: Disposing RecordingNotifier
2022-12-27 22:20:12.633 Info App: Disposing UpgradeChannelOptionsEntryPoint
2022-12-27 22:20:12.633 Info App: Disposing EntryPoint
2022-12-27 22:20:12.633 Info App: Disposing ChannelsEntryPoint
2022-12-27 22:20:12.633 Info App: Disposing UserDataChangeNotifier
2022-12-27 22:20:12.634 Info App: Disposing SystemEvents
2022-12-27 22:20:12.634 Info App: Disposing StartupWizard
2022-12-27 22:20:12.634 Info App: Disposing ServerEventNotifier
2022-12-27 22:20:12.635 Info App: Disposing LibraryChangedNotifier
2022-12-27 22:20:12.636 Info App: Disposing KeepServerAwake
2022-12-27 22:20:12.636 Info App: Disposing AutomaticRestartEntryPoint
2022-12-27 22:20:12.636 Info App: Disposing LibraryMonitorStartup
2022-12-27 22:20:12.636 Info App: Disposing DeviceAccessEntryPoint
2022-12-27 22:20:12.636 Info App: Disposing RemoteAddressEntryPoint
2022-12-27 22:20:12.636 Info App: Disposing UdpServerEntryPoint
2022-12-27 22:20:12.636 Info App: Disposing ApiEntryPoint
2022-12-27 22:20:12.637 Info App: Disposing EntryPoint
2022-12-27 22:20:12.637 Info App: Disposing DlnaEntryPoint
2022-12-27 22:20:12.637 Info Dlna: Disposing PlayToManager
2022-12-27 22:20:12.637 Info App: Disposing ServerEntryPoint
2022-12-27 22:20:12.637 Info App: Disposing EventMonitorEntryPoint
2022-12-27 22:20:12.637 Info App: Disposing IntrosEntryPoint
2022-12-27 22:20:12.638 Info App: Disposing PluginSecurityManager
2022-12-27 22:20:12.638 Info App: Disposing EntryPoint
2022-12-27 22:20:12.638 Info App: Disposing EntryPoint
2022-12-27 22:20:12.638 Info App: Disposing ConfigurationUpgradeEntryPoint
2022-12-27 22:20:12.638 Info App: Disposing NotificationManager
2022-12-27 22:20:12.639 Info App: Disposing ExternalPortForwarding
2022-12-27 22:20:12.639 Info App: Disposing StrmMounter
2022-12-27 22:20:12.639 Info App: Disposing BlurayMounter
2022-12-27 22:20:12.639 Info App: Disposing DvdMounter
2022-12-27 22:20:12.639 Info App: Disposing OpenSubtitleDownloader
2022-12-27 22:20:12.639 Info App: Disposing HauppaugeTunerWindows
2022-12-27 22:20:12.639 Info App: Disposing ActivityLogWebSocketListener
2022-12-27 22:20:12.640 Info App: Disposing SessionWebSocketListener
2022-12-27 22:20:12.640 Info App: Disposing ScheduledTasksWebSocketListener
2022-12-27 22:20:12.641 Info App: Disposing SessionInfoWebSocketListener
2022-12-27 22:20:12.641 Info App: Disposing SessionInfosWebSocketListener
2022-12-27 22:20:12.642 Info App: Disposing SessionEventsWebSocketListener
2022-12-27 22:20:12.642 Info App: Disposing EncodingManager
2022-12-27 22:20:12.643 Info App: Disposing ActivityRepository
2022-12-27 22:20:12.643 Info ActivityRepository: DisposeConnection
2022-12-27 22:20:12.643 Info ActivityRepository: PRAGMA analysis_limit=400;PRAGMA optimize
2022-12-27 22:20:12.643 Info ActivityRepository: Closing sqlite connection
2022-12-27 22:20:12.647 Info App: Disposing MediaEncoder
2022-12-27 22:20:12.647 Info App: Disposing SsdpDevicePublisher
2022-12-27 22:20:12.650 Info App: Disposing SsdpCommunicationsServer
2022-12-27 22:20:12.651 Info App: SsdpCommunicationsServer Disposing 4 sendSockets
2022-12-27 22:20:12.651 Info App: SsdpCommunicationsServer disposing sendSocket from 0.0.0.0:1900
2022-12-27 22:20:12.651 Info App: SsdpCommunicationsServer disposing sendSocket from 0.0.0.0:33440
2022-12-27 22:20:12.651 Info App: SsdpCommunicationsServer disposing sendSocket from 172.17.0.5:47426
2022-12-27 22:20:12.651 Info App: SsdpCommunicationsServer disposing sendSocket from 127.0.0.1:54322
2022-12-27 22:20:12.651 Info App: Disposing LiveTvManager
2022-12-27 22:20:12.651 Info App: Disposing SessionManager
2022-12-27 22:20:12.652 Info App: Disposing ProviderManager
2022-12-27 22:20:12.652 Info App: Disposing MediaSourceManager
2022-12-27 22:20:12.653 Info App: Disposing ImageProcessor
2022-12-27 22:20:12.653 Info App: Disposing ProcessManager
2022-12-27 22:20:12.654 Info App: Disposing HttpListenerHost
2022-12-27 22:20:12.654 Info Server: Stopping HttpListener...
2022-12-27 22:20:12.654 Info Server: HttpListener stopped
2022-12-27 22:20:12.654 Info App: Disposing LibraryMonitor
2022-12-27 22:20:12.654 Info App: Disposing AuthenticationRepository
2022-12-27 22:20:12.654 Info AuthenticationRepository: DisposeConnection
2022-12-27 22:20:12.654 Info AuthenticationRepository: PRAGMA analysis_limit=400;PRAGMA optimize
2022-12-27 22:20:12.654 Info AuthenticationRepository: Closing sqlite connection
2022-12-27 22:20:12.659 Info App: Disposing SqliteUserDataRepository
2022-12-27 22:20:12.659 Info SqliteUserDataRepository: DisposeConnection
2022-12-27 22:20:12.659 Info App: Disposing SqliteItemRepository
2022-12-27 22:20:12.659 Info SqliteItemRepository: DisposeConnection
2022-12-27 22:20:12.659 Info SqliteItemRepository: PRAGMA analysis_limit=400;PRAGMA optimize
2022-12-27 22:20:12.662 Info SqliteItemRepository: Closing sqlite connection
2022-12-27 22:20:12.670 Info App: Disposing SqliteDisplayPreferencesRepository
2022-12-27 22:20:12.670 Info SqliteDisplayPreferencesRepository: DisposeConnection
2022-12-27 22:20:12.670 Info SqliteDisplayPreferencesRepository: PRAGMA analysis_limit=400;PRAGMA optimize
2022-12-27 22:20:12.671 Info SqliteDisplayPreferencesRepository: Closing sqlite connection
2022-12-27 22:20:12.671 Info App: Disposing SqliteUserRepository
2022-12-27 22:20:12.671 Info SqliteUserRepository: DisposeConnection
2022-12-27 22:20:12.671 Info SqliteUserRepository: PRAGMA analysis_limit=400;PRAGMA optimize
2022-12-27 22:20:12.671 Info SqliteUserRepository: Closing sqlite connection
2022-12-27 22:20:12.674 Info App: Disposing InstallationManager
2022-12-27 22:20:12.675 Info App: Disposing TaskManager
2022-12-27 22:20:12.676 Info TaskManager: Scan media library: Cancelling
2022-12-27 22:20:12.676 Info App: Disposing MediaMountManager
2022-12-27 22:20:12.721 Info Main: Shutdown complete
 

 

Link to comment
Share on other sites

1 minute ago, Happy2Play said:

Something is gracefully shutting down Emby as shown in the log but hopefully debugging shows more info as currently I don't see any shutdown calls.

  Reveal hidden contents

2022-12-27 22:15:57.466 Info HttpClient: GET https://api.themoviedb.org/3/search/movie?api_key=‌f6bd687ffa63cd282b6ff2c6877f2669‌&query=Woman King&language=nl&year=2022
2022-12-27 22:20:12.622 Info Server: Stopping HttpListener...
2022-12-27 22:20:12.626 Info Server: HttpListener stopped
2022-12-27 22:20:12.626 Info App: Disposing CoreAppHost
2022-12-27 22:20:12.626 Info App: Disposing LoopUtilEntryPoint
2022-12-27 22:20:12.626 Info App: Disposing SyncNotificationEntryPoint
2022-12-27 22:20:12.627 Info App: Disposing SyncManagerEntryPoint
2022-12-27 22:20:12.627 Info App: DisposeConnection
2022-12-27 22:20:12.627 Info App: Disposing ConnectEntryPoint
2022-12-27 22:20:12.627 Info App: Disposing Notifications
2022-12-27 22:20:12.628 Info App: Disposing EncodingManagerEntryPoint
2022-12-27 22:20:12.628 Info App: Disposing ActivityLogEntryPoint
2022-12-27 22:20:12.632 Info App: Disposing RecordingNotifier
2022-12-27 22:20:12.633 Info App: Disposing UpgradeChannelOptionsEntryPoint
2022-12-27 22:20:12.633 Info App: Disposing EntryPoint
2022-12-27 22:20:12.633 Info App: Disposing ChannelsEntryPoint
2022-12-27 22:20:12.633 Info App: Disposing UserDataChangeNotifier
2022-12-27 22:20:12.634 Info App: Disposing SystemEvents
2022-12-27 22:20:12.634 Info App: Disposing StartupWizard
2022-12-27 22:20:12.634 Info App: Disposing ServerEventNotifier
2022-12-27 22:20:12.635 Info App: Disposing LibraryChangedNotifier
2022-12-27 22:20:12.636 Info App: Disposing KeepServerAwake
2022-12-27 22:20:12.636 Info App: Disposing AutomaticRestartEntryPoint
2022-12-27 22:20:12.636 Info App: Disposing LibraryMonitorStartup
2022-12-27 22:20:12.636 Info App: Disposing DeviceAccessEntryPoint
2022-12-27 22:20:12.636 Info App: Disposing RemoteAddressEntryPoint
2022-12-27 22:20:12.636 Info App: Disposing UdpServerEntryPoint
2022-12-27 22:20:12.636 Info App: Disposing ApiEntryPoint
2022-12-27 22:20:12.637 Info App: Disposing EntryPoint
2022-12-27 22:20:12.637 Info App: Disposing DlnaEntryPoint
2022-12-27 22:20:12.637 Info Dlna: Disposing PlayToManager
2022-12-27 22:20:12.637 Info App: Disposing ServerEntryPoint
2022-12-27 22:20:12.637 Info App: Disposing EventMonitorEntryPoint
2022-12-27 22:20:12.637 Info App: Disposing IntrosEntryPoint
2022-12-27 22:20:12.638 Info App: Disposing PluginSecurityManager
2022-12-27 22:20:12.638 Info App: Disposing EntryPoint
2022-12-27 22:20:12.638 Info App: Disposing EntryPoint
2022-12-27 22:20:12.638 Info App: Disposing ConfigurationUpgradeEntryPoint
2022-12-27 22:20:12.638 Info App: Disposing NotificationManager
2022-12-27 22:20:12.639 Info App: Disposing ExternalPortForwarding
2022-12-27 22:20:12.639 Info App: Disposing StrmMounter
2022-12-27 22:20:12.639 Info App: Disposing BlurayMounter
2022-12-27 22:20:12.639 Info App: Disposing DvdMounter
2022-12-27 22:20:12.639 Info App: Disposing OpenSubtitleDownloader
2022-12-27 22:20:12.639 Info App: Disposing HauppaugeTunerWindows
2022-12-27 22:20:12.639 Info App: Disposing ActivityLogWebSocketListener
2022-12-27 22:20:12.640 Info App: Disposing SessionWebSocketListener
2022-12-27 22:20:12.640 Info App: Disposing ScheduledTasksWebSocketListener
2022-12-27 22:20:12.641 Info App: Disposing SessionInfoWebSocketListener
2022-12-27 22:20:12.641 Info App: Disposing SessionInfosWebSocketListener
2022-12-27 22:20:12.642 Info App: Disposing SessionEventsWebSocketListener
2022-12-27 22:20:12.642 Info App: Disposing EncodingManager
2022-12-27 22:20:12.643 Info App: Disposing ActivityRepository
2022-12-27 22:20:12.643 Info ActivityRepository: DisposeConnection
2022-12-27 22:20:12.643 Info ActivityRepository: PRAGMA analysis_limit=400;PRAGMA optimize
2022-12-27 22:20:12.643 Info ActivityRepository: Closing sqlite connection
2022-12-27 22:20:12.647 Info App: Disposing MediaEncoder
2022-12-27 22:20:12.647 Info App: Disposing SsdpDevicePublisher
2022-12-27 22:20:12.650 Info App: Disposing SsdpCommunicationsServer
2022-12-27 22:20:12.651 Info App: SsdpCommunicationsServer Disposing 4 sendSockets
2022-12-27 22:20:12.651 Info App: SsdpCommunicationsServer disposing sendSocket from 0.0.0.0:1900
2022-12-27 22:20:12.651 Info App: SsdpCommunicationsServer disposing sendSocket from 0.0.0.0:33440
2022-12-27 22:20:12.651 Info App: SsdpCommunicationsServer disposing sendSocket from 172.17.0.5:47426
2022-12-27 22:20:12.651 Info App: SsdpCommunicationsServer disposing sendSocket from 127.0.0.1:54322
2022-12-27 22:20:12.651 Info App: Disposing LiveTvManager
2022-12-27 22:20:12.651 Info App: Disposing SessionManager
2022-12-27 22:20:12.652 Info App: Disposing ProviderManager
2022-12-27 22:20:12.652 Info App: Disposing MediaSourceManager
2022-12-27 22:20:12.653 Info App: Disposing ImageProcessor
2022-12-27 22:20:12.653 Info App: Disposing ProcessManager
2022-12-27 22:20:12.654 Info App: Disposing HttpListenerHost
2022-12-27 22:20:12.654 Info Server: Stopping HttpListener...
2022-12-27 22:20:12.654 Info Server: HttpListener stopped
2022-12-27 22:20:12.654 Info App: Disposing LibraryMonitor
2022-12-27 22:20:12.654 Info App: Disposing AuthenticationRepository
2022-12-27 22:20:12.654 Info AuthenticationRepository: DisposeConnection
2022-12-27 22:20:12.654 Info AuthenticationRepository: PRAGMA analysis_limit=400;PRAGMA optimize
2022-12-27 22:20:12.654 Info AuthenticationRepository: Closing sqlite connection
2022-12-27 22:20:12.659 Info App: Disposing SqliteUserDataRepository
2022-12-27 22:20:12.659 Info SqliteUserDataRepository: DisposeConnection
2022-12-27 22:20:12.659 Info App: Disposing SqliteItemRepository
2022-12-27 22:20:12.659 Info SqliteItemRepository: DisposeConnection
2022-12-27 22:20:12.659 Info SqliteItemRepository: PRAGMA analysis_limit=400;PRAGMA optimize
2022-12-27 22:20:12.662 Info SqliteItemRepository: Closing sqlite connection
2022-12-27 22:20:12.670 Info App: Disposing SqliteDisplayPreferencesRepository
2022-12-27 22:20:12.670 Info SqliteDisplayPreferencesRepository: DisposeConnection
2022-12-27 22:20:12.670 Info SqliteDisplayPreferencesRepository: PRAGMA analysis_limit=400;PRAGMA optimize
2022-12-27 22:20:12.671 Info SqliteDisplayPreferencesRepository: Closing sqlite connection
2022-12-27 22:20:12.671 Info App: Disposing SqliteUserRepository
2022-12-27 22:20:12.671 Info SqliteUserRepository: DisposeConnection
2022-12-27 22:20:12.671 Info SqliteUserRepository: PRAGMA analysis_limit=400;PRAGMA optimize
2022-12-27 22:20:12.671 Info SqliteUserRepository: Closing sqlite connection
2022-12-27 22:20:12.674 Info App: Disposing InstallationManager
2022-12-27 22:20:12.675 Info App: Disposing TaskManager
2022-12-27 22:20:12.676 Info TaskManager: Scan media library: Cancelling
2022-12-27 22:20:12.676 Info App: Disposing MediaMountManager
2022-12-27 22:20:12.721 Info Main: Shutdown complete
 

 

I changed 3 things:

1. Debug is switched on

2. Stopped triggering scan every 15 min

3. changed to the BETA docker image of EMBY

 

Still no crash, till now..... (don't push your luck now, Marco 😉

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...