Rtorrent: All torrents are paused immediately after start

[Wymaxep2011]

Hello
I've installed rTorrent 0.9.2/0.13.2 + rutorrent web GUI about 10 times at different VPS with different virtualization and other parameters using same or similar manuals, but now got the same error for the second time. It is OpenVZ but I did it successfully at OpenVZ before.

Sympthoms: when the torrent is started it became paused in few seconds (rutorrent refresh time).
The free HDD size is OK.
In rTorrent there is one [OPEN] and 5 [CLOSED] torrents, all of them loaded fully (I want to start seeding). All 6 are Inactive, done. In RuTorrent the first is "paused" other are "finished". It doesn't matter which one will I start - it will be paused.

The .rtorrent.rc file was copied from VPS where rtorrent worked without any problems (now modified trying to find the reason).

The log is attached (cleared, started rTorrent, started seeding first torrent, it was paused, log copied here).

Please help.

[Wymaxep2011]

UP!!!

[chros73]

Do you happen to have sorting/filtering on started or stopped view? https://github.com/rakshasa/rtorrent/issues/449

[Speeddymon]

Hi @Wymaxep2011 The pastebin seems to have expired. Please reupload it and provide the new pastebin link.

[Wymaxep2011]

No sorting.

Here is a full log, I don't remember what exactly I put there last time
http://pastebin.com/BnErLYXw
The problem still happens at several VPS

[Speeddymon]

Thanks. I am going to copy the log in case the pastebin expires again.

Backup of the log is located here: https://github.com/Speeddymon/rtorrent/blob/Speeddymon-issue_433_log/master_433.log

[Wymaxep2011]

UP
it happens at two OpenVZ servers, one of them I cancelled last week during costs optimization.

[noraj]

It can if the save destination is undefined.

[jeliasson]

I don't know if this helps anyone, but I had the incorrect download path - causing all torrents to hit 'Paused' state.

[somehibs]

Came across this trying to add a torrent to rtorrent in a directory I had no write access to.

[CyberSecGuy]

@jeliasson This resolved my issue, thank you!