CORBA 2.6.1 Administration Guide
Starting and Stopping NonStop Services for CORBA
Running nsdstart
Running nsdstop
Running nsdstart
Before running nsdstart, be sure the required environment variable settings are in effect.
To run the
nsdstart script, enter the following command at the OSS command prompt:
nsdstart
This command starts the set of processes that comprise the NonStop Services for CORBA. A message similar to the following indicates that the
processes have been started successfully:
gtacl[9]: warning: unable to propagate all environment variables
gtacl[9]: warning: unable to propagate all environment variables
NSDOM runtime environment was started.
Alternatively, you can run the nsdstart script in a manner that produces additional output as the script is executed by using the -v option as
follows:
nsdstart -v
The additional output shows the script as it is executed. This mode of running nsdstart can be useful for troubleshooting configuration errors.
To verify whether NonStop CORBA is running, type the following command (assuming NonStop CORBA is installed in the default
nsdoms
directory):
ps –e | grep nsd
You should see output similar to this:
56996660 ? 00:00 /usr/tandem/nsdoms/bin/ilsd
33095692 ? 00:00 /usr/tandem/nsdoms/bin/name_servant
84090631 ? 00:00 /usr/tandem/nsdoms/bin/lsd
66650123 ? 00:00 /usr/tandem/nsdoms/bin/cs
33095693 ? 00:00 /usr/tandem/nsdoms/bin/EventService
33095695 ? 00:00 /usr/tandem/nsdoms/bin/ird
33095696 ? 00:00 /usr/tandem/nsdoms/bin/NSotsTM
If you do not see output like this, you can restart the NonStop CORBA processes with the nsdstart script.
Running nsdstop
Before running nsdstop, be sure the required environment variable settings are in effect.
To run the
nsdstop script, enter the following command at the OSS command prompt:
nsdstop
This command stops the set of processes that comprise the NonStop Services for CORBA. The nsdstop script does not output a message when
it completes.
How the nsdstart Script Works
Each time it is run, the nsdstart script does the following:
1. Sets the script variables that specify the NonStop CORBA process names, such as the process names for the Comm Server and
Naming Server.
2. Determines the home terminal (
hometerm) on which server output messages are displayed.
3. Starts the PATHMON process that manages the server processes.
4. Creates a new TS/MP configuration file using the server pool settings contained in the script. Some process names are defined using the
script variables from Step 1.
5. Starts all the defined server processes.
The configuration settings defined by the script are stored in a TS/MP configuration file (PATHCTL). This file is created in the directory given by the
_DEFAULTS define in effect when the script is executed. For details about the PATHMON process and the PATHCOM commands used in the
scripts, see the NonStop TS/MP System Management Manual.
Troubleshooting: Problems Starting NonStop Services for CORBA
Process Name in Use
Pathctl File in Use
Process Name in Use