TruCluster
Showing results for 
Search instead for 
Do you mean 

problem with the ASE in 4 members cluster system

Frequent Advisor

problem with the ASE in 4 members cluster system

dear all
The system is running with oracle parallel database 7.3.4, and currently it is a production server, many users are connected now

No problem is noticed from connection, no symptoms of the below problem



When running asemgr,



# asemgr

can't talk to agent!

#

# asemgr â H â ¦. To list cluster members of same ASE

can't talk to agent!

Unable to connect to agent/director

#





On mc-billSVR0 console ( Cluster Director), hereunder messages as an effect of trying to start asemgr on the new mc-billSVR3.



Jul 27 12:08:48 billSVR0 ASE: local AseLogger ***ALERT: ***Possible security breach attempt: connect request from non-member 'billSVR3'

Jul 27 12:08:48 billSVR0 ASE: local AseLogger Notice: connection refused by connect callback

Jul 27 12:08:48 billSVR0 ASE: mc-billSVR3 Agent ***ALERT: ***Possible security breach attempt: connect request from non-member node 'billSVR3'

Jul 27 12:08:48 billSVR0 ASE: mc-billSVR3 Agent Notice: connection refused by connect callback



Another point: when running Cluster Monitor (Graphics) on any member , the original 3 members are shown with their services attached to them, but the fourh (ES40) itâ s service appears without member icon for mc-BILLSVR3 as for other members.
2 REPLIES
Honored Contributor

Re: problem with the ASE in 4 members cluster system


Mahdi,

The symptoms point to billSRV3 having another ASE_ID (see /etc/rc.config) than the rest of the cluster. If not you migth have an asecdb corruption.

What output do you get from clu_ivp and from /usr/sbin/drd_ivp -p -v ?

__Johan__

_JB_
Honored Contributor

Re: problem with the ASE in 4 members cluster system

is this the cluster with the previous "funny" configuration?

Try clu_ivp -v to verify proper cluster setup (and as a starter).

Have you changed the hostname or ip within the cluster, if so this problem is typically for not properly made configuration changes.

Easiest way is to open a call within the HP support center asking for assistent. It seems your configuration is screwed up and correction can not be done within a forum for such complex task.

The cluster manual contains a troubleshooting section with all necessary steps (checking daemons, settings etc.) so give it a try it will answer all questions regarding troubleshooting a cluster.

Btw. hostnames with upper/lowercase are problematically (see RFC).
Help() { FirstReadManual(urgently); Go_to_it;; }
//Add this to "OnDomLoad" event