Can't start DA

[frankie328]

today i install DA in RHEL4.0 , the OS is new installed
but after install DA, It have a error ,The DA can not start
how can i fix this problem


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

Type: /sbin/service httpd restart
./install.sh: line 204: ./directadmin: cannot execute binary file
./install.sh: line 207: ./directadmin: cannot execute binary file


service httpd restart
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
[root@xxx/]# service directadmin start
Starting DirectAdmin: /usr/local/directadmin/directadmin: /usr/local/directadmin/directadmin: cannot execute binary file

 

[nobaloney]

The best way to get problems such as these resolved is to contact DA support.

Jeff

 

[DirectAdmin Support]

Hello,

That would either be an incorrect OS selected in the license file (check your license in your DA client account), or a processor that is not supported (ie: Solaris, PowerPC, etc) Intel/AMD only!

cat /proc/cpuinfo

John

 

[galacnet]

I have this problem too...
I selected FC4 in the license... but I, in the end, still prefer RH9 and installed that instead...

and I got

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

Type: /sbin/service httpd restart
./directadmin: error while loading shared libraries: libssl.so.5: cannot open shared object file: No such file or directory
./directadmin: error while loading shared libraries: libssl.so.5: cannot open shared object file: No such file or directory


The installation does not work

 

[DirectAdmin Support]

Hello,

cat /etc/redhat-release

to check your OS version.

The DA binaries you download must be specified in your license file before you start the install.

When you run the installer, it asks for your OS, but that's only for the services pack, *not* the DA binaries.

Let us know if you need an OS change in your license.

John

 

[harro]

Argh! I had requested an OS change in the license, but started installing too soon. Just found out that it is indeed the OS in the license that determines which source files are retrieved by custombuild, not the OS where it is run.

Perhaps the latter would be more logical and fail-safe? Or a warning message stating that the license OS is leading and that if this is not yet confirmed, the install will fail?

There have not been very many people posting the same issue, but several. Of course there is some own responsibility too, just sharing my experience.

Harro

 

[sohaib]

I got the same problem DA Support never respond they should mentioned in their client area to change the OS Type instead of waiting for them and change the license OS Type, this is very wrong we should have this option to change the LICENSE OS TYPE, so we can install the DA on any OS type we want without having to beg them to change they do change but take way too long to respond, If I wanted to do some DA Installation I have to wait sometime 2 hours or 1 day so I can start my installation which is a complete nonsense. I am sorry but that what I feel like after my worst experience I had today . My servers are down just because I am waiting like an idiot to get an answer from DA support which is only two people Mark and John they can respond change my License OS Type so I can begin my installation.