Closed electrotype closed 2 years ago
I'm seeing this also. It also seems that when this happens ratio stuff can also fail on that torrent. So ratio rules for assigning a ratio group based on tracker url doesn't seem to happen. If manually applied then the ratio rules do work okay.
When this happens on torrents it is also quite common for the finished column to be empty, though not consistently it seems.
I'm wondering whether its an issue with how torrents are added and interaction with the UI. One thing I've noticed is that when I'm checking the web UI to see what's going on with these torrents that the timestamps shown are all over the place. The time in the bottom of the window is wrong and existing timestamps on torrents are often several hours or more in the future. Refreshing the browser window seems to bring this back in line.
If a browser session thinks its in the future then maybe this could affect things when a torrent gets added? (maybe it is attempting to work around back-dated timestamps?)
Another data point: when this happens to torrents I note that there is also no pushbullet notification. So it looks like the events aren't being fired for these torrents for some reason. I have a mix of torrents added by sonarr/radarr and also autodl using the direct rtorrent method.
The comments from @esran make me realise that maybe the way I add new torrents has something to do with the issue? I have a script on my local machine which automatically uploads the .torrent
files to the "/watch
" folder on the server where rTorrent runs...
But then again, this works fine and the empty "added" column issue only happens sometimes/after a while.
Possible reasons of this: 1) Failed 'on_insert' handler in the other plugin(s). For detection: add diagnostic to the .rtorrent.rc, catch issue and check log file. For example, by such way:
log.execute = /tmp/rtorrent_exec.log
2) This issue - https://github.com/rakshasa/rtorrent/issues/161 Solution: use patched version of rtorrent - https://github.com/Novik/rtorrent
I enabled the log and had that running when a new torrent failed to get updated. No added date and no pushbullet notification. No errors show in the log. I went back to the previous log entry referring to a torrent, which was a different torrent finishing. Following that we got the following:
I've trimmed out a lot of duplicate messages. Some of these occur very frequently. For reference, here are some counts from the current log file:
Interestingly, I've just been pinged with a finished notifcation for the torrent that failed on adding. So it does have a finish time, but no added time and auto ratio group hasn't been set.
could you fix the problem @esran
I cannot fix this problem, changing date format, restart server or restart plugin didn't help on me
Haha, no. I've switched to qbittorrent.
Haha, no. I've switched to qbittorrent.
are there supports for qbittorrent like execute scripts after finished downloads etc?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
not sure why this is marked as "wontfix" this is an ongoing issue........
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
For those following this issue, I found a workaround that is acceptable for me. It's not a fix.
First, I realized that this empty "Added" field occures only when the web interface is not open when a torrent file is added (I add new torrent files using a script and sftp).
Since I sort by the "Added" column, all new torrents with an empty added date are listed first so they are easy to find.
The trick is to right-click on them, choose Edit torrent...
and then click OK
without changing anything. This will actually populate the added date and the torrent will be moved to the end of the list!
Just to be more specific for those in the future, the added date that is populated using the above method will be the date and time you clicked edit torrent and ok, not the actual date and time the torrent was added. This is a good enough fix for me when my container runs out of memory and crashes all the plugins since I'm just trying to keep track of roughly how long the torrent has been active for, and a few days here and there aren't that big an issue, but may not be for others.
This also resets the ratio column to 0.
You can also write a method for rTorrent in rtorrent.rc
to populate the added time using something like:
method.set_key = event.download.inserted
You need to populate the value of d.set_custom
for addtime
on the current torrent. Should be able to retrieve this from shell.
The real problem though is a race condition with rTorrent
like Novik mentioned. It's not an ruTorrent
issue. I will submit a patch to the swizzin install script when time permits. This is only supported on Ubuntu and Debian though. Many seed box providers use a modified version of this install script. They will probably see the patch and add it to their services.
I'm aware of https://github.com/Novik/ruTorrent/issues/1859 . But the issue still occures with ruTorrent v3.10
The issue is that after a while, the "added" column is not populated anymore. Therefore you can't sort your torrents by the latest ones added, which is an issue for me.
The ruTorrent I use runs on a seedbox provider, pulsedmedia.com , which is very responsive and always keeps the softwares up-to-date. Version 3.10 of ruTorrent is currently installed. The support from Pulsedmedia says that this bug now exists for many years and that the only thing that seems to "fix" it is to restart rTorrent...
I sadly don't have control on the installation of rTorrent or ruTorrent, but I do have access to the files on the server and I see the
seedingtime
plugin is installed.Do you have any idea of what can be the cause for this issue?
Let me know if you need information about any of the files on the server or need an HTTP response from the server for a specific request (I could use my browser's devTools to get it).
Thank you!