astro-wiki

This is an old revision of the document!

---

== Change in Yum Update Location - email from Jon “ just created a redhat directory on astrobackup2, and modified /etc/auto.home on astronomy to point the automount (/home/redhat) to it, the did a cd_var_yp_make} to push this to NIS for all other machines.”

== Update Schedule Zach will start updating machines on a monthly basis on the last day of the month. After kernel updates, reboots will be required in order for new kernel to take effect (best schedule for reboots?).

== Last Time 'Yum Update' Was Run on the Machine?

'Best practice' - Run 'yum update' on one machine first to get an idea of what's being installed/updated. Then once that completes, you can run the doit scripts for CentOS 6 and 7 machines. For example: user_astronomy_home_local_etc_doit-centos7_yum_update_-y}

It is perhaps a good idea, after the doit script runs, to check the history to make sure no errors were noted: user_astronomy_home_local_etc_doit-centos7_yum_history} And then list any oddities in the below table –

'NOTE' - At 9:00am on 7-31-2020, Zach ran the doit script for CentOS7 machines. (this note is for me to track how long this process takes for a 'long' update. Updates finished at ~3:30pm).

'NOTE' - On Sept. 30th - Zach Noticed that Acrux, Mintake, Spica, and Zenith were shut down. They were shut down by means OTHER than Zach or Jon. Actions - Zach will go into the building Next week to inspect these machines, power them on and access them. Zach went into the department on 10-5-2020. Machines were okay. No foul play detected.

== Last Time a Update was done on Sever/RAID device?

'NOTE' For AstroBackUp, AstroBackUp3, Cosmology1,4,5 → you need to log in through the astronomy.nmsu.edu subnet and follow the GUI to update these machines.

== Possible Issues Some machines will not be able to update the kernel due to small partition sizes in /boot file system.

In order to clear up space:

First, use yum to check the kernel installed: root_machine}

Then, figure out which kernel is the active one: root_machine}

Then, use yum to remove kernels that is 'NOT' the active kernal: root_machine}

Also, an additional work around is to just exclude the kernel in the update: root_machine}

ISSUES