| Exit Print View | |
Sun OpenDS Standard Edition 2.2 Command-Line Usage Guide |
|
|
|
The status command displays basic server status information.
status [options]
The status command can be used to display basic server information, such as the status of the server (started or stopped), the configured connection handlers, or the list of defined back ends and suffixes.
If the server is started, the status command connects to the server over SSL, through the administration connector.
For more information, see Managing Administration Traffic to the Server in Sun OpenDS Standard Edition 2.2 Administration Guide.
If the server is stopped, you must run this command as a user with file system access rights to read the configuration files (particularly the config.ldif file).
Note - Certain monitoring data can only be displayed when the server is running (for example, the number of entries in a back end).
The status command contacts the server over SSL through the administration connector (described in Managing Administration Traffic to the Server in Sun OpenDS Standard Edition 2.2 Administration Guide). These connection options are used to contact the server.
Use the bind DN to authenticate to the server. This option is used when performing simple authentication and is not required if SASL authentication is to be used. The default value for this option is cn=Directory Manager.
Contact the server on the specified hostname or IP address. If this option is not provided, a default of localhost is used.
Use the bind password in the specified file when authenticating to the server. This option must not be used in conjunction with --bindPassword.
Use the client keystore certificate in the specified path.
Use the specified certificate for client authentication.
Use the specified options for SASL authentication.
SASL is not supported for Sun OpenDS Standard Edition proxy.
Contact the server at the specified administration port. If this option is not provided, a default administration port of 4444 is used.
Use the client trust store certificate in the specified path. This option is not needed if --trustAll is used, although a trust store should be used when working in a production environment.
Use the password needed to access the certificates in the client trust store. This option is only required if --trustStorePath is used and the specified trust store requires a password in order to access its contents (which most trust stores do not require). This option must not be used in conjunction with --trustStorePasswordFile.
Use the password in the specified file to access the certificates in the client keystore. This option is only required if --keyStorePath is used. This option must not be used in conjunction with --keyStorePassword.
Use the password in the specified file to access the certificates in the client trust store. This option is only required if --trustStorePath is used and the specified trust store requires a password in order to access its contents (most trust stores do not require this). This option must not be used in conjunction with --trustStorePassword.
Use the bind password when authenticating to the server. This option can be used for simple authentication as well as password-based SASL mechanisms. This option must not be used in conjunction with --bindPasswordFile. To prompt for the password, type -w -.
SASL is not supported for Sun OpenDS Standard Edition proxy.
Use the password needed to access the certificates in the client keystore. This option is only required if --keyStorePath is used. This option must not be used in conjunction with --keyStorePasswordFile.
Trust all server SSL certificates that the server presents. This option can be used for convenience and testing purposes, but for security reasons a trust store should be used to determine whether the client should accept the server certificate.
Use non-interactive mode. If some data in the command is missing, you are not prompted and the command will fail.
Indicate that the command should not use a properties file to get the default command-line options.
Specify the path to the properties file that contains the default command-line options.
Run in “script friendly” mode. Script friendly mode will not prompt you for any information but requires that all values be provided through command-line options.
Display command-line usage information for the command and exit without making any attempt to stop or restart the server.
Display the version information for the server and exit rather than attempting to run this command.
The following examples show how to use the server commands. You can use the commands on any UNIX, Linux, or Windows system that has at least the Java SE 5 (at least Sun version 1.5.0_08, preferably the latest version of Java SE 6) runtime environment installed on its target system.
For more information, see Sun OpenDS Standard Edition System Requirements in Sun OpenDS Standard Edition 2.2 Installation Guide.
The following example displays the current status of a standalone server that is currently online:
$ status -h localhost -p 4444 -D "cn=directory manager" -w password -X -n
--- Server Status ---
Server Run Status: Started
Open Connections: 1
--- Server Details ---
Host Name: llandudno
Administrative Users: cn=Directory Manager
Installation Path: /var/OpenDSSE/build/package/OpenDS-1.1.0
OpenDS Version: OpenDS Directory Server 1.1.0
Java Version: 1.6.0_07
Administration Connector: Port 4444 (LDAPS)
--- Connection Handlers ---
Address:Port : Protocol : State
-------------:----------:---------
0.0.0.0:636 : LDAPS : Disabled
0.0.0.0:1389 : LDAP : Enabled
0.0.0.0:1689 : JMX : Disabled
--- Data Sources ---
Base DN: dc=example,dc=com
Backend ID: userRoot
Entries: 102
Replication: DisabledAn exit code of 0 indicates that the operation completed successfully. A nonzero exit code indicates that an error occurred during processing.
The server supports the use of a properties file that passes in any default option values used with the status command. The properties file is convenient when working in different configuration environments, especially in scripted or embedded applications. For more information, see Using a Properties File With Server Commands.
The following options can be stored in a properties file:
bindDN
bindPassword
bindPasswordFile
certNickname
hostname
keyStorePassword
keyStorePasswordFile
keyStorePath
port
saslOption
SASL is not supported for Sun OpenDS Standard Edition proxy.
trustAll
trustStorePassword
trustStorePasswordFile
trustStorePath
Entries in the properties file have the following format:
toolname.propertyname=propertyvalue
For example:
status.bindPassword=password
UNIX and Linux: install-dir/bin/status
Windows: install-dir\bat\status.bat
|
|