crazygambit

I've also been having this issue. Has anyone found a solution? Or at least a way to increase the log size permanently, since 128M seems pretty small and for some reason when the logs roll they're saved in the same directory, which kinda negates the point of rolling in the first place (so the log doesn't fill up in the first place!).

I've been racking my brain to come up with a way to have the plugin automatically start the mover if the cache is filled up over a certain threshold (say 90%), but also run once a day normally at a certain time. I don't want to take the performance hit to run it every hour if it's not needed, but I'm willing to take the hit if it's getting full. I know the plugin won't automatically detect if it's over 90% full, so I'm running it hourly if it's over a certain threshold and have the option to Cron Schedule to force move all of files at 6 am. The problem is that the hourly move never activates, even if the cache is full. Is it possible to do what I want or am I completely misunderstanding what this plugin does?

I got reverse proxy working using Letsencrypt (now called Swag) using nginx just by modifying the provided sample for subdomain. The install instructions mention that subfolder doesn't work so I made a new subdomain using duckdns.org. I've never used Cloudflare, so no clue there.

Is anyone having trouble with setting up email notifications? For some reason the same settings that work perfectly in Ombi don't work here at all. I never get the test email.

Was a solution found to this? I also had my log filled up with this error.

Is there a current workaround? I'm also getting the download error.

Ah yes, I'm indeed using a couple of AOC-SASLP-MV8 cards. If anyone is wondering, the IRQ Nobody cared issue is triggered by either connecting an HDMI out cable to a monitor or USB mouse and keyboard. Simply not doing that (or rebooting after you say change BIOS settings) avoids the problem altogether. Otherwise those cards seem to work fine. I've had them for almost 10 years now.

Really? For me it's a complete performance killer for certain stuff. Like the mover slows to a crawl for example. I've never understood what exactly the problem is.

The release notes for the latest version mentions the removal tests for IRQ x: Nobody cared. Why was that test removed? As someone that has been affected by it in the past (and the present, I know exactly how to trigger it), it was nice to have.

I will check this. There are also some browser extensions that allow you to interact with JDownloader. Instead of copy/paste you links, they could be better alternatives. Did you ever find the answer to this? I find the docker dies with even a moderate number of links ~100. If assigning more resources to it would allow it to work with more, it would be great.

Does anyone know why the webgui doesn't work for me in Chrome while it works in MS Edge? It's not critical, but I'd rather not run Edge. Edit: Also how do I get it to save the settings. The speed limit on downloads is particularly annoying to have to reset each time.

No, I have those on the 15th.

I uninstalled this plugin, but today is the day I had it scheduled to run (the first of the month) and my server is going crazy, so I highly suspect it's still running. I found this in my system log today: Mar 1 05:44:39 Tower inotifywait[5734]: Failed to watch /mnt/disk4; upper limit on inotify watches reached! Mar 1 05:44:39 Tower inotifywait[5734]: Please increase the amount of inotify watches allowed per user via `/proc/sys/fs/inotify/max_user_watches'. Does that mean it is in fact running? If so, how do I disable it? Do I need to install it again and clear the schedule or something?

I've only recently started experiencing issues with radarr. It's using over 5GB RAM (out of 16) and it makes all my dockers completely unresponsive and I start to get 100% CPU utilization. So basically until this is fixed I can no longer use it. Has anyone had any success with limiting the amount of RAM the docker can use?

For some reason it's not making any difference. It still works if I manually redirect, but otherwise, no dice.