Changes between Version 16 and Version 17 of PS1_IPP_Czarlog_20160411

Timestamp:

Apr 13, 2016, 12:32:33 AM (10 years ago)

Author:

Mark Huber

Comment:

--

PS1_IPP_Czarlog_20160411

@@ -15 +15 @@
  * 15:10 CZW: Started wave3 rsyncs on stare00.  I'm starting fairly slowly, with 5x4x10MB transfers to get an idea of the speed and loading of this.
  * 19:12 MEH: ipp050 crash, nothing on console -- not responding to power cycle yet so neb-host down (from repair) before it messes up nightly processing..
- * 20:13 MEH: appears ipp100-104 were fully setup to run jobs... missing /local/ipp dir etc.. 
-  * oddly so is ipp078 -- /local/ipp symlink to /export/ipp078.0/ipp -- why aren't things like this being checked... probably explains some faults in the past when ipp078 was in use before dvo use..
- * 23:10 MEH: things running better tonight, only ~40 exposures behind @2230 when >70 the past few nights -- noticed another apache server had '''NOT''' been turned on to replace ippc05 being removed since down, ippc02 was fixed when disk/raid and power supply issue at end of 2015 so have uncommented that for ~ipp, ~ippqub/.tcshrc
+ * 20:13 MEH: appears ipp100-104 were '''NOT''' fully setup to run pantasks jobs... missing /local/ipp link etc.. 
+  * oddly so is ipp078 -- /local/ipp symlink to /export/ipp078.0/ipp -- why aren't things like this being checked... probably explains some faults in the past when ipp078 was in use before dvo use...
+ * 23:10 MEH: things running better tonight, only ~40 exposures behind @2230 when >70 the past few nights (so similar to earlier last week and still not back to ~60 exposures/hr as normal several weeks ago) -- noticed another apache server had '''NOT''' been turned on to replace ippc05 being removed since down, ippc02 was fixed when disk/raid and power supply issue at end of 2015 so have uncommented that for ~ipp, ~ippqub/.tcshrc 
   * ippc02 also originally hosted stdscience pantasks, probably should also be returned since seen ippc01 having a good amount of load at times...
   * wondering if there are other pantasks running not using the same apache for nebulous -- maybe should stop apache on those nodes to block any cases of that...