07-21-2018
You said you want the MTBF for each node. The node 127.0.0.1 was always down (for all three times it appeared in the data in post #4 and for both times it appeared in the data in post #1).
If a node is never up, isn't the mean time between failures zero? What value were you expecting?
This User Gave Thanks to Don Cragun For This Post:
6 More Discussions You Might Find Interesting
1. Virtualization and Cloud Computing
Hear how the changing needs of massive scale-out computing is driving a transfomation in technology and learn how HP is supporting this new evolution of the web.
More... (1 Reply)
Discussion started by: Linux Bot
1 Replies
2. HP-UX
What are the server requirements, Software requirements, Network requirements etc,
Please help me.. as 'm new 'm unable to get things done @ my end alone.
Please refrain from typing subjects completely in upper case letters to get more attention, ty. (5 Replies)
Discussion started by: Sounddappan
5 Replies
3. Red Hat
Hi,
We are having many RedHat linux Server with Cluster facility for availability of service like HTTPD / MySQL.
We face some issue while some issue related to power disturbance / fluctuation or Network failure. There is two Cluster Node configured in... (0 Replies)
Discussion started by: hirenkmistry
0 Replies
4. What is on Your Mind?
Three days ago we received an expected notice from our long time data center that they were going dark on Sept 12th.
About one and a half hours ago, after three days of marathon work, I just cut over the unix.com to a new data center with a completely new OS and Ubuntu distribution. (22 Replies)
Discussion started by: Neo
22 Replies
5. What is on Your Mind?
Dear All,
There was a problem in the data center data, which caused the server to be unreachable for about an hour.
Server logs show the server did not crash or go down.
Hence, I assume there was a networking issue at the data center.
Still waiting for final word on what happened.
... (4 Replies)
Discussion started by: Neo
4 Replies
6. What is on Your Mind?
There was a problem with our data center today, creating a site outage (server unreachable).
That problem has been resolved.
Basically, it seems to have been a socially engineered denial-of-service attack against UNIX.com; which I stopped as soon as I found out what the problem was.
Total... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT CENTOS
crm_node
PACEMAKER(8) System Administration Utilities PACEMAKER(8)
NAME
Pacemaker - Part of the Pacemaker cluster resource manager
SYNOPSIS
crm_node command [options]
DESCRIPTION
crm_node - Tool for displaying low-level node information
OPTIONS
-?, --help
This text
-$, --version
Version information
-V, --verbose
Increase debug output
-Q, --quiet
Essential output only
Stack:
-A, --openais
Only try connecting to an OpenAIS-based cluster
-H, --heartbeat
Only try connecting to a Heartbeat-based cluster
Commands:
-n, --name
Display the name used by the cluster for this node
-N, --name-for-id=value
Display the name used by the cluster for the node with the specified id
-e, --epoch
Display the epoch during which this node joined the cluster
-q, --quorum
Display a 1 if our partition has quorum, 0 if not
-l, --list
Display all known members (past and present) of this cluster (Not available for heartbeat clusters)
-p, --partition
Display the members of this partition
-i, --cluster-id
Display this node's cluster id
-R, --remove=value
(Advanced) Remove the (stopped) node with the specified name from Pacemaker's configuration and caches
In the case of Heartbeat, CMAN and Corosync 2.0, requires that the node has already been removed from the underlying cluster
Additional Options:
-f, --force
AUTHOR
Written by Andrew Beekhof
REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org
Pacemaker 1.1.10-29.el7 June 2014 PACEMAKER(8)