Squid

So the error is from a plugin. OTOH network stats since it didn't show back up. Probably harmless and can be ignored though.

Reboot in safe mode

Does a scan with Fix Common Problems tell you anything?

Changed Status to Closed

I just did the same thing and also saw that it's not the issue. But, FCP is adding it as a warning as it is contradictory. The GUI does disable the include / exclude settings from being modified when its set to be Only, but it should also IMO clear the settings also Just noticed that my server is now also showing exists on no drives, so will investigate the diagnostics issue.

re: https://forums.unraid.net/topic/129150-drives-dont-spin-down/?do=findComment&comment=1176393 Could this be the issue: shareInclude="disk1,disk2" shareUseCache="only" Setting an Include (or an exclude) on a share that is a cache only share... Technically it is set incorrectly as there shouldn't be any include / exclude on a cache only share. Time for a new FCP test?

As of late, @ich777 and myself have noticed a fair amount of overuse of maintainers setting the Privileged flag on. Privileged effectively gives root access to your server and should only be enabled if the container actually requires it. CA in the side bar will display a warning if Privileged is set and if installing directly from the card, the following will appear Because there are certain containers which do require Privileged to be set, to have CA not display this message then you would add into the XML <PrivilegedReq>true</PrivilegedReq>

The error is being returned by docker itself because it's not supporting that and is unfortunately out of the OS's hands. The container being deleted (actually orphaned) is normal and expected since the docker run command is invalid and because it's invalid the container doesn't actually exist anymore. Once again how docker works and by design.

Settings - Docker with the service disabled

@dlandon?

There should be no problem jumping all the way forward. Before upgrading though, just make a copy of /config on the flash drive (along with all of the bz* files) You will most likely have to do a manual upgrade. Download the zip from https://unraid.net/download and extract all of the bz* files in the archive to the flash drive and then reboot

Try this 0 0 * * 1 [[ $(date +%e) -le 7 ]] && First Monday of every month at midnight

Wed will not work (slackware does not support that) For the others, there should be no problems. Post the output of cat /etc/cron.d/root

All attached drives (excluding optical media and the boot flash drive) count towards the counts on a license. You will need a Plus license

Undo whatever changes / mods you're making via User Scripts or the go file and reboot.

Best place for support on all LSIO containers is via their Discord. Click on the app and select Discord in the drop down

You best bet would be to do a general google search on switching from MySQL to MariaDB. Rather surprising to me though they're suggesting switching as MySQL is the gold standard and MariaDB is a fork that is nearly completely compatible.

You'll really need to post your diagnostics so that the persons who are most capable to help have something to go on.

That was also part of it and is fixed given the steps above

Postgresql fixed via the application feed. The template as it is had a weird repository reference registry.hub.docker.com/library/postgresql:14 instead of the usual way of simply saying either postgresql:14 or library/postgresql:14 The "fix" on your side would be to take note of all of the paths / variables you have on your existing template via the docker tab, then uninstall on the docker tab, go to Previous Apps and delete the one that probably shows up there and finally reinstall postgresql14 and change the variable settings etc.

Thanks. Will get fixed on next release

It's still usable and works. If you've had it previously installed it will show up in Previous Apps. If you haven't had it installed in Settings enable show deprecated apps

@NLS Re: #2 If you don't have a template for them (ie installed from the command line instead of Add Container) then CA will not display them. Re: #1 CA actually uses the identical routines as the docker tab, so without what the error was I'm nilot sure

Not really. (Although I had this morning CA go to a blank page when I tried to download it's diagnostics, which has never happened before (download code is the same as flash backup) - But nothing similar was logged)

Did you change anything since updating CA? (It was up to date). If CA was able to be updated, then there shouldn't be any issues with it downloading the feed. And you did ping github from the OS, not another system?