Open fiver22 opened 1 month ago
possibly related: when attempting to move torrents from the broken path to correct dir, I sometimes get "DataDir plugin: operation fail"
@fiver22 Could you upgrade to ruTorrent v4.3.6
or ask your provider to upgrade? We resolved an auto move regression with this version. We would need to know if this issue is present on the latest version of ruTorrent to move forward with diagnostics.
@fiver22 Could you upgrade to ruTorrent
v4.3.6
or ask your provider to upgrade? We resolved an auto move regression with this version. We would need to know if this issue is present on the latest version of ruTorrent to move forward with diagnostics.
Happy to ask that they upgrade. I will ask and report back what I can.
Was able to upgrade to 4.3.6. The issue has not been completely resolved but may have changed. normally I would have expected 3 or more such errors over the 80 some torrents added but I have only seen one similar error and it's behaviour is a little different:
the error now presents as save path = /home14/[user_name}/downloads/Literal Name of Torrent /dev/sdae1 1881839948 2929687500 0 32543 0 0y
I hope this can be of some use. Happy to provide any detail I'm able -just let me know what would be useful.
Could you provide a screenshot of the autotools tab in your settings menu?
Please complete the following tasks.
Tell us about your environment
Web Browser: latest firefox stable , latest chrome stable, n/a ruTorrent Version: v4.3.5 PHP Version: PHP 8.1.2-1ubuntu2.18 Operating System: Ubuntu 22.04.4 LTS
Tell us how you installed ruTorrent
seedbox provider installed -hopefully they will add detail
Describe the bug
Occasionally, approximately 1 out of every 30 torrents, torrents are saved to incorrect paths that include unintended concatenations of system outputs and the intended paths. This issue seems to trigger timeouts and loading errors in ruTorrent.
Example of Incorrect Save Path: Path format with spacing detailed:
/dev/sdae1␣498814504␣␣2929687500␣␣␣␣␣␣␣0␣␣␣␣␣␣␣␣16513␣␣␣␣␣␣␣0␣␣␣␣␣␣␣0␣␣␣␣␣␣␣␣/home14/{user_name}/downloads
Steps to reproduce
Add torrents as usual. Observe the save path for each torrent. Note that approximately 1/30 torrents exhibit the issue described.
Expected behavior
All torrents should be saved to the designated save path, in this case: /home14/{username}/downloads
Additional context
This issue occurs on a shared slot provider where I do not have root access. I have already opened a ticket with the provider, and they suggested posting this bug report. Possibly related issue: #1585