At 7 PM. the server that contains the Intranet, the ITS Home Page, the online admissions application, WONC, pages remaining on www2, and some department pages (i.e., depts.noctrl.edu) went into a state of shock and was not responding.  ITS staff tried to fix the problem remotely but this server was in a coma.  ITS staff then drove in and physically gave the server a shock and then rebooted it at after 8 PM.  It looked like a successful recovery so we did a few more techie things to make sure that all was fine before heading home.  Of course as soon as the ITS staff member reached his driveway (and he does not live close to the College) he received another page saying that the server was again in shock.  Back he comes to the scene of the emergency.

 

ITS staff then tried swapping out the hard drives with a spare server, but the new set up wouldn't recognize the network configurations so everything was put back to where it was before.  Wouldn't you know it after some research on the Web in techie types of hang outs we find that this issue might be due to bad memory.  Now every server has different memory (just like humans) and of course we had spare memory laying around, but not the specific type for that server.   At this point we really became creative, and we came up with this incredibly techie solution.  We pulled out the memory on that server and literally gave it mouth to mouth resuscitation---yes we did blow on the memory---and then reinstalled it.  The server was  rebooted at 12:30 am.  Staff stayed another 30 minutes to make sure that our doctoring worked.  That server has been running fine ever since.  Today we will do a few more diagnostic tests on the memory to make sure that the memory is not bad.