If you have any trouble during pyrocore installation and
configuration, or using any of the commands, join the pyroscope-users
mailing list or the inofficial
##rtorrent channel on
irc.freenode.net. IRC will generally provide a faster resolution.
If you are sure there is a bug, then open an issue on GitHub. Make sure that nobody else reported the same problem before you, there is a search box you can use (after the Filter button). Please note that the GitHub issue tracker is not a support platform, use the mailing list or IRC for that.
Please describe your problem clearly, and provide any pertinent information. What are the version numbers of software and OS? What did you do? What was the unexpected result? If things worked and ‘suddenly’ broke, what did you change?
On IRC, don’t ask if somebody is there, just describe your problem. Eventually, someone will notice you – IRC is a global medium, and people do live in different time zones than you.
Put up any logs on 0bin or any other pastebin service, and make sure you removed any personal information you don’t want to be publically known. Copy the pastebin link into IRC or into your post.
The following helps with querying your system environment, e.g. the version of Python and your OS.
Providing Diagnostic Information¶
Execute the following command to be able to provide some information on your Python installation:
deactivate 2>/dev/null; /usr/bin/virtualenv --version; python <<'.' import sys, os, time, pprint pprint.pprint(dict( version=sys.version, prefix=sys.prefix, os_uc_names=os.path.supports_unicode_filenames, enc_def=sys.getdefaultencoding(), maxuchr=sys.maxunicode, enc_fs=sys.getfilesystemencoding(), tz=time.tzname, lang=os.getenv("LANG"), term=os.getenv("TERM"), sh=os.getenv("SHELL"), )) .
enc_fs is not
UTF-8, then call
dpkg-reconfigure locales (on Debian type systems) and choose a
proper locale (you might also need
locale-gen en_US.UTF-8), and make
LANG is set to
en_US.UTF-8 (or another locale with UTF-8
Similarly, execute this in a shell prompt:
uname -a; echo $(lsb_release -as 2>/dev/null); grep name /proc/cpuinfo | uniq -c; \ free -m | head -n2; uptime; \ strings $(which rtorrent) | grep "client version"; \ ldd $(which rtorrent) | egrep "lib(torrent|curses|curl|xmlrpc.so|cares|ssl|crypto)"; \ ps auxw | egrep "USER|/rtorrent" | grep -v grep
Common Problems & Solutions¶
“rTorrent-PS features NOT active!” during rTorrent startup¶
As mentioned several times in the installation guides,
you must tell the standard
include that it’s loaded into a rTorrent-PS installation.
The way to do that is setting the
pyro.extended constant to
method.insert = pyro.extended, value|const, 1
If you do that and are not actually running rTorrent-PS, you will get errors about missing commands during startup.
WARNING: … (update rTorrent-PS)!¶
If you run vanilla rTorrent instead of rTorrent-PS, these message will appear during startup. They can be silenced, see below.
If you run rTorrent-PS, the warnings are there to tell you that you should update to a recent version supporting new features. So just do that. ☺
Otherwise, either ignore the warnings (that is why they are WARNINGs and not ERRORs),
or else add the files in
that are logging them to the
You’ll find the specific files using
grep -RinH update.rtorrent ~/.pyroscope/rtorrent.d
“Input failed: ExecFile::execute(…) Fork failed.” during searches¶
This is always a host setup problem and not one in this software.
Check your resource limits,
nofile (max. number of open file handles)
nproc (max. number of processes).
Also look into
~/rtorrent/log/execute.log if it contains any hints.
“Scheduled command failed: bind_home: Bad key definition.” during startup¶
Your rTorrent-PS is too old to support the new default key bindings
End, and so on. Either compile the HEAD of rTorrent-PS
to update your installation, or else do this:
echo >>~/.pyroscope/rtorrent.d/.rcignore "bind-navigation-keys.rc.default"