Server Clustering
cancel
Showing results for 
Search instead for 
Did you mean: 

CMU installation problem

Towhid
Occasional Visitor

CMU installation problem

WE have a cluster with 8 BL465c server. I tried to make the blade 1 as a master node and install CMU on it. However, when I try to start the CMU it gives a message "failed configuring (audit mode)" Even in the the dchpd, it shows "no cmu header" Could anyone help in this reagrd?
4 REPLIES
viollet
Occasional Visitor

Re: CMU installation problem

Hello,

As stated is CMU manual, after installation CMU starts in audit mode (to allow easy HA configuration).
Please type
/etc/init.d/cmu unset_audit

and restart your CMU service

/etc/init.d/cmu restart

Towhid
Occasional Visitor

Re: CMU installation problem

Your solution does not work. Basically, there is a problem in the cmuserver script. It checks the java version with a fixed string "1.6.0". However, my version is 1.6.0_17. That creates the problem. I edited the script. It works fine.
Dennis Gurgul
Occasional Contributor

Re: CMU installation problem

I'm having a similar problem with similar lines regarding java. I tried editing the line grep -q -e '"1.6' $java_tmp ; javaVersion=$? to grep -q -e '"1.6.0_17' $java_tmp ; javaVersion=$? in cmuserver but still get the same failure. I'm not sure java's the problem but it's the only info sent to the screen other than the lines about "failed config", "not running", etc.

Is there other editing that's needed in cmuserver? I also have java version "1.6.0_17".

Thanks

Re: CMU installation problem

Hello,

It sounds like you have a java version problem. CMU requires Sun/Oracle java. Most Linux distributions come with an open-source version of java, like this:

[root@node14 ~]# java -version
java version "1.6.0"
OpenJDK Runtime Environment (build 1.6.0-b09)
OpenJDK 64-Bit Server VM (build 1.6.0-b09, mixed mode)
[root@node14 ~]#

Note that even after you install the Sun/Oracle version of java, your path may still be configured to find the open-source version:

[root@node14 ~]# rpm -ivh jre-6u11-linux-amd64.rpm
Preparing... ########################################### [100%]
1:jre ########################################### [100%]
Unpacking JAR files...
rt.jar...
jsse.jar...
charsets.jar...
localedata.jar...
[root@node14 ~]# java -version
java version "1.6.0"
OpenJDK Runtime Environment (build 1.6.0-b09)
OpenJDK 64-Bit Server VM (build 1.6.0-b09, mixed mode)
[root@node14 ~]#

This occurs because the 'alternatives' package is managing your 'java' link:

[root@node14 ~]# ls -l `which java`
lrwxrwxrwx 1 root root 22 Jun 6 10:46 /usr/bin/java -> /etc/alternatives/java
[root@node14 ~]#
[root@node14 ~]# alternatives --display java
java - status is auto.
link currently points to /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java
/usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java - priority 16000
...

To fix this, you need to add the Sun/Oracle java binary to the 'alternatives' management system with a higher priority than the open-source version. First find out where Sun/Oracle installed java:

[root@node14 ~]# rpm -ql jre | tail -n1
/usr/java/jre1.6.0_11/man/man1/unpack200.1

Then use the alternatives command to configure this new java version:

[root@node14 ~]# alternatives --install /usr/bin/java java /usr/java/jre1.6.0_11/bin/java 17000

Finally, confirm that your default java version is now Sun/Oracle:

[root@node14 ~]# java -version
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode)
[root@node14 ~]#