12-20-2019
Could this be that whatever is supplying the common disk used to keep heartbeat failed? That way, both nodes would be unable to keep updating the shared disk and the usual response is to terminate all services to avoid getting in the way, i.e. to panic/abort. We've had a Oracle RAC database cluster do this before. not pretty, but it is the best course of action to avoid damage.
Robin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. HP-UX
hi friends,
i know that when there is a crash then that memory image is
put into /var/adm/crash
but if the system hangs up and if i have access to console of
that machine then how can i take the crash dump manully.
thanks (2 Replies)
Discussion started by: mxms755
2 Replies
3. Solaris
Can anyone of you help me in enabling crash dump on Solaris 5.5.1 (1 Reply)
Discussion started by: csreenivas
1 Replies
4. AIX
Hi Guys,
I have two nodes clustered. Each node is AIX 5.2 & they are clustered with HACMP 5.2. The mode of the cluster is Active/Passive which mean one node is the Active node & have all resource groups on it & the 2nd node is standby.
Last Monday I noted that all resource groupes have been... (2 Replies)
Discussion started by: aldowsary
2 Replies
5. Solaris
hi ,
i have machine that is crashed
how i can enable core dump file & how can i find it ? :confused: (4 Replies)
Discussion started by: lid-j-one
4 Replies
6. UNIX for Advanced & Expert Users
Hi.
I have started heartbeat on two redhat servers. Using eth0.
Before I start heartbeat I can ping the two server to each other.
Once I start heartbeat both the server become active as they both have warnings that the other node is dead.
Also I am not able to ping each other. After stopping... (1 Reply)
Discussion started by: amrita garg
1 Replies
7. AIX
Hi Guys,
I have to design a multinode hacmp cluster and am not sure if the design I am thinking of makes any sense.
I have to make an environment that currently resides on 5 nodes more resilient but I have the constrain of only having 4 frames. In addition the business doesnt want to pay for... (7 Replies)
Discussion started by: zxmaus
7 Replies
8. AIX
Hi
I had an active passive cluster. Node A went down and all resource groups moved to Node B.
Now we brought up Node A. What is the procedure to bring everything back to Node A.
Node A #lssrc -a | grep cl
clcomdES clcomdES 323782 active
clstrmgrES cluster... (9 Replies)
Discussion started by: samsungsamsung
9 Replies
9. HP-UX
Hi Experts,
I have configured HP-UX Service Guard cluster and it dumps crash every time i reboot a cluster node. Can anyone please help me to prevent these unnecessary crash dumps at the time of rebooting SG cluster node?
Thanks in advance.
Vaishey (2 Replies)
Discussion started by: Vaishey
2 Replies
10. OS X (Apple)
MacPro (2013) 12-Core, 64GB RAM (today's crash):
panic(cpu 2 caller 0xffffff7f8b333ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (318824 seconds ago): 31883, last successful... (3 Replies)
Discussion started by: Neo
3 Replies
cm(5) File Formats Manual cm(5)
NAME
cm - cluster monitor for high availability clusters
Remarks
Cluster operations require the installation of the optional Serviceguard or Serviceguard Extension for RAC software, which is not included
in the standard HP-UX operating system.
DESCRIPTION
Serviceguard and Serviceguard Extension for RAC are high availability products which provide an environment such that after a failure of a
node, services (applications) can be up and running again on another node within a very short amount of time. In addition, Serviceguard
Extension for RAC is the enabling software for the Real Application Clusters (RAC). Working with the basic Serviceguard product, Service-
guard Extension for Faster Failover allows configuration of clusters for optimized failover.
Commands
The following set of commands is used to configure a high availability cluster:
cmquerycl(1M)
cmmakepkg(1M)
cmcheckconf(1M)
cmapplyconf(1M)
The following commands are used to run or halt a cluster:
cmruncl(1M)
cmhaltcl(1M)
cmrunnode(1M)
cmhaltnode(1M)
cmviewcl(1M)
Once a cluster is formed, the following commands are provided for manual operation on high availability packages:
cmrunpkg(1M)
cmhaltpkg(1M)
cmmodpkg(1M)
The following commands are used within a package control script to control the services and networks configured for a package:
cmrunserv(1M)
cmhaltserv(1M)
cmmodnet(1M)
A command is provided to aid in migrating from a SwitchOver/UX configuration to a Serviceguard cluster:
cmmigrate(1M)
This command is not applicable with Serviceguard Extension for RAC.
SEE ALSO
Managing Serviceguard.
Configuring RAC Clusters with Serviceguard Extension for RAC.
Requires Optional Serviceguard Software cm(5)