OpenShift Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
Then tail the journalctl log. More details on getting logging information: | Then tail the journalctl log. More details on getting logging information: | ||
{{ | {{InternalOpenShift_Logging#Master_and_Node_Process_Logging|OpenShift Master and Node Process Logging}} | ||
=Metrics Troubleshooting= | =Metrics Troubleshooting= | ||
Revision as of 21:53, 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:
--loglevel=10 seems to work fine.
Then tail the journalctl log. More details on getting logging information:
Template:InternalOpenShift Logging
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