Replies: 8 comments
-
That's a lot of torrents. Maybe the qbittorrent App or the Apps framework itself implements some kind of resource limits? Should be possible to do with systemd-nspawn too, see their docs. I never needed it myself. |
Beta Was this translation helpful? Give feedback.
-
With linux, To review the log from the previous boot, run: journalctl --boot=-1 --all --reverse This will list all of the messages from the previous boot in reverse order in a pager (less), you migth glean some insight on why things went bad. |
Beta Was this translation helpful? Give feedback.
-
Nothing special in the logs, I've already checked many times... When I want to take my jail in ssh, the connection can take 1 to 2 seconds to be established the first time, as if it had to be woken up. |
Beta Was this translation helpful? Give feedback.
-
Good luck! Sounds like it's running out of some resources. But which one? Idk. Maybe a TCP connection limit? |
Beta Was this translation helpful? Give feedback.
-
I think that's exactly it, when I start my qbit instance with kubernetes I get this message: Apr 30 15:08:52 SRV-NAS kernel: TCP: request_sock_TCP: Possible SYN flooding on port 10.13.128.113:50025. Sending cookies I tried to solve the problem by tunning the kernel settings, but without success:
Also Truechart said to add this kernel value:
But with my jail, I don't get the Two question is comming because I read the entire manpage Duo to the fact for my qbit instance I use
Also do I need to modify RLIMIT ? --rlimit=RLIMIT_NOFILE=32768
--rlimit=RLIMIT_NPROC=4096 root@SRV-DOCKER:~# ulimit -Ha
real-time non-blocking time (microseconds, -R) unlimited
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 513382
max locked memory (kbytes, -l) 16471004
max memory size (kbytes, -m) unlimited
open files (-n) 1048576
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 513382
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
root@SRV-DOCKER:~# ulimit -Sa
real-time non-blocking time (microseconds, -R) unlimited
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 513382
max locked memory (kbytes, -l) 16471004
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 513382
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited but these settings don't solve the network latency problem I'm having :/ Do I need to switch this issue as discussion ? |
Beta Was this translation helpful? Give feedback.
-
I have converted the issue into a discussion. I don't think there's anything wrong with jailmaker which is causing this situation. I don't use qbittorrent or wireguard in a jail so I don't know how to fix this. |
Beta Was this translation helpful? Give feedback.
-
I've found my problem, it's a Truenas Scale bug
The problem will be solved in the next version 24.04.1 and higher Temporary fix :
|
Beta Was this translation helpful? Give feedback.
-
No more problems on my side, the middleware works well and without any latency ! |
Beta Was this translation helpful? Give feedback.
-
I carried out several tests over 2 weeks and realized that when I launch my docker qbittorrent instance via my jail, after a while my Truenas middleware no longer responds.
Here's my docker-compose.yaml file
For my jail, I used the template here, and only passthrough the nvidia gpu.
Today, my qbittorrent instance has over 8500 torrents, it works fine with kubernetes but as I said above, when I start my qbit instance in the jail, my truenas become unresponsive over time, the whole system lags and all this doesn't happen instantly!
I turn off my qbit instance and the web interface (middleware) and the system of my truenas work perfectly (sometimes I need to restart the middleware anyway).
Being a bit desperate, I'm turning to you for an idea of why this is happening...
I can do tests if you wish and don't hesitate if you want more information!
Beta Was this translation helpful? Give feedback.
All reactions