Squid

All repos

As you noted, all the apps are separate from the OS and Limetech themselves offer no support etc for them. (Ignoring plugins which are a different beast). But it's really no different than say Windows (another paid OS) supporting any random program within their own forums (or running the same docker container under Windows) But one thing to actually consider is that 99% of any given issues with any random app isn't an issue with the container itself, but rather with the actual application. All set up guides, internal settings etc are basically the responsibility of the actual program author, not the template maintainer / container author. All that being said, @alturismo does seem to do a good job of supporting his templates (along with every one else) It's for this reason that there is usually a "Project" link on most applications -> to directly take you to the appropriate Project. Can't comment on this particular app specifically, but it is unrealistic for these forums to properly support, provide set up guides etc for the applications when the particular project already does that and it is ultimately their responsibility in the first place to do so. All that being said, the Apps tab does have provisions for Guides / Videos / Screenshots etc to make things easier for the end-user. Additionally, @SpaceInvaderOne, @Sycotix and more have dedicated videos to both understanding how docker works in the first place and also providing set up guides for certain key applications. Your "officially approved" apps idea has come up before has been implemented in the past with mixed results, and is now no longer done (with the exception of a select number of plugins).

You're correct. Thanks.

That seems to imply it's the weekly schedule. You sure there's nothing running via user scripts (if installed) Install Dynamix Schedules and then look at Settings - Schedules - Fixed Schedules or ls /etc/cron.weekly

This thread is to be used to provide feedback, suggestions etc to anything within the More Information Thread (https://forums.unraid.net/topic/120220-fix-common-problems-more-information) This thread should not be used for getting help on any given issue, but only suggestions, wording changes etc to the more information posts As usual, if you are creating a new topic to get assistance with any problem in Fix Common Problems, always include your diagnostics

VM Backup. Known and harmless rclone Known and harmless (It attempts an auto update if the network is up)

Post your diagnostics when you're getting that error

The faults are from "Bad state on FPU" which seems to imply the CPU I'd start by running a Memtest for a couple of passes if only to rule it out.

Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz First thing to check with any crashes when running 10th Gen+ is what the TDP limits are within the BIOS. 99% of the 10th Gen motherboards + would ship with defaults that effectively set the TDP of the processor to be 4096 Watts instead of in your case 125 watts Change the TDP setting from what is probably auto to instead be 125W Also, disable XMP within the BIOS to stop the overclock on the RAM. Crucial doesn't specify what the SPD speed is on the RAM, but it's most likely 2133 and your currently running at 2933

Are these mounts shares on the array or are they via Unassigned Devices?

Not going to comment on why (because I don't use it or have any need or desire to), but if it's java based they tend to be pigs. You can limit the memory usage of any random container by

No. A process kept disk #1 in use. Stopping the array vs a powerdown is a slightly different process. A powerdown (even from the GUI) will after a bit forcibly kill off processes that are tying up the system whereas stopping the array will not.

There is no support mechanism for rolling back releases easily. But, if you have access to the system remotely and not locally, what I would do is grab the diagnostics remotely when it's in the state that you can't access locally and post them.

Last update was yesterday

Parity 2 has at least 1 UNC on it Feb 19 11:43:33 Tower kernel: sd 11:0:7:0: [sdw] tag#2009 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=4s Feb 19 11:43:33 Tower kernel: sd 11:0:7:0: [sdw] tag#2009 Sense Key : 0x3 [current] Feb 19 11:43:33 Tower kernel: sd 11:0:7:0: [sdw] tag#2009 ASC=0x11 ASCQ=0x0 Feb 19 11:43:33 Tower kernel: sd 11:0:7:0: [sdw] tag#2009 CDB: opcode=0x88 88 00 00 00 00 00 05 62 ee 38 00 00 04 00 00 00 Feb 19 11:43:33 Tower kernel: blk_update_request: critical medium error, dev sdw, sector 90369688 op 0x0:(READ) flags 0x0 phys_seg 116 prio class 0 I would start by running an extended smart test on it.

Invalid file (or folder) contained within /mnt NOTE: This has been edited for the new recommendation of /mnt/addons instead of /mnt/remotes or /mnt/disks (3/3/23) Unraid maintains exclusive control over files / folders that are stored within /mnt Any file which may get written there that isn't stored on a disk (/mnt/diskX) or a share (/mnt/user) will be lost on a reboot Similarly, any folder which you are adding to within /mnt should not be there. This usually happens when using something like rclone (or ZFS) and mounting the remote share within /mnt You should instead mount the remote path within /mnt/addons for the least amount of problems Additionally, this can also happen if you have a docker container which is directly accessing a non-existent drive (eg: /mnt/cache when you don't have a cache drive). Usually something like this will happen when you remove or rename a cache pool, as the Apps tab will automatically ensure that the paths when installing any new container correctly match your system) If you have any questions, post the full FCP warning and your diagnostics (from Tools -> Diagnostics) to this thread https://forums.unraid.net/topic/47266-plugin-ca-fix-common-problems

