-
Posts
28674 -
Joined
-
Last visited
-
Days Won
314
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by Squid
-
-
Reason for not available would be that it failed to be able to check the current versions from GitHub. Try setting static DNS addresses in Network Settings, DNS Servers. #1: 208.67.222.222 and #2: 208.67.220.220 and see if that makes a difference.
-
Retest next (post 6.12.8) OS release
-
Changed Status to Solved
-
28 minutes ago, JonathanM said:
update loop
Hit check for updates multiple times without ever navigating away from the page. Or do pretty much anything on the page without navigating away, and when you finally hit Update All, then you'll get an "update" issued for the same containers. Number of times the "update" happens equals number of times you did something on that page.
Kudos to @HastyBacon for figuring out the steps to replicate so the one-line fix can be implemented
-
Just waiting for some updates to test my fix
-
You are correct. That page isn't considering that you would hit update all after removing a container without reloading the page.
IE: Simple workaround is to reload the page before hitting update all if you've deleted something, but yes you found a bug
- 1
-
So everything works though if you boot in one of the NON GUI modes and you access via another computer? (this is how 99.9% of the times you would manage the system. Fundamentally, GUI mode is there if your daily driver you use is a VM on the Unraid Server itself.
Curious if when booting via the non-gui mode after you log in at the prompt and then enter in the command
slim
if the GUI comes up.
-
Instead of using your router as your DNS servers, setup DNS #1 and #2 with a dedicated DNS server. Use 208.67.222.222 and 208.67.220.220 (OpenDNS servers)
-
Changed Status to Solved
- 1
-
-
2 hours ago, wgstarks said:
Would an FCP warning be possible?
In my case I ran into this problem with the LSIO Plex docker. IIRC the template was originally setup with users adding their own paths for movies, tv shows etc but at some point LSIO added these paths to the template. Since I (and others) already had these paths as host path 2, host path 3 etc the newly added paths were never used and that worked just fine until 6.12.8. It was an easy fix after the update since someone else had already found the fix and posted it in that support thread but I think an FCP warning might help people who unknowingly have this problem prior to them updating to 6.12.8. Just a thought.
A quick patch plugin will be done shortly. FCP will warn if the plugin isn't there.
This isn't fixing any bug but rather changing the behaviour. If there is a bug per se then it's with previous versions of docker
- 1
-
-
8 minutes ago, ich777 said:
After a little bit of back and forth with @sonic6 I think this is simply a bad Docker template either the maintainer has to fill out a path by default for the host and container or he has to fill out the container path and mark the path as required so the user is forced to fill in the path or delete the path.
That‘s my opinion on that.
OK. What I'll do then is have CA adjust every template on 6.12.8+ to have the paths as required..
- 1
-
6 minutes ago, JonathanM said:
I don't think 6.12.6 would have accepted it either.
6.12.6 fails silently in this circumstance (incorrect behavior) Tested it all and I can get this via the GUI no problems.
-
Changed Status to Retest
-
Why would you want to have a container path that isn't mapped to a host path?
The docker executables let that slide without an error on 6.12.6 and do indeed return an error on 6.12.8. And the error is correct. Docker silently failed on .6 as it wouldn't create any container path. Now they're calling it an error instead of silently failing.
There is a bug here, but it's not that the path is empty. Rather that on editing or creating a container and adding a new path without a host path that you can apply without having it filled out unlike installing a new template with an empty path where it forces you to enter something before you can apply.
-
23 hours ago, mattalat said:
I tried time machine like a year ago and couldn't get it to work - excited to see if this allows it to function again!
I can't get TM to fail under 6.12.7. Been trying hard for the last month with no success
- 2
-
Enable the syslog server (mirror to flash) and after the next crash post a new set of diagnostics and the syslog that was saved in /logs on the flash drive
-
First things you should always do in any situation like this is run Memtest from the boot menu for at least a couple of passes.
To roll back though, all you have to do would be to download the appropriate .zip file from https://unraid.net/download
Shutdown the server, pull out the flash and replace all of the bz* files in the root of the flash drive with those in the archive. Power back up.
Alternatively you can also create a folder on the flash drive named "previous" and put all of the files in the root of the archive into that folder and then Update OS will offer you a rollback option
-
On 11/24/2023 at 11:51 AM, murkus said:
Due to this this bug is actually urgent, not minor.
1 - We always need diagnostics (preferably grabbed while this is happening)
2 - If anyone in a position to fix the problem could ever replicate it, then it would be fixed.
-
Changed Status to Closed
-
Quote
Delete docker vdisk/folder.
That makes sense that you're seeing what you're seeing. The autostart and startup order is all stored within the docker image. IE: expected results.
-
Changed Status to Closed
-
docker.folder.plg - 2021.08.20 (Up to date) (Incompatible)
Docker folder is no compatible and you need to uninstall it and install Folder View instead
[6.12.9] - Parity Check trigged twice end of March
in Stable Releases
Posted
You'd have to post your diagnostics and a screenshot of your parity schedule settings