./install.sh: line 288: ./slib.sh: No such file or directory

[root@cuixi20181024 ~]# wget https://software.virtualmin.com/gpl/scripts/install.sh --2018-10-24 01:20:51-- https://software.virtualmin.com/gpl/scripts/install.sh Resolving software.virtualmin.com..., Connecting to software.virtualmin.com||:443... connected. HTTP request sent, awaiting response... 200 OK Length: 31528 (31K) [application/x-sh] Saving to: `install.sh'

100%[===================================================================================================================================================>] 31,528 --.-K/s in 0.1s

2018-10-24 01:20:52 (222 KB/s) - `install.sh' saved [31528/31528]

[root@cuixi20181024 ~]# chmod +x install.sh [root@cuixi20181024 ~]# ./install.sh chmod: cannot access `slib.sh': No such file or directory ./install.sh: line 288: ./slib.sh: No such file or directory [root@cuixi20181024 ~]#



Joe's picture
Submitted by Joe on Wed, 10/24/2018 - 00:56 Pro Licensee

Something is weird about your system or your network/DNS is acting up. Is /tmp writeable and does it allow executables? (If you've run a "hardening" script on the system that disables executables in /tmp, the installer won't work...you'll need to run it after installation, though you should only do so if you understand what it's doing and why.)

slib.sh is downloaded into a temp directory by the install.sh, and it contains utility functions we need for the rest of the installer. So, make sure you can download from software.download.com onto the system (though, obviously you were able to for install.sh, so that's kinda confirmed).

Also, can I recommend you use CentOS 7 instead of CentOS 6. CentOS 6 is quite old at this point, with quite old packages, and will reach end of life in 2020. 7 will be a better experience all around.

When I installed it today, I also had the same problem. How to solve it?