Changes between Version 8 and Version 9 of PS1_IPP_Czarlog_20190426

Timestamp:

Apr 30, 2019, 1:45:40 PM (7 years ago)

Author:

fairlamb

Comment:

--

PS1_IPP_Czarlog_20190426

@@ -432 +432 @@
 After this the server started getting used, but the nebulous_server.log file disappeared. Simply restarting the apache server recreated it. However, if it does not you may need to touch the file (and make sure the permissions are correct).
 
-NEW PRBOLEMS!
-The log file is just not updating at all, even when we are using ippc76 to connect to the nebulous database (you can forcably change to use a specfic apache node by {{{set NEB_SERVER = http://ippc76}}}).
+NEW PROBLEMS!
+The log file is just not updating at all, even when we are using ippc76 to connect to the nebulous database (you can forcibly change to use a specific apache node by {{{set NEB_SERVER = http://ippc76}}}).
 Not sure what the problem is so we'll remove ippc76 from the nebservers list for the time being...
 
@@ -442 +442 @@
 
 
-To do: 
+''' Hardware update ''' b JRF
+
+13:30 - ITS has finished installing PDUs in cabinet M.02, for machines ipp134-136. At the same time Haydn has installed the fan extensions. I have checked that I can log into the console for each machine and view the power status.
+I'm going to put this machines back into repair so that updates can proceed:
+
+neb-host ipp134 repair --note "JRF: down -> repair: install of cabinet PDU and fan extension complete, should be set to up when confident"
+neb-host ipp135 repair --note "JRF: down -> repair: install of cabinet PDU and fan extension complete, should be set to up when confident"
+neb-host ipp136 repair --note "JRF: down -> repair: install of cabinet PDU and fan extension complete, should be set to up when confident"
+
+Now revert all the stalled jobs, and they should pick up that the files only on ipp134-136 are now available.