Issues pertaining to the installation of DirectAdmin and it’s included services. ./install.sh: line 225: ./directadmin: cannot execute binary file
If you are getting one of the following errors:
./install.sh: line 225: ./directadmin: cannot execute binary file
./install.sh: line 228: ./directadmin: cannot execute binary file
Then it will mean that the OS version tune in your license file does not match the OS you’re using.
For getting the correct binaries, you will need to change the OS set in your license.
You can set this by logging into your /clients section, click the license ID to change the settings, and set the OS as need.
If there it is a new install, re-run the setup.sh again.
If there it is an existing install, then grab the new binaries manually.
Other errors that are causing by the wrong OS:
or on line 21 of /etc/httpd/conf/extra/httpd-vhosts.conf: Could not open configuration file /etc/httpd/conf/ips.conf: No such file or directory
If you have just finish a DirectAdmin install and are trying to start apache, but you get the error:
Syntax error on line 21 of /etc/httpd/conf/extra/httpd-vhosts.conf: Could not open configuration file /etc/httpd/conf/ips.conf: No such file or directory
this means that the ips.conf is missing. The cause of that is usually that the DirectAdmin install did not actually finish.
To finish that install, type:
which is the last step of the DA install. Likely something with this step is failing, then hence the ips.conf is not created. Address whatever error is displaying, then run it again to complete the install.
The usual cause of it will be incompatible binaries (see the link below) or invalid options set in the /usr/local/directadmin/scripts/setup.txt.
Another cause would be if something is in custombuild did not compile correctly.
Type the following:
./build all d
and check for the errors in the last few pages of output if it stops prematurely.