Can't resolve hostname

somus1735

Member
May 25, 2018
833
0
16
Since upgrading from rtorrent 0.8.9/0.12.9 to 0.9.2/0.13.2 (on headless server running Ubuntu 10.04), I've been having enormous problems. I compiled everything myself but made what might have been a mistake in not backing up my "sessions" directory.

As soon as I started up rtorrent, all of my torrents had the error "Couldn't resolve hostname." I thought this was weird, since: 1) 0.8.9 had no problem resolving things; 2) no other programme is having difficulty resolving hostnames.

I gathered it had something to do with the Sessions directory so I trashed the files in there. I've got separate watch directories and data directories for different kinds of media, so I moved all the data into the main downloads folder and then readded the .torrent files to the main watch folder. This got all the torrents going with no problem: no problems resolving hostnames and they successfully seeded data to peers.

However, now, whenever I stop rtorrent and restart it, all of the torrents have the "Couldn't resolve hostname" error again. The only way I can solve it is by once again deleting all the Session data, moving all data back to the main downloads folder and re-adding the .torrent files. If I stop rtorrent again: same difficulty resolving hostname.

0.8.9/0.12.9 had none of these problems and was basically bulletproof for me.

Anyone have any suggestions for how to fix this or what might be wrong?
Since upgrading from rtorrent 0.8.9/0.12.9 to 0.9.2/0.13.2 (on headless server running Ubuntu 10.04), I've been having enormous problems. I compiled everything myself but made what might have been a mistake in not backing up my "sessions" directory.

As soon as I started up rtorrent, all of my torrents had the error "Couldn't resolve hostname." I thought this was weird, since: 1) 0.8.9 had no problem resolving things; 2) no other programme is having difficulty resolving hostnames.

I gathered it had something to do with the Sessions directory so I trashed the files in there. I've got separate watch directories and data directories for different kinds of media, so I moved all the data into the main downloads folder and then readded the .torrent files to the main watch folder. This got all the torrents going with no problem: no problems resolving hostnames and they successfully seeded data to peers.

However, now, whenever I stop rtorrent and restart it, all of the torrents have the "Couldn't resolve hostname" error again. The only way I can solve it is by once again deleting all the Session data, moving all data back to the main downloads folder and re-adding the .torrent files. If I stop rtorrent again: same difficulty resolving hostname.

0.8.9/0.12.9 had none of these problems and was basically bulletproof for me.

Anyone have any suggestions for how to fix this or what might be wrong?
 

jith45

Member
May 25, 2018
960
0
16
I have the same issues here when i upgraded rtorrent like you did.

Does anyone have any idea as to why this may be happening?
 

jith45

Member
May 25, 2018
960
0
16
Just an update. I have fixed my issues with this so thought i would post here what i did.

You need to make sure you DON'T set the following in your .rtorent.rc config:

network.max_open_files.set
network.max_open_sockets.set

If you comment out both these lines i found i didn't receive the issues mentioned above.

Hope this helps.
 

jith45

Member
May 25, 2018
960
0
16
Thanks for the reply. No the host name resolution is different to the problem we have had.

Rtorrent wouldn't resolve any host names for the tracker, not the actual peers, therefore you couldn't seed or peer with any other users.

By default you are right the name/dns resolution for the peers is turned off.