Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
tutorial:adm:server_os_updates [2019/12/17 07:43] fiserp [Performing the OS update] |
tutorial:adm:server_os_updates [2019/12/17 07:47] fiserp [Performing the OS update] |
||
|---|---|---|---|
| Line 42: | Line 42: | ||
| - Perform the update | - Perform the update | ||
| - Begin the maintenance. | - Begin the maintenance. | ||
| + | - Disable monitoring system notifications. | ||
| - (If you use hot snapshots, make one.) | - (If you use hot snapshots, make one.) | ||
| - Make sure no user or external application can access the IdM. | - Make sure no user or external application can access the IdM. | ||
| Line 53: | Line 54: | ||
| - Make backup of ``/boot``, ``/etc``, list of processes ``ps -ef`` and list of network services ``netstat -tulnp`` (or ``ss -tulnp``). Those dumps will help you check if all the services started. You can also recover some settings from backups in case something goes wrong (in a minor way) - you will not need to roll back whole snapshot. | - Make backup of ``/boot``, ``/etc``, list of processes ``ps -ef`` and list of network services ``netstat -tulnp`` (or ``ss -tulnp``). Those dumps will help you check if all the services started. You can also recover some settings from backups in case something goes wrong (in a minor way) - you will not need to roll back whole snapshot. | ||
| - Perform the update (e.g. ``yum update``). | - Perform the update (e.g. ``yum update``). | ||
| - | - Reboot the affected services or the whole machine if necessary. | + | - Restart |
| - When the machine is up, check ``dmesg`` and ``/ | - When the machine is up, check ``dmesg`` and ``/ | ||
| - Check running processes and network services whether everything started properly. | - Check running processes and network services whether everything started properly. | ||
| - Namely PostgreSQL and HTTPd should be up and running. Those are parts of IdM deployment. | - Namely PostgreSQL and HTTPd should be up and running. Those are parts of IdM deployment. | ||
| - If everything is ok, start the IdM service. | - If everything is ok, start the IdM service. | ||
| - | - Enable autostart of IdM service upon OS start. | ||
| - Check IdM logs whether it started successfuly. | - Check IdM logs whether it started successfuly. | ||
| - Log into the IdM and test connection to end systems (configuration form for the system, green button "Test connector" | - Log into the IdM and test connection to end systems (configuration form for the system, green button "Test connector" | ||
| - Check your testing use-cases. | - Check your testing use-cases. | ||
| + | - Enable autostart of IdM service upon OS start. | ||
| + | - (If there were changes to the database (e.g. PostgreSQL major version upgrade), make a backup of the upgraded database.) | ||
| - Allow users to access the IdM. | - Allow users to access the IdM. | ||
| + | - Enable monitoring system notifications. | ||
| - End the maintenance. | - End the maintenance. | ||
| - Wrap-up | - Wrap-up | ||