OpenShift Troubleshooting: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 20: Line 20:


  [[journalctl]] -u atomic-openshift-node -f
  [[journalctl]] -u atomic-openshift-node -f


=Metrics Troubleshooting=
=Metrics Troubleshooting=

Revision as of 21:35, 5 August 2017

Internal

Overview

The general technique is to increase the logging level of various OpenShift master (api, controllers) and node processes as described here:

Change the Log Level for OpenShift Processes

--loglevel=10 seems to work fine.

Then tail the journalctl log.

For the master controller process:

journalctl -u atomic-openshift-master-controllers -f

For the node process:

journalctl -u atomic-openshift-node -f

Metrics Troubleshooting

oadm diagnostics MetricsApiProxy

Pod Troubleshooting

oc -n <project-name> get pods
oc -n <project-name> describe po/<pod-name>

...
Name:			logging-fluentd-3kz30
...
Node:			node2/
...
Status:			Failed
Reason:			MatchNodeSelector
Message:		Pod Predicate MatchNodeSelector failed

Logging

OpenShift Logging