OpenShift Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
| Line 28: | Line 28: | ||
=Pod Troubleshooting= | =Pod Troubleshooting= | ||
oc -n <project-name> get pods | [[oc get#pods|oc -n <project-name> get pods]] | ||
oc -n <project-name> describe po/<pod-name> | [[oc describe#pod|oc -n <project-name> describe po/<pod-name>]] | ||
... | ... | ||
Revision as of 20:49, 30 July 2017
Internal
Overview
The general technique is to increase the logging level of various OpenShift master (api, controllers) and node processes as described here:
--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