WP12274

FAMIS28946

We rebooted the h1guardian1 machine today for 3 things:

1. Point the machine back at nds0 as the primary nds server
   • I noticed the other day that the guardian was still defining the chosen nds server as nds1 primary and nds0 as secondary. I'm not entirely sure when this was changed, but maybe 2 years ago (alog66834).
   • This was done by changing the NDSSERVER definition in the /etc/guardian/local-env file
2. Relieve any stale processes that might latch the gps leap second data.
3. Quarterly machine reboot FAMIS task

All 168 nodes came back up and Erik confirmed that nds0 was seeing the traffic after the machine reboot.