IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 25 and Version 26 of PS1_IPP_Czarlog_20190204


Ignore:
Timestamp:
Feb 11, 2019, 2:03:27 PM (7 years ago)
Author:
fairlamb
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PS1_IPP_Czarlog_20190204

    v25 v26  
    320320}}}
    321321
    322 JRF: ME, MEH, and TdB shall be going though reprocessing some data for Rob without some pixels removed (as an NEO is suspected to be falling into a masked area).
    323 
    324 
    325 
    326322* 16:00 EAM : I started a set of rsyncs on ippb04 to copy nebulous directories to ippb16, ippb18, ippb19 (for b04.0, .1, .2 respectively).  I needed to add an id_rsa-style key to the ipp user since ippb04 refuses to use dsa keys.  (copy of existing authorized_keys saved as authorized_keys.20190207)
    327323
    328 === Saturday : 2019.02.09 ===
    329324
    330325JRF: Have been checking through the list of cluster nodes using neb-host to find nodes that have been left in repair. So that they can be brought back into production if they are ok
     
    358353}}}
    359354
     355=== Saturday : 2019.02.09 ===
     356
     357JRF: MEH took TdB and myself through checking out ganlia. Monitoring the general trends on CPU, memory and network loads on various machines. How to spot problems e.g. If the CPU report displays mostly orange/red then it indicates that the machine is often waiting before it can do something, which suggests a more thorough investigation.
     358
     359Can check individual machines in pantasks (or add/delete them too).
     360pantasks_client
     361controller host check ippc118
     362
     363Configuration failed on processing some files.
     364Used the following:
     365{{{
     366chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id
     367}}}
     368This was to solve some warps that got stuck in the warp stage when reprocessing, the chip im files just needed to be updated. Found out by querying:
     369SELECT warp_id, state, label FROM warpRun WHERE label LIKE "ps_ud_WEB";
     370then:
     371select chip_id,chipRun.state,chipRun.label,chipRun.data_group from warpRun join fakeRun using (fake_id) join camRun using (cam_id) join chipRun using (chip_id) where warp_id=1043753;
     372Repeated for the the remainder stuck in this state.
     373
     374
     375There are a bunch of wfix things stuck in the cam stage, so queried those to get the chip
     376chiptool -dbname gpc1 -setimfiletoupdate  -set_label PSNSC.wfix.20180525 -chip_id
     377{{{
     378+---------+---------+---------+---------+--------+
     379| warp_id | fake_id | cam_id  | chip_id | state  |
     380+---------+---------+---------+---------+--------+
     381| 1043758 | 1037107 | 1061440 | 1093979 | update |
     382| 1168814 | 1161011 | 1185484 | 1210911 | update |
     383| 1168816 | 1161013 | 1185486 | 1210913 | update |
     384| 1169004 | 1161150 | 1185635 | 1211006 | update |
     385| 1169008 | 1161154 | 1185639 | 1211010 | update |
     386| 1169202 | 1161493 | 1185817 | 1211220 | update |
     387| 1169204 | 1161495 | 1185820 | 1211223 | update |
     388| 1175590 | 1168954 | 1193676 | 1228151 | update |
     389| 1181423 | 1173791 | 1198632 | 1233292 | update |
     390| 1187981 | 1179229 | 1203026 | 1238323 | update |
     391| 1265032 | 1258067 | 1284307 | 1321028 | update |
     392| 1265037 | 1258072 | 1284316 | 1321033 | update |
     393| 1842166 | 1835551 | 1863463 | 1895949 | update |
     394+---------+---------+---------+---------+--------+
     395chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1093979
     396chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1210911
     397chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1210913
     398chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1211006
     399chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1211010
     400chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1211220
     401chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1211223
     402chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1228151
     403chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1233292
     404chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1238323
     405chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1321028
     406chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1321033
     407chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id 1895949
     408}}}
     409
     410
     411Do this on the MOPS.2 stuff to get them going again:
     412chiptool -dbname gpc1 -definebyquery -set_label PSNSC.wfix.20180525  -set_workdir neb://@HOST@.0/gpc1/PSNSC.wfix.20180525  -set_dist_group NULL -set_tess_id RINGS.V3 -set_end_stage warp -set_reduction SWEETSPOT -set_data_group PSNSC.wfix.20180525.x.date -exp_name
     413o5327g0047o
     414o5675g0136o
     415o5675g0143o
     416o5829g0438o
     417o5328g0050o
     418Once confirmed that the data has been processed, clean up the old stuff...
    360419
    361420=== Sunday : 2019.02.10 ===
     
    363422 * MEH: power at ATRC down, Haydn powered down ippb06-b23 -- set neb-host down for all machines so any primary copies there will switch to secondary on the system
    364423  * Gene has ippb04,b05 in repair to rsync and retire -- there are now no backup/archive nodes for replication -- NO processing can proceed -- this is not an acceptable situation as discussed before and a backup node set and plan is needed for future ATRC down event.
     424
     425JRF: ME, MEH, and TdB never got round to going though reprocessing some data for Rob without some pixels removed (as an NEO is suspected to be falling into a masked area). TODO at a later date.