OpenShift Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
oadm diagnostics MetricsApiProxy | oadm diagnostics MetricsApiProxy | ||
= | =Troubleshooting Pods= | ||
[[oc get#pods|oc -n <project-name> get pods]] | [[oc get#pods|oc -n <project-name> get pods]] | ||
| Line 37: | Line 37: | ||
[[Oc_logs#-f|oc logs -f <''pod-name''>]] | [[Oc_logs#-f|oc logs -f <''pod-name''>]] | ||
=Troubleshooting Routes= | |||
=Logging= | =Logging= | ||
{{Internal|OpenShift Logging|OpenShift Logging}} | {{Internal|OpenShift Logging|OpenShift Logging}} | ||
Revision as of 00:50, 12 October 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:
Metrics Troubleshooting
oadm diagnostics MetricsApiProxy
Troubleshooting Pods
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
In-line pod logs:
oc logs -f <pod-name>