Short answer:
most likely Flood is creating the job correctly but
rTorrent is refusing to start/accept it because of either (a) rTorrent isn’t fully running/SCGI socket mismatch, (b) file/dir
permissions or wrong download/session path seen by the rTorrent process, or (c) a broken ipfilter / config that prevents rTorrent from launching after Flood posts the torrent. Check rTorrent logs and Flood → rTorrent connectivity and fix the path/permission or disable ipfilter. Below are concrete checks and steps you can perform on a QNAP with rTorrent-Pro / Flood.
What to check first (quick list)
1) rTorrent service health and logs
- Look at the rTorrent logs: Rdownload/logs/rtorrent.error.log, Rdownload/logs/rtorrent.critical.log and Rdownload/logs/rtorrent.storage_critical.log for errors about starting, permission denied, session folder, or ipfilter problems. These logs are the primary source of why rTorrent refuses tasks.
2) IP filter
- If you enabled an external ipfilter/peer
block list, disable it and restart rTorrent. An incompatible ipfilter can prevent rtorrent from starting (see forum fragment saying ipfilter can avoid start of daemon).
3) Does rTorrent actually run and accept requests from Flood?
- Confirm the rTorrent daemon is up (process present) and that Flood’s configured SCGI/HTTP endpoint matches the rTorrent endpoint. If Flood cannot reach the rTorrent RPC/SCGI socket it will show the torrent but it won’t start.
4) Download directory / session path and permissions
- Ensure the download directory that Flood uses matches the path rTorrent is configured to use and that the running rTorrent user (the rTorrent-Pro package user) has read/write/execute permissions on that path. Common problem: Flood posts a torrent with a download directory Flood can see, but rTorrent cannot write to it.
5) Test adding the same torrent via rTorrent Advanced UI
- If adding from rTorrent’s Advanced UI works but Flood does not, the problem is the interface between Flood and rTorrent (SCGI/socket or path mapping). If both fail, the problem is rTorrent config/service itself.
Detailed troubleshooting steps (do these in order)
1) Inspect rTorrent logs
- Open Rdownload/logs and read rtorrent.*.log files for obvious errors (permission denied, cannot create session file, ipfilter errors, relaunching watchdog messages). These logs generally tell why a torrent stays paused after being added from an external UI.
2) Temporarily disable ipfilter
- Using the rTorrent-Pro UI or by removing the ipfilter list, disable it and restart rTorrent. Forum reports show an ipfilter can make rTorrent fail to start or limit functionality.
3) Verify service/process
- Confirm rTorrent is running continuously. If you see repeated watchdog messages (“rtorrent is down. Relaunching...”), rTorrent is unstable and external UIs will be unable to control tasks reliably.
4) Verify Flood → rTorrent connectivity/config
- In Flood settings check the configured rTorrent endpoint (SCGI socket or host
ort). Make sure Flood is talking to the same rTorrent instance that the base UI uses.
- If Flood is configured to use an SCGI socket file but rTorrent is listening on TCP (or vice versa), Flood will add the torrent but rTorrent won’t process it.
5) Compare the torrent-add behavior and directory values
- Add a test torrent in Flood and note the "target directory" Flood is sending. Compare that to rTorrent’s configured default directory (rtorrent.conf “directory” setting or the package’s setup). If Flood sends a path that is not writable or not visible to the rTorrent process (e.g., /share/Download vs different
mount), rTorrent will create a paused entry.
6) Check
NAS share mounts and tmpfs pitfalls
- If you used a manually created /share/Download symlink or created directory via CLI,
QTS may mount shares differently (tmpfs issues on boot). Create the Download share via QTS GUI to ensure persistent mount, and ensure rTorrent uses a stable path (not a tmpfs-only path).
7) Fix permissions
- On the download folder and rTorrent session folder ensure owner/group and POSIX permissions allow the rTorrent process user (the package account) full access. Use the QTS File Station permissions or chmod/chown if needed.
8) Reset to defaults if configuration is corrupted
- If config corruption is suspected, you can restore defaults: uninstall rTorrent-Pro and remove the Rdownload (or the package data) and Download/rtorrent folders as described in the package notes, then reinstall. WARNING: this removes rTorrent configuration and possibly torrents state — back up session files if you need to keep current tasks.
9) After changes: restart rTorrent, then Flood
- Restart rTorrent service (or reboot NAS if you prefer) and then restart Flood UI. Try adding the torrent again from Flood. Monitor rtorrent logs while adding to catch immediate errors.
10) If Flood shows UI JS errors (window.flm undefined)
- That error can indicate Flood’s UI can’t communicate with the backend; check browser console only for UI-side issues, but primarily confirm the backend rTorrent API is reachable and the flood service is healthy.
Notes on differences and common traps (based on forum patterns)
- Many users saw rTorrent behave fine when adding torrents from the "base" rTorrent UI (because that UI talks locally to the correct instance and uses correct paths/credentials), while Flood (as an external UI) fails when Flood’s configured connection or paths differ from what rTorrent expects.
- IP filter lists and bad configuration lines in rtorrent.conf commonly cause rTorrent not to start or to run partially, which leads to paused sessions when torrents are added externally.
- Creating persistent Download share via QTS GUI avoids disappearing /share/Download problems on reboot; creating it manually in CLI sometimes leads to tmpfs/mount issues.
If you follow the above you should find one of these is the root cause: rTorrent not running reliably; Flood pointing to the wrong SCGI/socket; permissions or path mismatch; or ipfilter/config preventing starts. Fix that and torrents added from Flood will start automatically like those added from the base UI.
Closing summary (concrete next actions)
1) Open and read Rdownload/logs/rtorrent.*.log for clear errors.
2) Temporarily disable ipfilter and restart rTorrent.
3) Verify Flood’s rTorrent endpoint (SCGI socket or host
ort) matches the running rTorrent instance.
4) Ensure download/session folders exist, are persistent (create share via QTS GUI) and writable by rTorrent.
5) If config seems corrupted, uninstall rTorrent-Pro, remove package data (per the package notes) and reinstall (
backup session if needed).
Do these in order; logs will usually point to the exact cause.
Źródła na forum:
Ta wiadomość pochodzi od asystenta AI — może zawierać błędy, zweryfikuj przed zastosowaniem. Oceń ją, głosując pod postem: ▲ pomocna lub ▼ nieprzydatna.
Na tym forum nie ma złych ocen — wszyscy wciąż się uczymy i wszyscy jesteśmy adminami, a +1 czy −1 to zawsze tylko 1 punkt. Każde Twoje kolejne pytanie to wspólna pomoc, która zostaje nie tylko na forum, ale i w internecie. Społeczność forum QNAP działa od 2008 roku i po niemal dwóch dekadach nieprzerwanie dostarcza rzetelne treści, z których korzystają kolejni admini — a ostatnio uczy się na nich także AI.
