Cessquill

Why did I have it in my head a dev was on here? Apologies.

Hi - is it (or might it be) possible to add a note to the weekly email? There's often times when there's a small announcement that doesn't warrant it's own email. If a field could be populated during the week, inserted into the email and then cleared that would be very handy. 😀

Completely understand, and share concerns. Maybe appending a download request url with "&new=true" (or technical equivalent and encrypted depending on mechanism)? As I understand it (and I'm wrong a lot), your download is already counted but not associated with anybody. This just allows that same count to be arguably more useful, and it's still not tied to you. I get why it's a contentious issue - just thinking out loud.

That's not what I meant, TBH. When your client downloads something, it currently adds 1 to a download count for the star system (the way I understand it). I was proposing that the count is only increased if it's a fresh install, and not an upgrade. It's not storing anything about you specifically having it. There is some mechanism (I'm guessing client-side) to list your previous apps and installed apps already within CA. Therefore, when an app is downloaded, a yes/no flag would highlight whether this was a new install. Wouldn't be super-accurate. Obviously getting hypothetical, since I have no real clue how it works, but ultimately I wasn't suggesting that CA maintain an online database of who's got what. Just some kind of anonymous count.

Sorry, "most people use" wasn't a great phrase, and I get why it's not that simple, and potentially misleading. Some containers update almost daily. Having some mechanism to auto-highlight the most popular on a list without necessarily having to sort by it would be handy though. Can you easily discern between fresh install and upgrade? Hopefully as CA knows what a user has installed, it might somehow maintain an install count for each app. Lots of ifs and maybes in there though. I wouldn't know how useful an actual rating system would be. This time around I went to the support threads of each and tried to work it out for myself. Thanks for the comments, very interesting.

I was looking to install Emby for the first time the other day, and wanted a quick way from the search results to see which one most people use. In the past I'd normally go down the "most starred" route. Whether that's fair to the other devs (or best for my use case) is debatable, but it helps make a choice (in the same way that plumping for an Amazon product with the highest rating does).

Apologies - I stared at that for ages and still missed it. Long day. Didn't help that I checked against mine on a mobile phone and don't have 58946 mapped. As you were...

According to your screenshot, you've got the same port mapped three times in your container settings (port 58846). That doesn't look right.

That's handy (I hope). I sent @SlrG my conf file, which was slightly modified but not crazy - and it doesn't look like anything in it would prevent it from starting. Could be another plugin/setting I've got - my machine's not a mess, but it's been upgraded since v4.7, so you never know.

/usr/local/SlrG-Common/usr/local/sbin/proftpd: error while loading shared libraries: libssl.so.1: cannot open shared object file: No such file or directory I'm in a similar boat - RC4 won't start, whereas 6.6.6 was fine. The above is the result of your command

Thanks - that's what I was thinking. PIA has a 5 connection limit, so it's not the end of the world using 2 or 3 of those on Unraid. Would rather use as few as possible though. (the support link in CA currently points to here - assuming a new topic will be created and linked in due course)

Apologies if this is the wrong thread , but a support link in CA sent me here. Just found binhex-privoxyvpn in CA, and from what I can tell it's fairly new. Is it the "VPN" part of the other binhex containers (ie, binhex-delugevpn without the deluge)? If so, this might come in handy - I've raised before that I've wanted to stop a container, but couldn't because VPN traffic was going through it. If so, I'm guessing deluge/rtorrent can be set to use a proxy and have VPN turned off?

Out of interest, if you didn't receive a warning, and space in your container was ~8GB, why do you think it was full? I get that the issue is solved now and you've resized, but just restarting the docker system (which you'll have done to resize) may have solved the issue

OK. Only trying to help - your container size information was not in your post when I initially replied.

You did not receive a warning that your container was getting full? If you did, that was your warning - that's what I'm getting at. I understand that dockers removing or reporting false updates is frustrating, but there will be unexpected behaviour if you run out of space. And since dockers don't store any config/data, there's no harm done.

That's not this docker's fault. Do you not receive notifications when your container is getting full?

Shot in the dark - have you recently filled up your cache drive (assuming your appdata is on your cache)? I've had problems before when dockers essentially ran out of space and got upset. If so, you could try going to settings, dockers, and turning them off and on again (or just rebooting Unraid) to restart the docker system. Then go to the dockers, delete any hanging images, and reinstall any dockers that are no longer on your list (CA, previous installs (or similar text)).

I'd quite like this too, but for completely lazy reasons. I don't have any dummy drives in my server's hotswap bays, so to keep the airflow normal I have old drives in there that I manually spin down on boot (don't know whether this is bad practise). (whilst typing this, I just thought of the hdparm -Y option, which will take the drive out of the system altogether, yes?)

I've not really delved into this part of Radarr before, but does anybody know if it's possible to edit when scheduled tasks are run? Mine seems to run Refresh Movies daily at about 10pm. This really eats into RAM and CPU usage and takes a while when my server's likely to be transcoding. I'd prefer intense tasks to be run during downtimes if possible. Appreciate that this is more of a Radarr dev thing, but thought I'd ask here before venturing out.

