May 4, 20251 yr Odd issue has started to become a reoccurring one... every f or so days my docker apps stoip responding. Some docker apps seems to keep running while most stop. The docker page only shows "docker is not running" and none of the apps showing. I end up having to reboot to fix. not sure what could have caused this. Currently on unraid 7.0 (however just updated to RC4 and rebooting as I am typing this) intel 14600k 64gbram (will be swapping in my 96GB kit back in tonight or tomorrow) Asus Pro Art Z790 motherboard HBA with bunch off HDD and m.2 Please let me know if there is any other info needed. Thank you diag.zip
May 4, 20251 yr Community Expert Why do you have 120G docker.img. Have you had problems filling it? The usual cause of filling docker.img is an application writing to a path that isn't mapped. Apr 28 05:30:05 Rocket1 root: Fix Common Problems: Error: Invalid folder cache contained within /mnt You must have renamed a pool, and didn't update all paths to the old name. Check your docker volume mappings.
May 4, 20251 yr Author 40 minutes ago, trurl said: Why do you have 120G docker.img. Have you had problems filling it? The usual cause of filling docker.img is an application writing to a path that isn't mapped. Apr 28 05:30:05 Rocket1 root: Fix Common Problems: Error: Invalid folder cache contained within /mnt You must have renamed a pool, and didn't update all paths to the old name. Check your docker volume mappings. Because I was running Ollama and a couple other large images that needed the space, I never reclaimed it. figured to just leave it be. I do not have any apps writing any data there. I will have to double check to see if one is setup that way... checking...
May 8, 20251 yr Community Expert Did it happen right before the diags were created? I'm not seeing anything relevant logged.
May 10, 20251 yr Author On 5/8/2025 at 4:06 AM, JorgeB said: Did it happen right before the diags were created? I'm not seeing anything relevant logged. The event was before I pulled the logs. I just dont remember if I pulled logs then rebooted, or rebooted first then pulled logs. but the event was before the log was generated. I will update when it happens again with a new log the next time. I will grab some screen shots of what I see too. TY! Edited May 10, 20251 yr by KooKoo102
May 10, 20251 yr Author On 5/8/2025 at 4:06 AM, JorgeB said: Did it happen right before the diags were created? I'm not seeing anything relevant logged. Well... just happened... rebooted and waiting for diag data to download...
May 10, 20251 yr Community Expert There's nothing relevant logged, last thing logged about docker was the trim: May 9 06:00:05 Rocket1 root: /var/lib/docker: 11.1 GiB (11940425728 bytes) trimmed on /dev/loop2 May 9 06:00:08 Rocket1 root: /var/lib/docker/btrfs: 11.1 GiB (11955826688 bytes) trimmed on /dev/loop2[/btrfs] Did you use a docker folder before?
May 10, 20251 yr Author 1 hour ago, JorgeB said: There's nothing relevant logged, last thing logged about docker was the trim: May 9 06:00:05 Rocket1 root: /var/lib/docker: 11.1 GiB (11940425728 bytes) trimmed on /dev/loop2 May 9 06:00:08 Rocket1 root: /var/lib/docker/btrfs: 11.1 GiB (11955826688 bytes) trimmed on /dev/loop2[/btrfs] Did you use a docker folder before? Really odd nothing is showing in the log. Not sure what you mean by use a docker folder? Do you mean before it locked up and the docker system "turned off"? if thats what you are asking, no... i was actually playing a game on my PC... not doing anything with my Unraid server. only found out because I got a notification on my phone that lead me to check and sure enough, Docker was "off"
May 10, 20251 yr Community Expert 2 hours ago, KooKoo102 said: Not sure what you mean by use a docker folder? Docker can be set as an image or a folder (Settings - Docker settings), you are currently using an image, but looked like you used a directly before, not that is necessarily a problem, just curious, and looking again at the log, seems like I misread that. Do you know the time it happened, just to make sure it was covered by the syslog-previous?
May 11, 20251 yr Author On 5/10/2025 at 7:18 AM, JorgeB said: Docker can be set as an image or a folder (Settings - Docker settings), you are currently using an image, but looked like you used a directly before, not that is necessarily a problem, just curious, and looking again at the log, seems like I misread that. Do you know the time it happened, just to make sure it was covered by the syslog-previous? Oh ok, I understand now. I never had it setup as a folder, only as an image. I have seen information on that, but never seen the Need to do so. either way... its in the "normal" setup in that regard. I believe it was right about 9pm. it happened and I rebooted within 5 min of noticing it was down, then pulled the log about 10 min after it rebooted.
May 12, 20251 yr Community Expert Last log entry is from 4pm May 9 16:00:02 Rocket1 sshd-session[2107723]: pam_unix(sshd:session): session closed for user root May 9 16:00:02 Rocket1 elogind-daemon[2034]: Removed session 181.
May 12, 20251 yr Community Expert You can enable the syslog server and post that after is happens again, in case there's something more logged.
May 13, 20251 yr Author Awesome, Done... system has been up for 2.5 days so far, however new stable version is out... might just wait till it dumps docker again and then I run the update. so another 2.5+ days and should hopefully have more logs. TY!
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.