Changes between Version 19 and Version 20 of PS1_IPP_Czarlog_20160411
- Timestamp:
- Apr 13, 2016, 12:51:49 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PS1_IPP_Czarlog_20160411
v19 v20 17 17 * 20:13 MEH: appears ipp100-104 were '''NOT''' fully setup to run pantasks jobs... missing /local/ipp link etc.. 18 18 * 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... 19 * 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 d own, ippc02 was fixed when disk/raid and power supply issue at end of 2015 so have uncommented that for ~ipp, ~ippqub/.tcshrc19 * 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 disk/raid issues, ippc02 was fixed when disk/raid and power supply issue at end of 2015 so have uncommented that for ~ipp, ~ippqub/.tcshrc 20 20 * ippc02 also originally hosted stdscience pantasks, probably should also be returned since seen ippc01 having a good amount of load at times... 21 21 * 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... -- yep... ~ipptest and ~ipplanl were both out of alignment with ~ipp/ippqub using ippc02 rather than ippc05, so using ippc02 again helps those use the proper same apache servers..
