Red Hat build of MicroShift

Check journal logs after updates

You can use journal logs to help diagnose MicroShift update failures. The default configuration of the systemd journal service stores data in a volatile directory, which does not persist across restarts. To retain logs across restarts, enable log persistence and set a maximum size limit for journal data.

Procedure

Get comprehensive MicroShift journal logs by running the following command:
```
$ sudo journalctl -u microshift
```
Check the greenboot journal logs by running the following command:
```
$ sudo journalctl -u greenboot-healthcheck
```
Examining the comprehensive logs of a specific boot uses three steps. First list the boots, then select the one you want from the list you obtained:
- List the boots present in the journal logs by running the following command:
  $ sudo journalctl --list-boots
  Example output
  IDX BOOT ID FIRST ENTRY LAST ENTRY 0 681ece6f5c3047e183e9d43268c5527f <Day> <Date> 12:27:58 UTC <Day> <Date>> 13:39:41 UTC #....
- Check the journal logs for the specific boot by running the following command:
  $ sudo journalctl --boot _<idx_or_boot_id>
  where:
  
  idx_or_boot_id
  
  Replace <idx_or_boot_id> with the IDX or the BOOT ID number assigned to the specific boot that you want to check.
- Check the journal logs for the boot of a specific service by running the following command:
  $ sudo journalctl --boot <idx_or_boot_id> -u <service_name>
  where:
  
  idx_or_boot_id
  
  Replace <idx_or_boot_id> with the IDX or the BOOT ID number assigned to the specific boot that you want to check.
  
  service_name
  
  Replace <service_name> with the name of the service that you want to check.