OpenShift Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
| Line 33: | Line 33: | ||
... | ... | ||
Status: Failed | <font color=red>Name</font>: logging-fluentd-3kz30 | ||
... | |||
<font color=red>Node</font>: node2/ | |||
... | |||
<font color=red>Status</font>: Failed | |||
Reason: MatchNodeSelector | Reason: MatchNodeSelector | ||
Message: Pod Predicate MatchNodeSelector failed | Message: Pod Predicate MatchNodeSelector failed | ||
Revision as of 20:42, 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