arakasi72 / rtinst

seedbox installation script for Ubuntu and Debian systems
MIT License
1.22k stars 259 forks source link

RuTorrent failed to install on fresh Debian 10.6 'Buster' #545

Closed surfcode closed 4 years ago

surfcode commented 4 years ago

I booted up a fresh Debian Buster 10.6 which was installed via the netinstall iso and only added a local user with sudo permissions before using the script.

Used the following command: sudo rtinst --log --webpass mySecretPassword --dload --ssh-default -u myUnixUsername

Everything installed fine except for RuTorrent. Relevant log items pasted and highlighted in bold:

Start of the script:

Checking major 3rd party components Rtorrent: OK xmlrpc-c: OK RuTorrent: OK Autodl-irssi: OK

Middle of the script (comments partly translated to english):

Installing Rutorrent () tar (child): .tar.gz: Function open() has failed: File or directory does not exist tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now tar (child): .tar.gz: Function open() has failed: File or directory does not exist tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now mv: missing destination after 'rutorrent' Type 'mv --help' for more information. rm: cannot remove '.tar.gz': File or directory does not exist Configuring Rutorrent rm: cannot remove 'rutorrent/conf/config.php': File or directory does not exist cp: cannot create normal file '/var/www/rutorrent/conf/config.php': File or directory does not exist

End of the script:

RuTorrent Web GUI RuTorrent was not installed

Let me know if you need additional info. Thanks!

surfcode commented 4 years ago

I deleted the virtualized Debian Buster installation and created a new one. Did the exact same steps again and RuTorrent still failed after using the install command. First givinig me errors about github.com not being resolved. After 5 minutes I tried the install command again and RuTorrent got installed succesfully.

Cannot wrap my head around what just happend. Maybe Debian was still initializing in the background? That would be weird as Debian is a stable and sane OS.

Issue can be closed.