Questo contenuto non è disponibile nella lingua selezionata.
Chapter 3. Troubleshooting a cluster
To begin troubleshooting a Red Hat build of MicroShift cluster, first access the cluster status.
3.1. Checking the status of a cluster Copia collegamentoCollegamento copiato negli appunti!
You can check the status of a MicroShift cluster or see active pods by running a simple command. Given in the following procedure are three commands you can use to check cluster status. You can choose to run one, two, or all commands to help you retrieve the information you need to troubleshoot the cluster.
Procedure
You can check the system status, which returns the cluster status, by running the following command:
sudo systemctl status microshift
$ sudo systemctl status microshift
Copy to Clipboard Copied! Toggle word wrap Toggle overflow If MicroShift is failing to start, this command returns the logs from the previous run.
Optional: You can view the logs by running the following command:
sudo journalctl -u microshift
$ sudo journalctl -u microshift
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
The default configuration of the systemd
journal service stores data in a volatile directory. To persist system logs across system starts and restarts, enable log persistence and set limits on the maximum journal data size.
Optional: If MicroShift is running, you can see active pods by entering the following command:
oc get pods -A
$ oc get pods -A
Copy to Clipboard Copied! Toggle word wrap Toggle overflow