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. It runs diagnostics using a client and/or the state of a running master / node host.

oc adm diagnostics

If run without flags, it will check for standard config files for client, master, and node, and if found, use them for diagnostics. You may also specify config files explicitly with flags, in which case you will receive an error if they are not found. For example:

oc adm diagnostics --master-config=/etc/origin/master/master-config.yaml
· If master/node config files are not found and the --host flag is not present, host diagnostics are skipped.

· If the client has cluster-admin access, this access enables cluster diagnostics to run which regular users cannot.

· If a client config file is not found, client and cluster diagnostics are skipped.

Diagnostics may be individually run by passing diagnostic name as arguments. The available diagnostic names are: AnalyzeLogs ClusterRegistry ClusterRoleBindings ClusterRoles ClusterRouter ConfigContexts DiagnosticPod MasterConfigCheck MasterNode MetricsApiProxy NodeConfigCheck NodeDefinitions ServiceExternalIPs UnitStatus

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
Look for systemd and journald units even without master/node config
--images="openshift/origin-${component}:${version}"
Image template for DiagnosticPod to use in creating a pod
--latest-images=false
When expanding the image template, use latest version, not release version
--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
May be set to prevent diagnostics making any changes via the API

Options Inherited from Parent Commands

--api-version=""
DEPRECATED: The API version to use when talking to the server

--as=""
Username to impersonate for the operation.

--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.

--log-flush-frequency=0
Maximum number of seconds between log flushes

--match-server-version=false
Require server version to match client version

-n, --namespace=""
If present, the namespace scope for this CLI request.

--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

See Also

oc-adm(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

oc-adm(1).

Openshift CLI User Manuals Openshift June 2016