[[DEPRECATED] Linuxserver.io - Rutorrent]

9 minutes ago, deusxanime said:

 

I thought for this docker container you had to use the rtorrent.rc because anything you configure in the GUI/ruTorrent is not persistent between restarts? Or do some of the settings you configure in the GUI actually get written back to the .rc file?

I think it is written back to the file, just the wrong parameter name? I can test this and check it.

 

EDIT: Ok maybe not and I was wrong. Wow wonder how I never noticed this then...

[[DEPRECATED] Linuxserver.io - Rutorrent]

53 minutes ago, deusxanime said:

You might want to review all your settings if you are still using those old parameters. They were depreciated for quite a long time actually and finally had support completely removed for them months back. I had the same problem with some other settings as well (must have used an old guide to set it up originally so I was using many of the older deprecated parameters) and went back through and realized I had to redo quite a bunch of them to get things working properly again. Don't remember what version that happened in, but it just kind of stopped working all at once because of that.

I literally never touched the rtorrent.rc file before.

I always used the GUI to configure stuff.

 

But yes, same thing happened to me on my dedicated server.

Lot's of old parameters got depricated.

Took me a while to find out which and where... (the documentation of both rtorrent and rutorrent is kinda bad)

[[DEPRECATED] Linuxserver.io - Rutorrent]

On 5/22/2019 at 2:09 AM, surfshack66 said:

Any particular reason this container is ignoring configuration defined in rtorrent.rc? Despite setting variables in the rc file, this container defaults the global max upload and download rates.

I had the same issue.

 

download_rate = 10000
upload_rate = 5000

is deprecated now or something?

 

I replaced them with:

throttle.global_down.max_rate.set_kb = 10000
throttle.global_up.max_rate.set_kb   = 1000

 

And now it uses those every restart.

Haven't tried update yet but so far so good.

[[support] digiblur's Docker Template Repository]

@phil1c

What I did to fix my UNMS a while back was to not host it using the host ip bridge, but giving it a new private IP address (its somewhere under main docker settings, that you need to enable the private ip range, then you can assign ip's on the docker interface)

 

Then just made it so it doesn't use the 6443 ports but the actual 443 ports in the docker port mappings.

 

Didn't have any PostgreSQL errors as far as I can tell. Will check the logs when I get home.

[ISCSI Support]

+1 from me too.

[[support] digiblur's Docker Template Repository]

I tried UNMS (I own an EdgeRouter)

The webgui runs, everything seems fine.

 

But when try to connect to my EdgeRouter it fails, and I think I know why.

 

I tries to connect back to UNMS but using port 443, not 6443.

You can see this by looking into the EdgeRouter System config, there you see the UNMS url is pointed at port 443.

 

I will try to look into this more tonight, maybe by changing the UNMS port in the software to 6443 and then changing the docker mapping to 6443 -> 6443

 

Or maybe I am just doing something wrong  

 

 

[[Plugin] Linuxserver.io - Unraid Nvidia]

12 hours ago, saarg said:

It's mentioned in the start of this threaf that not all cards are supported by nvidia-smi, which is also stated in your screenshot. None of my 700-series card are supported. 

Emby says it's using nvenc/nvdec, so it's working. 

Ah ok, I thought it was something like that

 

Thanks for confirming and clarifying!

[[Plugin] Linuxserver.io - Unraid Nvidia]

I installed the plugin, everything seems to be working fine, I configured the Emby container with the GPU settings.

 

 

Everything seems to be running ok, except the transcode streams don't show up in the nvidia-smi utility.

 

I ran that from the main server console, is it supposed to be launched from somewhere else?

 

Included are some screenshots.

[Kernel Crash: "BUG: unable to handle kernel NULL pointer dereference at x"]

Yesterday I installed unRAID, and setup my 4disk + 1 cache disk array.

 

I already started copying some data over while the parity drive was initializing, everything was going well.

Was at 50% done when I went to bed, woke up and was greeted by a kernel panic/crash.

 

 

I restarted the PC again, since the webui was not available anymore.

Started the array, seems like no errors, but it's redoing all of the parity stuff again now.

 

So I wanna know, what went wrong? And what can I do to prevent this in the future?

[Can't write to USB.]

Yes, I used the alternative method for preparing the USB, (also tried with other USB) and that worked!

[Can't write to USB.]

https://s.lolisandstuff.moe/aomsYaYR.png

Can't write to the USB drive, says "couldn't open physical device"