You can use the stopOgServer script
to stop server processes.
- Stop eXtreme Scale container
processes.
- From the command line, navigate to the bin directory.
cd objectGridRoot/bin
- Run the stopOgServer script to stop
the server. The following example stops the c0 server:
stopOgServer.sh c0 -catalogServiceEndPoints MyServer1.company.com:2809
Attention: On the container, the
-catalogServiceEndPoints option
is used to reference the Object Request Broker (ORB) host and port
on the catalog service. The catalog service uses
-listenerHost and
-listenerPort options
to specify the host and port for ORB binding or accepts the default
binding. When you are stopping a container, use the
-catalogServiceEndPoints option
to reference the values passed to
-listenerHost and
-listenerPort on
the catalog service. If the
-listenerHost and
-listenerPort options
are not used when starting the catalog service, the ORB binds to
port 2809 on the localhost for the catalog service.
Do not use
the -catalogServiceEndPoints option to reference
the hosts and ports that were passed to the -catalogServiceEndPoints option
on the catalog service. On the catalog service, use the -catalogServiceEndPoints option
to specify the ports that are necessary for static server configuration.
- Stop eXtreme Scale catalog
service processes.
- From the command line, navigate to the bin directory.
cd objectGridRoot/bin
- Run the stopOgServer script to stop
the server.
stopOgServer.sh catalogServer -bootstrap MyServer1.company.com:6601
Identify the process to stop with the catalogServer argument,
the first argument that is passed to the script. For this example,
assume that the catalog service was started on the MyServer1.company.com
domain with a clientAccessPort value of 6601.
- Enable trace for the server stop process. If
a container fails to stop, you can enable trace to help with debugging
the problem. To enable trace during the stop of a server, add the -traceSpec and -traceFile parameters
to the stop commands. The -traceSpec parameter
specifies the type of trace to enable and the -traceFile parameter
specifies path and name of the file to create and use for the trace
data.
- From the command line, navigate to the bin directory.
cd objectGridRoot/bin
- Run the stopOgServer script with
trace enabled.
stopOgServer.sh c4 -catalogServiceEndPoints MyServer1.company.com:2809
-traceFile ../logs/c4Trace.log -traceSpec ObjectGrid=all=enabled
After the trace is obtained, look for errors related to
port conflicts, missing classes, missing or incorrect XML files or
any stack traces. Suggested startup trace specifications are: - ObjectGrid=all=enabled
- ObjectGrid*=all=enabled
For all of the trace specification options, see Trace options.