Remember that move is just like "copy then delete". If the source disk can't be altered, then the delete portion can't run.

Sorry if this is a silly question, but are they actually paused? That is, are you adding them in a paused state? And if so, does pressing the "Resume" button at the top do anything?

You could always add a User Script to check cache free space and invoke the mover if it is over x% - I have one that runs every minute (and 99.9% of the time does nothing). Then mover is invoked whenever my cache starts to fill up. Not always fail-safe, as data can often be written to the cache faster than it's copied off, but it might help to you run larger batches. Alternatively, do you have an old larger disk that you could temporarily use as a cache drive? Doesn't need to be SSD. Mass moving of data in batches over a week or so is something that I end up doing quite a lot, and assumed that a lot of Unraid users did it too.

Pretty much, yes. I'm not at my machine at the moment, so it might be a little vague, but in the plugin... Click the Add Script button Give it a title (say, Spin Up All Drives, or whatever you want) Save it Hover over the new script entry that's been created and click on it. The popup that appears will allow you to "Edit Script". Click on this In the box that appears at the top, enter... #!/bin/bash disks=$(ls /dev/md* | sed "sX/dev/mdXX"); for disknum in $disks; do /usr/local/sbin/mdcmd spinup $disknum; done Click the Save button. Your script will now be created To test it, you can click the Run Script button next to the title. A window will pop up. If its contents have any errors, we'll need to look into them. If not, close the popup and switch to the home page and check that all drives have spun up (note, mine didn't have temperature readings for a few minutes) If it's working as expected, you can now schedule it to run during your peak times. Go back to the User Scripts plugin. To the right of your script you've got a schedule dropdown. From it, select "custom" In the text box to the right of that, enter/paste... */10 20-22 * * * Click apply at the bottom. This is a cron schedule that basically tells User Scripts to execute your script every 10 minutes between 20:00 and 22:00 (actually at the end of 22:00, so in this case 22:50), every day. Adjust these hours to suit. I have to relearn the formatting every time I do something like this, but fortunately there are a lot of online tools to build the schedule code for you Once the script has run on the schedule, you'll get three buttons to the right of it - one of them allows you to view the log. You can use this to check for errors and make sure it's running at the correct times I've assumed that your disks' spin-down times are 15 minutes (default?). If not, you can adjust the 10 at the start to something that's just before when they'd normally spin down. Technically you could set the "10" to "14" As mentioned, if you need multiple schedules, that's possible with duplicating the script and adjusting the schedules of each to suit What I haven't thought about is whether running the spinup command on a drive that's already spun up will reset its spin-down timer. That is, if it's been up for 10 minutes, scheduled to spin down in 5 and you run a spin-up command - will it still spin down in 5, or has it been reset to 15? I'm afraid I don't know enough about the innards of Unraid, but it could be tested (and somebody would know).

Script to spin up all drives at certain times of day... #!/bin/bash startTime="20:00" endTime="23:00" begin=$(date --date=$startTime +%s) end=$(date --date=$endTime +%s) now=$(date +%s) if [ "$begin" -le "$now" -a "$now" -le "$end" ]; then disks=$(ls /dev/md* | sed "sX/dev/mdXX"); for disknum in $disks; do /usr/local/sbin/mdcmd spinup $disknum; done fi Instructions... Set appropriate start and end times (example above between 8pm and 11pm) Set it to run with a custom cron schedule of - say - every 10 minutes (or lower than your drive's spin down timings... */10 * * * * Notes... This checks every ten minutes to see whether it's within the window. If so, issue a spin up command on all data drives (could potentially check its state beforehand?) There might be a way to cron it so it only runs during the window, but I don't know enough about that More complicated schedules (eg, longer times at weekends) would need more complex logic, or duplication of the script It was written from bits and pieces I found. If I'm doing something very bad, please do let me know. Somebody raised it in a post and I thought "this sounds like a job for User Scripts" Testing it seems to work fine. Drives appear to spin up straight away, but don't have temperature readings for about 4-5 minutes (19 data drives) Edit: after looking more into cron, you can simplify it by making the schedule decide when the script runs, and having the script just run spinup. New script... #!/bin/bash disks=$(ls /dev/md* | sed "sX/dev/mdXX"); for disknum in $disks; do /usr/local/sbin/mdcmd spinup $disknum; done with the schedule command as... */10 20-22 * * * If I understand correctly, this will trigger the script at 8pm, and then re-run it every 10 minutes until 22:50. Change these values to suit. I've kept both for now in case one is stupid. Plus some snippets might come in handy for other people's projects. If you want to have your drives up for a different duration at the weekends, duplicate the script and give them both different schedules... Every 10 minutes between midday and 11pm, Saturday & Sunday */10 12-23 * * 6-7 Every 10 minutes between 8-11pm, Monday - Friday */10 20-23 * * 1-5

If it's got a "Cessquill Unraid" dymo label on it, you might want to give it a real deep clean 😄