Administration guide > Operate the deployment environment > Start and stop stand-alone servers
Stop stand-alone servers
Use the stopOgServer script to stop eXtreme Scale server processes.
Run the stopOgServer script by navigating to the bin directory:
cd wxs_install_root/bin
Procedure
- Stop container servers.
Run the stopOgServer script to stop the container server.
stopOgServer containerServer -catalogServiceEndPoints MyServer1.company.com:2809
Use the same script to stop multiple servers by separating a list of servers with commas:
stopOgServer cs0,cs1,cs2 -catalogServiceEndPoints MyServer1.company.com:2809
Attention: The -catalogServiceEndPoints option should match the value of the -catalogServiceEndPoints option that was used to start the container. If a -catalogServiceEndPoints was not used to start the container, the default values are likely localhost or the hostname and 2809 for the ORB port to connect to the catalog service. Otherwise, use the values that are 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.
- Stop catalog servers.
Run the stopOgServer script to stop the catalog server.
stopOgServer.sh catalogServer -catalogServiceEndPoints MyServer1.company.com:2809
Attention: When you are stopping a catalog service, use the -catalogServiceEndPoints option 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. 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. The -catalogServiceEndPoints option is different when stopping a catalog service than when you started the catalog service.
Start a catalog service requires peer access ports and client access ports, if the default ports were not used. Stopping a catalog service requires only the ORB port.
- 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 wxs_install_root/bin
- Run the stopOgServer script with trace enabled.
stopOgServer.sh c4 -catalogServiceEndPoints MyServer1.company.com:2809 -traceFile ../logs/c4Trace.log -traceSpec ObjectGrid=all=enabledAfter 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.
- Stop embedded servers programmatically.
For more information about stopping embedded servers programmatically, see Use the embedded server API to start and stop servers.
- stopOgServer script
The stopOgServer script stops catalog and container servers.
- Stop servers gracefully with the xsadmin tool
Use the xsadmin tool with the -teardown parameter to stop a list or group of catalog and container servers. This command simplifies shutting down all or portions of a data grid, avoiding unnecessary placement and recovery actions by the catalog service that normally occur when processes are stopped or killed.
Parent topic:
Start and stop stand-alone servers
Related concepts
Start and stop secure eXtreme Scale servers
Hardware and software requirements
Start and stop secure eXtreme Scale servers
Related tasks
Related reference