Best option right now is to specify explicit permissions for the folder involved chmod 0777 -R /mnt/user/appdata/qbit/downloads You'll have to adjust the path accordingly. Do not simply specify /mnt/user/appdata. Odds are good that you'll impact the ability of the various apps to start back up again with the same appdata

If you're having problems, it would be better to create your own thread with the details and your diagnostics rather than replying to a 3+ year old thread that is solved.

I just checked this on Unraid 6.10-rc2 and it works as expected -> only a single SMART report is present, so probably already fixed.

Changed Status to Retest

@rix Can I suggest you update the template xml and add in this line <ReadMe>https://github.com/rix1337/docker-ripper#readme</ReadMe>

This just needs to calm down here @stayupthetree, @rix before it gets out of control. The "tag" of Community Developer is not handed out like candy here, and after the initial round of giving this title (when the forum first supported it), it is actually fairly hard to come by and rarely given. Being nasty or sarcastic isn't going to accomplish anything in this circumstance. Arguing by a dev of a container and a user between the various use cases for a container (that the author may have absolutely zero way to test or implement) isn't helpful. As a general rule, all the authors / maintainers etc do everything for free in their spare time with no compensation at all. @rix does appear at first glance to support his applications whether you are a sponsor or not. That being said, it seems to me that because of how containers work there is absolutely no "real" reason why with proper mappings of the devices that multiple instances each with a separate drive mapped to them wouldn't work. I am however also completely unable to replicate any such situation, as I haven't seen a need for any optical drive installed on any system I own (server or otherwise) in over 10 years, so can't say for sure either way. This app was initially added to CA January 13, 2017 and the latest update was 7 days ago, so the application is obviously still supported and not abandoned

xxx.xml file corrupted This error will happen if one or more of the docker template files stored on your flash drive is corrupted. A corruption could occur if your server's memory is defective, the flash drive is defective, or if the server lost power when writing to the flash drive. You should always run a file system check on the flash drive in a Windows / Mac computer. The offending file(s) however will not be fixed. Ideally you would restore the files from a backup you have made (the MyServer's plugin is ideal for doing this). You may also need to replace the flash drive and transfer your registration to a new one. https://wiki.unraid.net/Manual/Changing_The_Flash_Device If you have any questions, post the full FCP warning and your diagnostics (from Tools -> Diagnostics) to this thread https://forums.unraid.net/topic/47266-plugin-ca-fix-common-problems

Directory Read Errors found This error is indicative of two possible issues: Your flash drive has major corruption issues The flash drive has dropped offline and then reconnected itself The only solution in either situation is to reboot. If these problems continue, then you should ideally be using a USB2 port on the server for your boot flash device. If these errors continue to happen on a regular basis, then check for corruption issues (place the flash into a barebones (windows) computer and run the file system check on it) or also possibly install the Flash Remount plugin which will recover the OS automatically from a disconnect / reconnect situation If you have any questions, post the full FCP warning and your diagnostics (from Tools -> Diagnostics) to this thread https://forums.unraid.net/topic/47266-plugin-ca-fix-common-problems