Squid
-
Posts
28,770 -
Joined
-
Last visited
-
Days Won
314
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by Squid
-
linuxserver/plexpy is installed otherwise you wouldn't be seeing the warning from FCP (and its no longer being maintained as per LSIO)
-
That's the issue. Regardless if your app has been automatically renamed at some point to be tautulli, linuxserver/plexpy (the repository your app is being pulled from) is no longer maintained, and is deprecated (actually, LSIO even deleted that template because of this) You really should install tautulli (linuxserver/tautulli) instead which is being maintained.
-
No problems per se as they can exist side by side. But, you would double the CPU usage at the very least as they both try to hash any new files added concurrently
-
I would think that every plugin including CA is having the same problem. My initial suggestion would be to rename config/ssl and config/ssh on the flash drive to something else, reboot and see what happens.
-
what about cat /etc/cron.d/root and crontab -l -
What about other plugins?
-
Not much choice
-
No it's not You error states unable to import xxx from /data/..... You can tell deluge to download to /downloads, but since you don't have /downloads mapped in the template, it winds up being stored within it's image, and doesn't matter what you do but sab will never have access to it. Change the container path for /data in deluge to be /downloads But, deluge (and Sab) may remember the original download path you had set when you queued up files (if it was originally set to use /data in its settings)
-
100% this https://forums.unraid.net/topic/57181-real-docker-faq/page/2/#comment-566086
-
Any password would be stored within /mnt/user/appdata/sabnzbd/someFilenameIDon'tKnowSinceIDontRunSab You would have to edit that particular file, or delete the entire folder and reset up Sab
-
Look in /mnt/user0 (BTW, if /mnt/user0 doesn't exist in the first place, then all checks for mover running is pointless)
-
What you should really do is advise the user to also stop all running VMs and docker containers, and not access the array at all since all of this can (and will) negatively impact the tests
-
Actually you would have to replace mover with a different script #!/bin/bash exit 0 So that if / when cron decides to execute the mover script, the non-existant script doesn't trigger an email to root. (Or get really fancy and have the different script send a notification that mover isn't running because UTT is running)
-
Mover technically can't be disabled. But a workaround is to rename /usr/local/sbin/mover to something else for the duration of the tests.
-
I'd hate to do it in bash. But a php script (eg) would be easy. In pseudo code, parse all of the .cfg files within /boot/shares, look for any shares which are set to use cache yes and file(s) exist on the cache drive, and use cache prefer and file(s) exist on the array.
-
I've un-deprecated the plugin because it does have use and I still regularly use it for convenience. There is now a huge warning though on the main page that if you screw up and delete an entire share because You severely misconfigured an app no longer installed, You checked off the folder to be deleted You answered the question "Are you really sure" Then you're SOL and maybe would be a candidate for the Darwin Awards
-
Maybe I'm missing something, but last time I checked, a PI runs ARM and unRaid is x86
-
Works for me
-
Autostart & delays are stored within the docker.img file (/var/lib/docker/unraid-autostart) CA when installing previous apps always sets everything to autostart as the assumption is that more often than not a user will want the app to start up automatically instead of being manual start. IE: Its how I want the system to work by default - any installation is set to autostart by default, and to not have it do that you then have to turn it off rather than the other way around.
-
Aug 1 14:48:11 BriServer kernel: FAT-fs (sda1): error, corrupted directory (invalid entries) Aug 1 14:48:11 BriServer kernel: FAT-fs (sda1): Filesystem has been set read-only Aug 1 14:48:11 BriServer kernel: FAT-fs (sda1): FAT read failed (blocknr 342) Shutdown, toss the flash into another computer and run checkdisk on it.
-
Practice, guesses, reading other users responses here who actually know what they're talking about (and no life )
-
Your share M---a exists on the cache drive, but is set to not use the cache. Change it to Use Cache Yes temporarily to clean that up next time mover runs. You can hit "Compute" on the Shares tab next to that share and you'll see how much space it takes up.
-
@ and then the user name, and select it from the drop down @radfx
-
Is your date and time correct? Sent via telekinesis
-
Easier to simply get it from the docker tab, calculate container size
