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.

Unclean shutdowns happen about 60-80% of the time when starting containers

Featured Replies

A lot of the time when I'm starting up containers, - I don't have exact stats but it happens often enough to certainly notice and be troublesome and I'm unable to determine if it's when I'm starting many at once or even just one at a time as it's happened in both scenarios - my system will unexpectedly shut down. When it starts back up it says it detected an unclean shutdown. The syslogs never seem to indicate anything. I've turned on saving the syslog across boots and can't see anything in there. I recently created a script to stop containers and restart them after rsyncing the appdata directory to back them up, but the first night it ran, last night, it did the same thing and shutdown the server even though in a test during the day it worked fine.

So this doesn't happen every time containers are started but so far it has only ever happened while starting containers; never during any other normal operation or when containers are already started and running just fine.


Attached is the diagnostics, please let me know if I can provide anything else helpful in debugging this.

turkeysunite-diagnostics-20251015-0640.zip

Edited by kamcknig

  • kamcknig changed the title to Unclean shutdowns happen about 60-80% of the time when starting containers
  • Author

It actually just occurred again as I was bringing them up after the last shutdown. I brought up a compose project with eight containers in it, and then individually started my single containers one at a time, waiting for each to finish starting before trying the next, and on the fifth one it shutdown again.

Attached is another diagnostics

turkeysunite-diagnostics-20251015-0659.zip

  • Community Expert

Do you mean the actual server shuts down/reboots by itself?

  • Author

Do you mean the actual server shuts down/reboots by itself?

That's correct, it just powers off and I have to go manually press the power button to get it back on.

  • Community Expert

That is almost always a hardware issue, like an overheating CPU, bad PSU, RAM, etc.

  • Community Expert

You can try running some kind of torture test, can be with another OS.

  • Author

You can try running some kind of torture test, can be with another OS.

Thanks, I'll look into some options.

  • Author

Tests seem to come back fine. Read some random articles about macvlan and ipvlan but I switched over to ipvlan and still get the same results there as well.

  • Community Expert

macvlan hasn't been an issue since 6.12.11, and it would not make the server restart anyway; restarts are almost always hardware related.

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.