welcome: please sign in

Upload page content

You can upload content for the page named below. If you change the page name, you can also upload content for another page. If the page name is empty, we derive the page name from the file name.

File to load page content from
Page name
Comment
First name of the author of the GNU Manifesto

Edit

OnSiteVisits / 20140417

Upgrade Fritz's RAM and attempt to restore KvmAccess.

1. People

2. Goals

3. Outcome

3.1. Short Version

3.2. Long Version

The actual RAM upgrade for fritz seemed to go quite smoothly. Fritz was down for ~15 minutes for hardware surgery, beating the expected time by a great margin. It was when it booted that problems developed. None were fatal, but combined caused fritz to take an ~1h15m before afs was restored and nearly another hour before all services were restored.

Attempts to restore KvmAccess ended with hopper being accessible and the other machines appearing to not work. ClintonEbadi requested that hopper's cables be swapped onto fritz, but fritz continues to not display anything. The KVM may be dying.

We managed to reboot deleuze. It required manually pressing the power button to make it finish halting, but it booted cleanly and quickly afterward.

Problems:

Fixes:

3.3. Next Steps

4. Supporting Material

inside-fritz.png

5. Itinerary

5.1. Upgrade Fritz Memory

SERVICE IMPACTING. Goal: 30 minutes downtime. Stretch: One hour. (Fritz can take up to 15 minutes to reboot)

5.2. Restore KVM

Not Service Impacting

5.3. Reboot Deleuze

Minor Service Impact (Mail will be rejected briefly)