Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid V6.12.6 Crashes when more than One Docker Container Starts

Featured Replies

My Unraid server crashed yesterday where I had to give it a hard restart.  Upon restarting my array couldn't be brought up because it couldn't find my third disk.  I initially thought it was a bad hard drive as these things happen, but since it was my newest hard drive and the only one on the LSI expansion card, I plugged the hard drive directly into a sata port on the motherboard.  When powering on, Unraid saw it right away and started the array.  I thought problem solved, hardware issue, not so fast.

 

When starting my docker containers back up, I would loose network connectivity to the server after a couple of minutes.  I couldn't ping the server, I couldn't access the web ui (what I consider a 'crash'), so I was forced to manually cycle power on the server to re-enable connectivity.  I tried following this thread as it seemed to be a similar issue but changing my custom docker network from macvlan to ipvlan did not solve the issue.

 

Debugging I have Tried

  • Start Unraid without docker started - does not crash after 30 minutes
  • Start Unraid with docker and no containers - does not crash after 30 minutes
  • Start Unraid with docker and only one container running (NGINXProxyManager) - does not crash after 30 minutes
  • Start Unraid with docker and only one container running (NGINXProxyManager) and update other non-running containers - crashes
  • Start Unraid with docker and only one container running (NGINXProxyManager) and start up secondary container - crashes
  • Delete and reinstall docker image and containers - crashes when reinstalling containers
  • Enable Syslog to write to disk - nothing useful during crash (that I can see)

 

I am going crazy trying to figure this out, please let me know if there is anything further I can provide to have someone help assist me.

 

illesserver-diagnostics-20231230-1636.zip

syslog-192.168.0.180.log

Edited by jtilles
Added Syslog

  • Community Expert
23 minutes ago, jtilles said:

Enable Syslog to write to disk - nothing useful during crash (that I can see)

Post it, the syslogs in your diagnostics don't have much except bootup.

  • Author
27 minutes ago, trurl said:

Post it, the syslogs in your diagnostics don't have much except bootup.

Added to the original post, thanks for the assistance @trurl

  • Community Expert

Have you done memtest?

  • Author

I have not, do you recommend it?  My hardware configuration hasn't been touched in over 3 years, do you think the memory could have gone bad?  How long do you suggest to run the test for?

Edited by jtilles

  • Community Expert

If only to eliminate that as a possibility.

 

Since you have ECC usually you would see something logged.

 

Memtest in the Unraid boot menu won't work with ECC, you would have to go to memtest86.com

Does the unradUi is getting slow after you start a container ?

My problem is a bit similar

  • Author

@Danuel, not really.  I'll see the cores spiking when they first start a container, but nothing out of the ordinary.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.