PDA

View Full Version : Error during installation on CentOS



firejake
05-04-2011, 12:55 PM
cat /etc/redhat-release
CentOS release 5.6 (Final)



yum install bison
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: ftp.tlk-l.net
* extras: ftp.tlk-l.net
* updates: ftp.tlk-l.net
Setting up Install Process
Package bison-2.3-2.1.i386 already installed and latest version
Nothing to do


but:


cat: /etc/rc.conf: Не******** ********а********ого ********а****************а ************************ ********а********а********ога
*** bison is required for compiling, please install bison ***
Installation didn't pass, halting install.



What do I do if bison is installed but directadmin not want to install? Help!

scsi
05-04-2011, 01:26 PM
Read the install guide on directadmin.com for what is required.

zEitEr
05-04-2011, 01:27 PM
I've never seen /etc/rc.conf on CentOS, isn't it FreeBSD based only? Why do you need it on CentOS?

firejake
05-04-2011, 01:44 PM
Read the install guide on directadmin.com for what is required.

I read the installation manual. There's nothing about such is not described.


I've never seen /etc/rc.conf on CentOS, isn't it FreeBSD based only? Why do you need it on CentOS?
I did not tell him how to read files. This applies not only to FreeBSD, but all the * BSD too.





In general, I would like to get a concise answer about this error, as well as setod its decision. Thanks.

SeLLeRoNe
05-05-2011, 12:53 AM
Is your license set for CentOS System?

firejake
05-05-2011, 12:58 AM
But what really needs to be purchased only under a license specific operating system and address? What a silly question. Of course the same, as well as IP-address and host name.

zEitEr
05-05-2011, 01:18 AM
OK, now it seems I get what you mean, but it was not that clear after first reading.

Post here results for


# uname
# whereis bison

It's important to see exaclty that output of uname, not of cat /etc/redhat-release. Because directadmin's setup.sh uses uname to detect OS type.

SeLLeRoNe
05-05-2011, 01:19 AM
DirectAdmin license is based on OS and IP, so, when installation start the script check your license and the OS assigned to the license and start installation for that OS, thats why ive asked... Is not so stupid question at my point of view.


Another stupid question, are the path in environment correct?

Regards

zEitEr
05-05-2011, 01:36 AM
Sorry to say, but not all that's true. Directadmin setup script do not check LICENSE untill all dependencies are installed. So it uses system tools to determine OS type and other things:


OS=`uname`;

only then


OS_VER=`cat /etc/redhat-release | cut -d\ -f7`

only then


$BIN_DIR/wget $WGET_OPTION -O $DA_PATH/update.tar.gz --bind-address=$IP https://www.directadmin.com/cgi-bin/daupdate?uid=$CID\&lid=$LID

In the long run LICENSE is checked only when you start Directadmin daemon.

SeLLeRoNe
05-05-2011, 01:46 AM
Yes you right my fault. But aswell before install he check if the license match the OS no?

zEitEr
05-05-2011, 01:59 AM
As far as I'm concerned, no, that is not checked. A lot threads on the forums are saying about, that they can not start directadmin after installation. And the most frequent problem is mismatched OS type.

SeLLeRoNe
05-05-2011, 02:17 AM
I see, well... i remember bad so :)

So, you can ignore my suggestions about LIC ^^

Regards

firejake
05-10-2011, 12:52 AM
*********************
uname -a
Linux srv1.**.ru 2.6.18-238.9.1.el5 #1 SMP Tue Apr 12 18:10:13 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

zEitEr
05-10-2011, 12:55 AM
whereis bison ???

firejake
05-10-2011, 02:48 AM
whereis bison ???

# whereis bison
bison: /usr/bin/bison /usr/share/bison /usr/share/man/man1/bison.1.gz

zEitEr
05-10-2011, 03:13 AM
I've scanned setup.sh and install.sh and have not found anything of your messages:


cat: /etc/rc.conf: Не******** ********а********ого ********а****************а ************************ ********а********а********ога
*** bison is required for compiling, please install bison ***
Installation didn't pass, halting install.

Where did you get it? If this message appeared within directadmin installation (you executed directadmin setup.sh), please post some more 10-50 lines prior to these.

firejake
05-10-2011, 03:23 AM
I've scanned setup.sh and install.sh and have not found anything of your messages:



Where did you get it? If this message appeared within directadmin installation (you executed directadmin setup.sh), please post some more 10-50 lines prior to these.
This message appears when you run the file ./install.sh

scsi
05-10-2011, 07:30 AM
What is install.sh?

toml
05-10-2011, 08:03 AM
install.sh should only be called from the DA setup.sh script.

Also, have you carefully followed the install steps from http://www.directadmin.com/installguide.html?

firejake
05-10-2011, 09:29 AM
How did you got the wild dog with his scouts. Of course I'm doing everything clearly on the instructions, if otherwise I would have no meaning to write. Can you recommend a valid option?

toml
05-10-2011, 09:41 AM
How did you got the wild dog with his scouts. Of course I'm doing everything clearly on the instructions, if otherwise I would have no meaning to write. Can you recommend a valid option?

Don't know anything about wild dogs, but you would be surprised how many people have no clue about system administration yet still insist on running a web host. DA, Cpanel, etc all make it easier to manage web hosts, but they do not replace knowing basic systems administration tasks.

I did a grep in all the install scripts and I see nowhere in them where they may be doing a cat of /etc/rc.conf, and they should not be on a CentOS host.

If this were me (I happen to be a software engineer by profession), I would throw some 'set -x' in some of the suspect install scripts and debug where it is going wrong. Of course that assumes you know something about shell scripting and know whate the various files on the host do.

I do see a check for bison it is doing a 'if [ ! -e /usr/bin/bison ]' so if it is installed and in that location it shouldn't fail.

Of course it would help to see the full output of your install attempt.