oc-adm-diagnostics man page

oc adm diagnostics — Diagnose common cluster problems

Synopsis

oc adm diagnostics [Options]

Description

This utility helps troubleshoot and diagnose known problems for an OpenShift cluster and/or local host. The base command runs a standard set of diagnostics:

oc adm diagnostics

Available diagnostics vary based on client config and local OpenShift host config. Config files in standard locations for client, master, and node are used, or you may specify config files explicitly with flags. For example:

oc adm diagnostics --master-config=/etc/origin/master/master-config.yaml

· Explicitly specifying a config file raises an error if it is not found.

· A client config with cluster-admin access is required for most cluster diagnostics.

· Diagnostics that require a config file are skipped if it is not found.

· The standard set also skips diagnostics considered too heavyweight.

An individual diagnostic may be run as a subcommand which may have flags for specifying options specific to that diagnostic.

Finally, the "all" subcommand runs all available diagnostics (including heavyweight ones skipped in the standard set) and provides all individual diagnostic flags.

Options

--cluster-context=""

Client context to use for cluster administrator

--config=""

Path to the config file to use for CLI requests.

--context=""

The name of the kubeconfig context to use

-l, --diaglevel=1

Level of diagnostic output: 4: Error, 3: Warn, 2: Notice, 1: Info, 0: Debug

--host=false

If true, look for systemd and journald units even without master/node config

--loglevel=0

Set the level of log output (0-10)

--logspec=""

Set per module logging with file|pattern=LEVEL,...

--master-config=""

Path to master config file (implies --host)

--node-config=""

Path to node config file (implies --host)

--prevent-modification=false

If true, may be set to prevent diagnostics making any changes via the API

Options Inherited from Parent Commands

--as=""

Username to impersonate for the operation

--as-group=[]

Group to impersonate for the operation, this flag can be repeated to specify multiple groups.

--azure-container-registry-config=""

Path to the file container Azure container registry configuration information.

--cache-dir="/builddir/.kube/http-cache"

Default HTTP cache directory

--certificate-authority=""

Path to a cert file for the certificate authority

--client-certificate=""

Path to a client certificate file for TLS

--client-key=""

Path to a client key file for TLS

--cluster=""

The name of the kubeconfig cluster to use

--google-json-key=""

The Google Cloud Platform Service Account JSON Key to use for authentication.

--insecure-skip-tls-verify=false

If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure

--match-server-version=false

Require server version to match client version

-n, --namespace=""

If present, the namespace scope for this CLI request

--request-timeout="0"

The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.

--server=""

The address and port of the Kubernetes API server

--token=""

Bearer token for authentication to the API server

--user=""

The name of the kubeconfig user to use

--version=false

Print version information and quit

See Also

oc-adm(1), oc-adm-diagnostics-aggregatedlogging(1), oc-adm-diagnostics-all(1), oc-adm-diagnostics-analyzelogs(1), oc-adm-diagnostics-appcreate(1), oc-adm-diagnostics-clusterregistry(1), oc-adm-diagnostics-clusterrolebindings(1), oc-adm-diagnostics-clusterroles(1), oc-adm-diagnostics-clusterrouter(1), oc-adm-diagnostics-configcontexts(1), oc-adm-diagnostics-diagnosticpod(1), oc-adm-diagnostics-etcdwritevolume(1), oc-adm-diagnostics-inpod-networkcheck(1), oc-adm-diagnostics-inpod-poddiagnostic(1), oc-adm-diagnostics-masterconfigcheck(1), oc-adm-diagnostics-masternode(1), oc-adm-diagnostics-metricsapiproxy(1), oc-adm-diagnostics-networkcheck(1), oc-adm-diagnostics-nodeconfigcheck(1), oc-adm-diagnostics-nodedefinitions(1), oc-adm-diagnostics-routecertificatevalidation(1), oc-adm-diagnostics-serviceexternalips(1), oc-adm-diagnostics-unitstatus(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

oc-adm(1), oc-adm-diagnostics-aggregatedlogging(1), oc-adm-diagnostics-all(1), oc-adm-diagnostics-analyzelogs(1), oc-adm-diagnostics-appcreate(1), oc-adm-diagnostics-clusterregistry(1), oc-adm-diagnostics-clusterrolebindings(1), oc-adm-diagnostics-clusterroles(1), oc-adm-diagnostics-clusterrouter(1), oc-adm-diagnostics-configcontexts(1), oc-adm-diagnostics-diagnosticpod(1), oc-adm-diagnostics-etcdwritevolume(1), oc-adm-diagnostics-inpod-networkcheck(1), oc-adm-diagnostics-inpod-poddiagnostic(1), oc-adm-diagnostics-masterconfigcheck(1), oc-adm-diagnostics-masternode(1), oc-adm-diagnostics-metricsapiproxy(1), oc-adm-diagnostics-networkcheck(1), oc-adm-diagnostics-nodeconfigcheck(1), oc-adm-diagnostics-nodedefinitions(1), oc-adm-diagnostics-routecertificatevalidation(1), oc-adm-diagnostics-serviceexternalips(1), oc-adm-diagnostics-unitstatus(1).

Openshift CLI User Manuals June 2016