Issues pertaining to the installation of DirectAdmin and it’s included services. /usr/include/krb5.h:2606:24: et/com_err.h: No such file or directory

If you receive the following error

/usr/include/krb5.h:2606:24: et/com_err.h: No such file or directory

When you are compiling, run the following then try again:

yum install e2fsprogs-devel

or

up2date -u e2fsprogs-devel

 

---

For CentOS 6, this file is provided by:

yum install libcom_err-devel libcom_err

 

./install.sh: line 225: ./directadmin: can not execute binary file

If you get one of the following error:

./install.sh: line 225: ./directadmin: cannot execute binary file
./install.sh: line 228: ./directadmin: cannot execute binary file

Though it will mean that the OS version tune in your license file does not match the OS that 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 needed.

If it is a new install, then re-run the setup.sh again.
If it is an existing install, then grab the new binaries manually.

Other errors that are causing by the wrong OS:

./install.sh: ./directadmin: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory
./install.sh: ./directadmin: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory

Bus 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

If you have just finishing a DirectAdmin install and are trying to start Apache, but if you get this 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 is usually that the DirectAdmin install did not actually finish.

To finish the install, type:

cd /usr/local/directadmin
./directadmin i
./directadmin p

which is the last step of the DA will be install.  Like though something with this step is failing, hence the ips.conf is not created.  the Address whatever error is displaying, then run it again to complete the install.

The usual cause of that incompatible binaries (see the link below) or invalid options set in the /usr/local/directadmin/scripts/setup.txt.

Another cause of that would be if something in custombuild did not compile correctly.  Type the following:

cd /usr/local/directadmin/custombuild
./build all d

and check for the errors in the last few pages of output if it stops prematurely.

Connecting to www.directadmin.com|216.144.255.179|:443… failed: Connection timed out.

If, during of the install of DA, you will get the following error:

–2011-11-22 10:12:06–  (try:11)  https://www.directadmin.com/
Connecting to www.directadmin.com|216.144.255.179|:443… failed: Connection timed out.
Retrying.

it would mean that the connection to our server will not be established.

1) If you have successfully downloaded the setup.sh from www.directadmin.com, then it would imply that our firewall is not blocked you, as if we block an IP, we block the IP on all ports.  For testing this, try:

wget -O /dev/null http://www.directadmin.com/index.html
wget -O /dev/null https://www.directadmin.com/index.html

If there both ports are blocking, try this test to other websites, eg:

wget -O /dev/null http://www.apple.com/index.html
wget -O /dev/null https://www.apple.com/index.html

2) If you cannot connect to outbound of any server on port 443, then it’s likely a firewall on your end.  Do this:

/etc/init.d/iptables stop
/sbin/chkconfig iptables off

3) If apple.com works, but directadmin.com does not (with the above guide), then try to contact us to see if your IP is in in our firewall.  It is also possible it’s blocked at our datacenter, in which case you would need to contact them to get it unblocking.  However, if it is blocked at our datacenter, then there would be a reason for that, so you would need to convince them that whatever reason it was blocking in the first place, no longer applies. (you might just be part of an entire IP range block, so don’t take it personally)

4) Sometimes a data-center will block your outbound port 443.  We have a work-around to allow the get License to download the license using port 80.  To enable this mode, please type:

echo 1 > /root/.insecure_download

and run the getLicense.sh script again.

5) Removed N/A.

6) The last possible is that you are running on a LAN instead of the requiring external IP.