ISPC3 on CentOS 5.5 64 Bit - Installation fails with Path Errors & DB not imported

Hi,

after having used ISPC2 for about 2 years now, I took the chance of a failed hard drive to give V3 a go now. I prepared a Installation closely following the Perfect Server SetUp, but the base system was installed by the Serverprovider, Server4You. The Firewall and SE Linux are switched off. Unfortunately I failed with several issues:

1) Starting ISPC Installation results in 22 Lines of following error:

(File or Folder not found)

2) If I go through anyway, at the End I was presended with the error, that the MySQL Data can not be imported. The Database is created correctly by ISPC.

3) On the Perfect Server Installation the SA-Update Command fails:

Now, looking around the Forum I found a couple of users who had the first issue and a common question back to those users was: what is the output of the "echo $PATH" command, which nobody seems to have answered, so I just append it here:

I take it there must be something missing, but currently I don't seem to be able to find out what. I tried Version ISPConfig-3.0.2.1 as well as ISPConfig-3.0.2.2

cheers

Klaus

 

sharing

Just want to share some of my experience.

I recently install my VPS with ISPConfig 3 on CentOS 5.5, it is similar to what u r doing. I also don't know the default install of the server. But I managed to run it with the help of people on this forum.

1. Are you sure you are using CentOS 5.5 64 bit? Because mine is 32 bit. If yours is 32 bit, then you must replace all file name containing x86_64 with i386.
2. If you're doing remove and reinstall of ISPConfig 3, don't forget to delete the dbispconfig in mysql after uninstall procedure. And also reboot after that. Because if not, the installer will say old database still exist and cannot continue.
3. Just to make sure we use the same way to install, I follow the guide from step 7-Install some software, there's no need to follow step 1-6 unless you have specific needs.
4. The only thing that was not installed on my default server is cron. If yours is the same, just do yum install vixie-cron

Ok, that's it from me. If still no result, you can view the install log to find the error.

 

Thanks for your comments on this, I appreciate you trying to help.

I am sure that I am running 64bit, also check the uname output:

I started the whole guide at page 3 with the addition of switching off Firewall and SELinux (on page 2). Actually I started a 3 times over by now, just to make sure I didn't make any errors. Just for good measure I will restore the server again to the CentOS 5.5 LAMP Image and start again.

I was mainly thinking, that those errors I found where also reported a couple of times here in the forum, so there should be a solution.

cheers again

Klaus

 

Seems perl-Archive-Tar version 1.39.1-1 is the culprit.

Edit your /usr/bin/sa-update and change

Code:

use Archive::Tar 1.23;

to

Code:

use Archive::Tar;

D.

 

Cheers for that, but it was "just" a byproduct recording this error in this post. I consider the other one(s) showstopper(s) and was hoping to get a solution there ...

cheers

Klaus

 

So ... I take it nobody is able to shed some light on these issues ... shame though.

cheers

Klaus

 

Will try to install CentOS 5.5 and try it in a virtual box.

D.

 

Well I just did the install on a CentOS 5.5 x64 and it worked flawlessly.

There is something else that makes me wonder.

Can you execute "which" on your machine to see whether 'which' is missing?

D.

 

Is available: /usr/bin/which

Anyway, I was hoping on the info from the path statement, because this was where all the others stopped asking for help ... could you post your paths output for a crosscheck?

cheers

Klaus

 

path

I'm using 32 bit, but the result seem almost the same:

/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

I think sa-update only for updating spamassasin, so it should not affecting the installation.

Maybe it's a permission problem. What user do you use, root or something else?

Why don't you try to check install log? It should be in /var/log/ispconfig3_install.log

 

User was root, the log file was not in the folder. Anyway, I gave up on ISPC3

cheers folks anyway

Klaus