Hello all,

 

I am using the Appdata Backup plugin for quite a while now and never had problems. That changed last night.

 

In the morning I noticed that all containers were not running. I checked the GUI and did not see any Docker containers at all. But Docker was running. I stopped it through settings ("Enable Docker" to No, then Apply) and then enabled it again. On the Docker page I saw "Status: Running" but still no containers. Retried, no change. In syslog I saw something that no memory is left so I stopped two VMs and then also with 20% memory usage I still got the same error. So I rebooted the Unraid machine and everything came back online. The problem is that I also had to bring down the VMs (one of them is OPNsense and another Pi-hole, so no Internet...) and also rebooting and having everything back running takes some time. So that's quite a deal.

 

As everything went offline at 3pm it looked to me already from the beginning of my investigation that it must be the weekly Appdata Backup which starts at 3am on Monday mornings. And yes, the log tells me that as well. The backup itself was okay, but then not all containers were started and it took a long time (one time over one hour) from one container start to the next which failed. I attached the log here. I also got a mail from Appdata Backup that something failed and that I need to check debug log. As I already rebooted (had to get out of the house to work and the services back online...) I do not see any logs anymore and I am also not sure if debug logging is enabled for Appdata Backup, I guess, it's not. I did not find debug in the plugin settings.

 

Anyway, I installed some more Docker containers last week, so something changed here. And I also have lots of data inside these containers for backup, e.g. 5GB+ of zstd compressed MariaDB data.

 

Do I need to adjust some settings? I never did for the Docker Engine. But is that really Docker as all containers get stopped before backup (I set it that way) and started again after backup?

 

Any ideas?

 

I'm glad to bring more data, I would also run a backup again and check debug first before rebooting. At the moment I hope for something simple, maybe a user problem with some setting I should have changed because of more containers, load or whatever.

 

Thanks.

backup.log

Edited February 3, 20251 yr by Roi
App Backup -> Appdata Backup

Recommend posting in the existing plugin support thread.

Thank you, okay, I will. But as the plugin only stops and starts the containers, it might not be plugin related. That was the reason I posted it here.

Then you should post the diagnostics, the plugin log is only useful for troubleshooting the plugin.

4 hours ago, JorgeB said:

Then you should post the diagnostics, the plugin log is only useful for troubleshooting the plugin.

Okay, here are the diagnostics. But it's from after the reboot. Not much sense in it? Or does it bring up information?

 

I am willing to try again, if this is not useful and then I can get diagnostics before rebooting.

sol-diagnostics-20250203-2200.zip

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications

6 minutes ago, trurl said:

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications

Thank you. Are you guessing because of what I described or do the diagnostics point to this?

Easy enough to try to see if it fixes.

Also

https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

15 hours ago, trurl said:

Easy enough to try to see if it fixes.

 

Thank you. I re-created the Docker image file in the morning and made it bigger (20 to 40GB). I do not have any custom networks for Docker, so no todo for me here.

 

Will try the Appdata backup maybe tomorrow morning and see what's happening.