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.

Frequent crashing on 6.9.2

Featured Replies

I recently decided to upgrade from 6.8.3 to 6.9.2. I first attempted this a couple weeks back, and immediately noticed some pretty severe stability issues. I'd typically end up rebooting my system for one reason or another, but it wasn't uncommon to have uptimes of several months. After upgrade, my server would typically crash within 12-24h. The symptoms would often first manifest as inability to load docker or VM tabs in the web interface, up to loss of the web interface itself. Typically I could still ping the server, though not in every case. At the time, I thought it might be related to a mining VM I was running on my 1080ti. (I thought possibly the card might be going bad.) Eventually, I rolled back to 6.8.3, and the stability issues disappeared. Recently I removed that video card to a separated machine (where it's been rock-solid, fwiw), and decided last night to attempt moving back to 6.9.2 again. The same thing is happening - I think I got about 12-14h of uptime before the system crashed.

 

I could roll back to 6.8.3 again, but if it's possible to figure out the issue that would be great. I've attached a diagnostic. Any help that might be provided is appreciated. Thanks!

unraid-diagnostics-20210422-0928.zip

  • Author
3 hours ago, JorgeB said:

Macvlan call traces are usually the result of having dockers with a custom IP address, more info below.

 

https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/

Thanks for the response! Is there something in the diagnostics that's indicating this might be the cause of the crashing? 

 

I read through that thread, and I'm also using a pihole docker, so I'll disable that for the time being. (Pretty sure that's my only one with a mapped IP.) I feel like I might've read that 6.9 modified how some of the docker networking works - is there a better way I might map an IP onto a container now? 

Edited by supagold

  • Community Expert
11 hours ago, supagold said:

Is there something in the diagnostics that's indicating this might be the cause of the crashing? 

There are Macvlan call traces

 

Hi there,

 

Let's try booting 6.9.2 in safe mode and disable all docker containers for the time being.  See if that works.  If so, start turning containers on one at a time, giving ample time for the issue to occur in between, until you've been able to reproduce the issue.  Then we can look more specifically at that container to see what's wrong.  If none of them give you an issue, it may be an issue with a plugin.  Either way, we need to step through the troubleshooting to figure out what's causing your problem.

  • Author
On 4/26/2021 at 3:07 PM, jonp said:

Hi there,

 

Let's try booting 6.9.2 in safe mode and disable all docker containers for the time being.  See if that works.  If so, start turning containers on one at a time, giving ample time for the issue to occur in between, until you've been able to reproduce the issue.  Then we can look more specifically at that container to see what's wrong.  If none of them give you an issue, it may be an issue with a plugin.  Either way, we need to step through the troubleshooting to figure out what's causing your problem.

Thanks for the followup. I have narrowed it down to either my pihole or unifi dockers, which are the only ones that have an assigned IP. The other dockers are currently up and running with normal stability. This does seem to match the thread that JorgeB reference, the difference is that it looks like those people were adding new hardware, where mine is existing hardware that's perfectly stable under 6.8.x and only shows issues with 6.9. 

  • 1 month later...

I have the exact problem. 6.8.3 was absolut stabel for a year now. Not a single crash. Now I updated to 6.9.2. and have also crashes every day. 

I also use PiHole as a docker container. 

  • 1 month later...

Is there any update on this topic? I also run pihole on a custom IP in docker and I am running 6.8.3 right now and thankfully search google for issues with 6.9.2, so I haven't upgraded yet. I would like to upgrade though. Thanks.

Archived

This topic is now archived and is closed to further replies.

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.