OpenShift Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
(→a) |
No edit summary |
||
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
The general technique is to increase the logging level of various OpenShift master (api, controllers) and node processes as described here: | The general technique is to increase the logging level of various OpenShift master (api, controllers) and node processes as described here: | ||
{{Internal|OpenShift_Change_the_Log_Level_for_OpenShift_Processes|Change the Log Level for OpenShift Processes}} | |||
--loglevel=10 seems to work fine. | --loglevel=10 seems to work fine. | ||
Then tail the journalctl log: | Then tail the journalctl log. | ||
For the master controller process: | |||
[[journalctl]] -u atomic-openshift-master-controllers -f | [[journalctl]] -u atomic-openshift-master-controllers -f | ||
For the node process: | |||
[[journalctl]] -u atomic-openshift-node -f | |||
=Metrics Troubleshooting= | =Metrics Troubleshooting= | ||
oadm diagnostics MetricsApiProxy | oadm diagnostics MetricsApiProxy | ||
Revision as of 17:25, 6 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