2007-06-12 07:44:01 +04:00
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
<refentry id= "onnode.1" >
<refmeta >
<refentrytitle > onnode</refentrytitle>
<manvolnum > 1</manvolnum>
2009-12-08 14:28:38 +03:00
<refmiscinfo class= "source" > </refmiscinfo>
<refmiscinfo class= "manual" > </refmiscinfo>
2007-06-12 07:44:01 +04:00
</refmeta>
<refnamediv >
<refname > onnode</refname>
<refpurpose > run commands on ctdb nodes</refpurpose>
</refnamediv>
<refsynopsisdiv >
<cmdsynopsis >
2008-07-10 08:19:52 +04:00
<command > onnode [OPTION] ... NODES COMMAND ...</command>
2007-06-12 07:44:01 +04:00
</cmdsynopsis>
</refsynopsisdiv>
<refsect1 > <title > DESCRIPTION</title>
<para >
onnode is a utility to run commands on a specific node of a CTDB
cluster, or on all nodes.
</para>
<para >
2008-09-12 12:20:52 +04:00
The NODES option specifies which node to run a command on. You
can specify a numeric node number (from 0 to N-1) or a
descriptive node specification (see DESCRIPTIVE NODE
SPECIFICATIONS below). You can also specify lists of nodes,
separated by commas, and ranges of numeric node numbers,
separated by dashes. If nodes are specified multiple times then
the command will be executed multiple times on those nodes. The
order of nodes is significant.
2007-06-12 07:44:01 +04:00
</para>
<para >
The COMMAND can be any shell command. The onnode utility uses
ssh or rsh to connect to the remote nodes and run the command.
2008-09-12 12:20:52 +04:00
</para>
</refsect1>
<refsect1 > <title > DESCRIPTIVE NODE SPECIFICATIONS</title>
<para >
The following descriptive node specification can be used in
place of numeric node numbers:
</para>
<variablelist >
<varlistentry > <term > all</term>
<listitem >
<para >
All nodes.
</para>
</listitem>
</varlistentry>
2009-09-15 13:33:35 +04:00
<varlistentry > <term > any</term>
<listitem >
<para >
A node where ctdbd is running. This semi-random but
there is a bias towards choosing a low numbered node.
</para>
</listitem>
</varlistentry>
2008-09-12 12:20:52 +04:00
<varlistentry > <term > ok | healthy</term>
<listitem >
<para >
All nodes that are not disconnected, banned, disabled or
unhealthy.
</para>
</listitem>
</varlistentry>
<varlistentry > <term > con | connected</term>
<listitem >
<para >
All nodes that are not disconnected.
</para>
</listitem>
</varlistentry>
2009-05-11 08:14:11 +04:00
<varlistentry > <term > lvs | lvsmaster</term>
<listitem >
<para >
The current LVS master.
</para>
</listitem>
</varlistentry>
<varlistentry > <term > natgw | natgwlist</term>
<listitem >
<para >
The current NAT gateway.
</para>
</listitem>
</varlistentry>
2008-09-12 12:20:52 +04:00
<varlistentry > <term > rm | recmaster</term>
<listitem >
<para >
The current recovery master.
</para>
</listitem>
</varlistentry>
</variablelist>
2008-07-10 08:19:52 +04:00
</refsect1>
<refsect1 > <title > OPTIONS</title>
<variablelist >
<varlistentry > <term > -c</term>
<listitem >
<para >
2008-07-11 09:05:41 +04:00
Execute COMMAND in the current working directory on the
specified nodes.
2008-07-10 08:19:52 +04:00
</para>
</listitem>
</varlistentry>
2009-05-11 08:14:11 +04:00
<varlistentry > <term > -o < prefix> </term>
<listitem >
<para >
Causes standard output from each node to be saved into a
file with name < prefix> .< ip> .
</para>
</listitem>
</varlistentry>
2008-07-10 08:19:52 +04:00
<varlistentry > <term > -p</term>
<listitem >
<para >
2008-07-11 09:05:41 +04:00
Run COMMAND in parallel on the specified nodes. The
default is to run COMMAND sequentially on each node.
2008-07-10 08:19:52 +04:00
</para>
</listitem>
</varlistentry>
<varlistentry > <term > -q</term>
<listitem >
<para >
Do not print node addresses. Normally, onnode prints
informational node addresses if more than one node is
specified. This overrides -v.
</para>
</listitem>
</varlistentry>
2009-10-22 10:47:10 +04:00
<varlistentry > <term > -n</term>
<listitem >
<para >
Allow nodes to be specified by name rather than node
numbers. These nodes don't need to be listed in the nodes
file. You can avoid the nodes file entirely by combining
this with <code > -f /dev/null</code> .
</para>
</listitem>
</varlistentry>
<varlistentry > <term > -f < file> </term>
<listitem >
<para >
2010-02-05 07:30:39 +03:00
Specify an alternative nodes file to use instead of the
default. This option overrides the CTDB_NODES_FILE
environment variable. See the discussion of
<filename > /etc/ctdb/nodes</filename> in the FILES section
for more details.
2009-10-22 10:47:10 +04:00
</para>
</listitem>
</varlistentry>
2008-07-10 08:19:52 +04:00
<varlistentry > <term > -v</term>
<listitem >
<para >
Print a node addresses even if only one node is specified.
Normally, onnode prints informational node addresses when
more than one node is specified.
</para>
</listitem>
</varlistentry>
<varlistentry > <term > -h, --help</term>
<listitem >
<para >
Show a short usage guide.
</para>
</listitem>
</varlistentry>
</variablelist>
2007-06-12 07:44:01 +04:00
</refsect1>
<refsect1 > <title > EXAMPLES</title>
<para >
The following command would show the process ID of ctdb on all nodes
2008-07-10 08:19:52 +04:00
</para>
<screen format= "linespecific" >
onnode all pidof ctdbd
</screen>
2007-06-12 07:44:01 +04:00
<para >
The following command would show the last 5 lines of log on each
2008-07-10 08:19:52 +04:00
node, preceded by the node's hostname
</para>
<screen format= "linespecific" >
onnode all "hostname; tail -5 /var/log/log.ctdb"
</screen>
2007-06-12 07:44:01 +04:00
<para >
The following command would restart the ctdb service on all nodes.
2008-07-10 08:19:52 +04:00
</para>
<screen format= "linespecific" >
onnode all service ctdb restart
</screen>
2007-06-12 07:44:01 +04:00
2008-07-10 08:19:52 +04:00
<para >
The following command would run ./foo in the current working
directory, in parallel, on nodes 0, 2, 3 and 4.
</para>
<screen format= "linespecific" >
onnode -c -p 0,2-4 ./foo
</screen>
</refsect1>
2009-10-06 06:38:00 +04:00
<refsect1 > <title > ENVIRONMENT</title>
<variablelist >
<varlistentry > <term > <envar > CTDB_NODES_FILE</envar> </term>
<listitem >
<para >
2010-02-05 07:30:39 +03:00
Name of alternative nodes file to use instead of the
default. See the discussion of
<filename > /etc/ctdb/nodes</filename> in the FILES section
for more details.
2009-10-06 06:38:00 +04:00
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
2008-07-10 08:19:52 +04:00
<refsect1 > <title > FILES</title>
<variablelist >
2009-10-06 06:38:00 +04:00
<varlistentry > <term > <filename > /etc/ctdb/nodes</filename> </term>
2008-07-10 08:19:52 +04:00
<listitem >
<para >
2009-10-06 06:38:00 +04:00
Default file containing a list of each node's IP address
or hostname.
2008-07-10 08:19:52 +04:00
</para>
2010-02-05 07:30:39 +03:00
<para >
Actually, the default is
<filename > $<envar > CTDB_BASE</envar> /nodes</filename> ,
where <envar > $CTDB_BASE</envar> defaults to
<filename > /etc/ctdb</filename> . If a relative path is
given (via the -f option or <envar > $CTDB_BASE</envar> ) and
no corresponding file exists relative to the current
directory then the file is also searched for in the
<filename > $<envar > CTDB_BASE</envar> </filename> directory.
</para>
2008-07-10 08:19:52 +04:00
</listitem>
</varlistentry>
2009-10-06 06:38:00 +04:00
<varlistentry > <term > <filename > /etc/ctdb/onnode.conf</filename> </term>
2008-07-10 08:19:52 +04:00
<listitem >
<para >
If this file exists it is sourced by onnode. The main
purpose is to allow the administrator to set $SSH to
something other than "ssh". In this case the -t option is
ignored. For example, the administrator may choose to use
use rsh instead of ssh.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
2007-06-12 07:44:01 +04:00
<refsect1 > <title > SEE ALSO</title>
<para >
ctdbd(1), ctdb(1), <ulink url= "http://ctdb.samba.org/" />
</para>
</refsect1>
<refsect1 > <title > COPYRIGHT/LICENSE</title>
<literallayout >
Copyright (C) Andrew Tridgell 2007
Copyright (C) Ronnie sahlberg 2007
2008-07-10 08:19:52 +04:00
Copyright (C) Martin Schwenke 2008
2007-06-12 07:44:01 +04:00
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
2007-07-10 09:29:31 +04:00
the Free Software Foundation; either version 3 of the License, or (at
2007-06-12 07:44:01 +04:00
your option) any later version.
This program 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
2007-07-10 09:46:05 +04:00
along with this program; if not, see http://www.gnu.org/licenses/.
2007-06-12 07:44:01 +04:00
</literallayout>
</refsect1>
</refentry>