Oracle Cluster Ready Services waiting for SunCluster on x86 to start
Recently i faced problem starting oracle application on my galaxy cluster on one node.In the log i found that the CRS demon was not started after the booting of the node , so i manually tried to start it but faced some error.
So here are the work around that i had done and the CRS services got started .
The error i was getting while starting oracle is
======================
PRKC-1056 : Failed to get the hostname for node galclus157
PRKH-1010 : Unable to communicate with CRS services.
[Communications Error(Native: prsr_initCLSS:[3])]
======================
When i tried to start the crsd manually the service did not started .
Then after debugging this error i found that the crs service depends on the ucmmd service to start .
So please check if this is already running or not (If not start it)
===================================
root@syscl055 # ps -aef | grep ucmmd
root 2030 1 0 May 12 ? 13:12 ucmmd -r /usr/cluster/lib/ucmm/ucmm_reconf
===================================
Hi,
I just started working on a script. After my research, i found a command which can help me:
AIM: To build a script which starts the services (Services 1) on server 1 automatically whenever its down. And it has a dependency on other service (Service 2) on Server 2.
So my script has to... (4 Replies)
Hi all,
I remember way back in some old environment, having the HA cluster services not being started automatically at startup, ie. no entry in /etc/inittab.
I remember reason was (taken a 2 node active/passive cluster), to avoid having a backup node being booted, so that it will not... (4 Replies)
Hello,
I'm attempting to use the DDD program. After launching it from the shell I try to set a breakpoint on a source code file and when I click run it hangs and says Waiting until GDB gets ready. I cannot do anything inside the program except quit (and even that takes a while). Can someone tell... (3 Replies)
Hey Admins,
I am running sun cluster 3.2 x86 on Vmware. I m facing an issue from 2 days..
One main node is continuously rebooting..... not sure... whats woring...
I just had change heartbeat timeout values on 1 this node... Now both node are just rebooting itself..seems panic..
Any... (1 Reply)
have a pair of sun servers, wanting to test drive a
2-node cluster using both software..
would like disable one of these cluster software while the othe is running..
Is it feasible at all ?? (2 Replies)
NDB_WAITER(1) MySQL Database System NDB_WAITER(1)NAME
ndb_waiter - wait for MySQL Cluster to reach a given status
SYNOPSIS
ndb_waiter options
DESCRIPTION
ndb_waiter repeatedly (each 100 milliseconds) prints out the status of all cluster data nodes until either the cluster reaches a given
status or the --timeout limit is exceeded, then exits. By default, it waits for the cluster to achieve STARTED status, in which all nodes
have started and connected to the cluster. This can be overridden using the --no-contact and --not-started options.
The node states reported by this utility are as follows:
o NO_CONTACT: The node cannot be contacted.
o UNKNOWN: The node can be contacted, but its status is not yet known. Usually, this means that the node has received a START or RESTART
command from the management server, but has not yet acted on it.
o NOT_STARTED: The node has stopped, but remains in contact with the cluster. This is seen when restarting the node using the management
client's RESTART command.
o STARTING: The node's ndbd process has started, but the node has not yet joined the cluster.
o STARTED: The node is operational, and has joined the cluster.
o SHUTTING_DOWN: The node is shutting down.
o SINGLE USER MODE: This is shown for all cluster data nodes when the cluster is in single user mode.
The following table includes options that are specific to the MySQL Cluster native backup restoration program ndb_waiter. Additional
descriptions follow the table. For options common to most MySQL Cluster programs (including ndb_waiter), see Options Common to MySQL
Cluster Programs(1).
Table 17.28. ndb_waiter Options and Variables: MySQL Cluster NDB 7.2
+---------------------------+--------------------------------------+-------------------------------------+
|Format | Description | Added / Removed |
+---------------------------+--------------------------------------+-------------------------------------+
| | Wait for cluster to reach NO CONTACT | |
| --no-contact, | state | All MySQL 5.5 based releases |
| | | |
| -n | | |
+---------------------------+--------------------------------------+-------------------------------------+
| | Wait for cluster to reach NOT | |
| --not-started | STARTED state | All MySQL 5.5 based releases |
+---------------------------+--------------------------------------+-------------------------------------+
| | Wait for cluster to enter single | |
| --single-user | user mode | All MySQL 5.5 based releases |
+---------------------------+--------------------------------------+-------------------------------------+
| | Wait this many seconds, then exit | |
| --timeout=#, | whether or not cluster has reached | All MySQL 5.5 based releases |
| | desired state; default | |
| -t | is 2 minutes (120 seconds) | |
+---------------------------+--------------------------------------+-------------------------------------+
| | List of nodes not to be waited for. | |
| --nowait-nodes=list | | All MySQL 5.5 based releases |
+---------------------------+--------------------------------------+-------------------------------------+
| | List of nodes to be waited for. | |
| --wait-nodes=list, | | All MySQL 5.5 based releases |
| | | |
| -w | | |
+---------------------------+--------------------------------------+-------------------------------------+
Usage
ndb_waiter [-c connect_string]
Additional Options
o --no-contact, -n
Instead of waiting for the STARTED state, ndb_waiter continues running until the cluster reaches NO_CONTACT status before exiting.
o --not-started
Instead of waiting for the STARTED state, ndb_waiter continues running until the cluster reaches NOT_STARTED status before exiting.
o --timeout=seconds, -t seconds
Time to wait. The program exits if the desired state is not achieved within this number of seconds. The default is 120 seconds (1200
reporting cycles).
o --single-user
The program waits for the cluster to enter single user mode.
o --nowait-nodes=list
When this option is used, ndb_waiter does not wait for the nodes whose IDs are listed. The list is comma-delimited; ranges can be
indicated by dashes, as shown here:
shell> ndb_waiter --nowait-nodes=1,3,7-9
Important
Do not use this option together with the --wait-nodes option.
o --wait-nodes=list, -w list
When this option is used, ndb_waiter waits only for the nodes whose IDs are listed. The list is comma-delimited; ranges can be
indicated by dashes, as shown here:
shell> ndb_waiter --wait-nodes=2,4-6,10
Important
Do not use this option together with the --nowait-nodes option.
Sample Output. Shown here is the output from ndb_waiter when run against a 4-node cluster in which two nodes have been shut down and then
started again manually. Duplicate reports (indicated by "...") are omitted.
shell> ./ndb_waiter -c localhost
Connecting to mgmsrv at (localhost)
State node 1 STARTED
State node 2 NO_CONTACT
State node 3 STARTED
State node 4 NO_CONTACT
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 UNKNOWN
State node 3 STARTED
State node 4 NO_CONTACT
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 STARTING
State node 3 STARTED
State node 4 NO_CONTACT
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 STARTING
State node 3 STARTED
State node 4 UNKNOWN
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 STARTING
State node 3 STARTED
State node 4 STARTING
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 STARTED
State node 3 STARTED
State node 4 STARTING
Waiting for cluster enter state STARTED
...
State node 1 STARTED
State node 2 STARTED
State node 3 STARTED
State node 4 STARTED
Waiting for cluster enter state STARTED
NDBT_ProgramExit: 0 - OK
Note
If no connection string is specified, then ndb_waiter tries to connect to a management on localhost, and reports Connecting to mgmsrv
at (null).
COPYRIGHT
Copyright (C) 1997, 2014, Oracle and/or its affiliates. All rights reserved.
This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as
published by the Free Software Foundation; version 2 of the License.
This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation,
Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/.
SEE ALSO
For more information, please refer to the MySQL Reference Manual, which may already be installed locally and which is also available online
at http://dev.mysql.com/doc/.
AUTHOR
Oracle Corporation (http://dev.mysql.com/).
MySQL 5.5 01/30/2014 NDB_WAITER(1)
