Has this only happened since you rebooted? Or has it been this way since square one?
- What Os/version are you using?
- What is the output of
- How full is your disk? Check with
- Does this return anything related to your SCREEN/rtorrent
ps x | grep rtorrent | grep -v grep? If you do see an rtorrent PID process (perhaps it has frozen) kill the process with
kill -9 PID (replace PID with the actual PID of the screen process... example:
19625 pts/4 DS+ 322:26 rtorrent. You would kill it with
kill -9 19625
- Have you modified your
- If you have
quotas installed, does the user have the appropriate space allowance set with
I hate to come off as snarky... but I'm not buying it. Something has either been modified outside of QuickBox and we're simply not getting the proper information that we need. For this, you'll need to issue some transparency and retrace the steps you took to get this error. I can reboot several machines throughout a week for managed members and have never hit that error... which is more than likely something to do with the user not existing, having no permissions, or the potential that the RTorrent service doesn't exist, bad kernel, modified and poorly configured files, full disk space thus rtorrent will not start.. but you say this applies to all services?