ovstart — start NNM managed processes
ovstart [ [-c] [-d] [-o ovspmd_path] [-v]
[--][ovspmd_options...][managed_process_names...]]
ovstart starts NNM managed processes. If called with one
or more managed_process_name arguments, it starts the designated managed process
after first starting any other managed processes on which it depends. If
called with no arguments, it starts all the managed processes that
are configured to start by default.
ovstart does not exit until all the managed processes
it has tried to start have either responded or timed out (failed
to respond within the LRF-specified timeout interval). By default,
it produces no output unless a managed process fails. When you execute it
from the command line, it is advisable to use the
-c or
-v option to track the progress
of the operation. Running
ovstart again after the
successful completion of a previous attempt to ovstart is
completely harmless.
ovstart sends a start request (OVS_REQ_START) to the process management service, ovspmd. If ovspmd is not already running, ovstart starts it first.
ovstart must be run by the
administrator or super-user.
The managed processes are configured by ovaddobj from information in local registration files (see lrf(4)).
A managed process is named by the first field in the LRF describing
it.
If ovstart is used on a node configured for NNM clustering (see
nnmcluster(1M))
then the behavior of ovstart is different than described above.
Specifically, ovstart behaves exactly like the "nnmcluster -daemon" command.
In a NNM cluster environment ovstart returns immediately
(after launching the NNM cluster in the background).
Instead, the nnmcluster command will determine if/when to start the other NNM processes.
Please monitor ovstatus output to determine if NNM processes have completed startup.
In a NNM clustered environment the other command-line options to
ovstart are not supported.
Note that for fine-grain control of NNM cluster attributes use the nnmcluster command directly.
The ovstart command in a NNM cluster environment is provided for convenience starting NNM using a familiar command.
ovstart recognizes the following options. Any unrecognized
options are reported by a usage message.
-c
Produce one line of information about the success or failure of each managed process.
-d
Report the important stages in processing, including
starting, contacting, and sending the start request to ovspmd, and closing the communication channel.
-o ovspmd_path
Specifies that the executable for ovspmd is in ovspmd_path instead of in the default location,
. If install_dir\binovspmd is already running, this option is ignored.
-v
Produce several lines of information about the success or failure of each managed process.
- ovspmd_options
Any option not known by
ovstart is passed to
ovspmd. Since the
-d option is valid for
both programs, it will be interpreted as an
ovstart option, and
will not be passed on to
ovspmd. Likewise, the
-V option
will be passed to
ovspmd since it is not
valid for ovstart. If
an option is not recognized by either, a usage message
will be printed from
ovspmd, not
ovstart.
--
Terminates the options section of the
ovstart command
line. Any arguments following the comment token
(--) are interpreted as
names of managed processes to start, and passed to
ovspmd.
In a non NNM cluster environment ovstart exits with the
status representing the number of object managers from the start
list that were not started successfully. If
all requested managed processes were started successfully,
ovstart exits with the status
0 (zero).
In a NNM cluster environment ovstart
always exit immediately with the status 0 (zero).
ovstart reports certain
command-line errors (in particular, too many arguments) and
system errors. The messages are prefixed with
ovstart:, and are intended to
be self-explanatory. ovstart
also outputs error messages received from
ovspmd. These messages are
prefixed with
ovspmd:.
ovstart does not treat
unrecognized options as errors, but
ovspmd does.
Note that ovspmd can
process multiple requests
(ovstart,
ovstop, or
ovstatus) at a time. If any of
these commands is being handled, the new request will be queued
by type until the previous command has completed.
ovstart
Request ovspmd to start
all managed processes configured to start by default. If
ovspmd is not already running,
start it with no options. Only failures are reported.
ovstart -v -V -- ovjboss
Request ovspmd to start
the ovjboss process, which
results in starting the Jboss application server and all of the
NNM services that are deployed together within Jboss, after
first starting any other managed processes that the
ovjboss process depends on. If
ovspmd is not already running,
start it in verbose mode (-V
option). Report program startup, whether successful or not
(-v option). Note that the
comment token (--) option is
necessary so that ovstart does
not interpret ovjboss as an
argument to the unrecognized -V
option.
See the nnm.envvars
reference page (or the UNIX manpage) for information on using environment
variables for the following files:
install_dir\bin\ovstart
install_dir\bin\ovspmd
$LANG provides a default
value if the internationalization variables, LC_ALL, LC_CTYPE,
and LC_MESSAGES are unset,
null, or
invalid.
If $LANG is
unset,
null, or
invalid, the default value of
C (or
English_UnitedStates.1252 on
Windows) is used.
LC_ALL (or
$LANG) determines the locale
of all other processes started by
ovspmd.
LC_CTYPE determines the
interpretation of text as single-byte and/or multi-byte
characters, the classification of characters as printable, and
the characters matched by character class expressions in
regular expressions.
LC_MESSAGES determines
the language in which messages are displayed.
If ovstart is
executed, and no ovspmd
process is currently running,
ovspmd inherits the
environment of the executing shell. All managed processes
started by ovspmd inherit
this same environment.
To change the environment for
ovspmd or any managed
process, you must restart
ovspmd with the correct
environment. This requires that all managed processes be
stopped (ovspmd does not
terminate until all managed processes have been shut
down).
As a result, to change the environment for any managed
process started from
ovstart/ovspmd,
you must do the following:
Execute ovstop
with no arguments to shut down all managed processes and
ovspmd.
Set up the correct environment variables.
Execute ovstart
to restart ovspmd and
any or all managed processes.