Error during setup.sh on Centos 4 VPS

D

David C

Verified User
Joined
Mar 10, 2006
Messages
74
Hi,

I'm installing DA on one of my VPS instance.

It is running on Centos 4.5.

Everything seem to install smoothly until the end, where I get the following error. I'm stuck now. I've been googling for the error, and I can't find anything.

Does this look familiar to anyone?

Code: 
Setting the suidkey...
Creating we80.cnf...
Done.  Frontpage Extension install complete.




*************************************
*                                   *
*   All parts have been installed   *
*                                   *
*************************************

Type: /sbin/service httpd restart
cp: `/var/www/html/squirrelmail/data' and `/var/www/html/squirrelmail-1.4.10a/data' are the same file
./install.sh: line 220: 11584 Floating point exception./directadmin i
./install.sh: line 223: 11585 Floating point exception./directadmin p
 
yup, unfortunately, this does look familiar.. have you found a solution already?

installing on a dedicated server: Dual Core Xeon 3050 with CentOS 4.5
 
Installation errors should be reported to DirectAdmin support as they may require a change in the installation script.

Look here.

Jeff
 
Hello,

The usual cause of the directadmin binary not working is due to OS mismatches. Escpeically with vps's systems, we run into wrong OS's being selected from time to time.... sometimes the binaries need to be set to the OS of the vps itself, and other times the binaries need to be set to the value of the server's OS that runs those vps's.

Type:

cat /etc/redhat-release

cat /proc/version

and see what it says. Compare that to the OS that's setup in your license file in your DirectAdmin clients section. They need to match.

Other times, the vps is just a little bit "too" virtual, and wont run the binaries.


If it's a 4.5 system, you can also try the 4.x binaries, because they're statically compiled.
The 4.4 binaries are dynamicly compiled for 4.4, so running dynamic binaries for 4.4 may have problems on 4.5.. where the 4.x (4.1 static) might have a better chance. This is usually requires some trial and error to figure out though.

John
 
DirectAdmin Support said:
Hello,

The usual cause of the directadmin binary not working is due to OS mismatches. Escpeically with vps's systems, we run into wrong OS's being selected from time to time.... sometimes the binaries need to be set to the OS of the vps itself, and other times the binaries need to be set to the value of the server's OS that runs those vps's.

Type:

cat /etc/redhat-release

cat /proc/version

and see what it says. Compare that to the OS that's setup in your license file in your DirectAdmin clients section. They need to match.

Other times, the vps is just a little bit "too" virtual, and wont run the binaries.

John
Click to expand...

Thanks for your reply.
I don't own the license myself, I'm leasing it from my (dedicated) server provider, so I can't look into it, but I guess it's the right version.

my /etc/redhat-release contains:
CentOS release 4.5 (Final)

and /proc/version gives:
Linux version 2.6.9-55.0.2.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-8)) #1 SMP Tue Jun 26 14:30:58 EDT 2007

Maybe you can look into the license for me? (edit: I mailed you with my license details)
 
Last edited:
DirectAdmin Support said:
Hello,
(...)
If it's a 4.5 system, you can also try the 4.x binaries, because they're statically compiled.
The 4.4 binaries are dynamicly compiled for 4.4, so running dynamic binaries for 4.4 may have problems on 4.5.. where the 4.x (4.1 static) might have a better chance. This is usually requires some trial and error to figure out though.

John
Click to expand...

How should I trial-and-error doing that?
 
For everyone who accidentally passes this topic in a Google search after a year or so, like I did: my license was configured for CentOS 5 while I used CentOS 4.5. Long story short: that's a mismatch.
Editing one of these, that is editing the license to use CentOS 4.x (which I did at first) or upgrading/reinstalling my OS to CentOS 5 (which is my current OS on my server), will solve the problem.

This topic can be closed imo.
 
Did you install DirectAdmin? If so, then check to make sure you installed the same version as your server runs.

If not, then check with whomever supplied your DirectAdmin installation.

Jeff
 
You must log in or register to reply here.
Back
Top