Changes between Version 15 and Version 16 of PS1_IPP_CzarLog_20120618

Timestamp:

Jun 25, 2012, 6:22:13 PM (14 years ago)

Author:

Mark Huber

Comment:

--

PS1_IPP_CzarLog_20120618

@@ -27 +27 @@
   * adding compute3 power to updates since no nightly science tonight as camera pumping down
   * selected chip updates finished, still working on kicking things
- * 22:10 Mark: PSS moving again, was it something I did or was someone else also monkeying with it?
+ * 22:10 Mark: PSS moving again, was it something I did or was someone else also monkeying with it? no. brief summary, don't understand fully why was blocked but once identified problem request, just put it in a hold state with
+{{{
+pstamptool -dbname ippRequestServer -dbserver $PSDBSERVER -updatereq -req_id 182918 -set_state hold
+}}}
+  * more detail, status at stalled state
+{{{
+| req_id | name                              | label  | reqType | state | fault | Num Rows | Total Jobs | Completed Jobs | Pending Jobs | Faulted Jobs | Image updates | last state change (UTC) |
++--------+-----------------------------------+--------+---------+-------+-------+----------+------------+----------------+--------------+--------------+---------------+-------------------------+
+| 182918 | web_59225                         | WEB    | pstamp  | run   |     0 |        1 |       9872 |           4811 |         5061 |         1370 |          1783 |     2012-06-20 20:49:14 | 
+| 182921 | MOPSSTAMPREQsp20120620T233423Z_00 | MOPS   | pstamp  | run   |     0 |        4 |          4 |              1 |            3 |            1 |             0 |     2012-06-20 23:34:59 | 
+| 182922 | MOPSSTAMPREQsp20120621T001932Z_00 | MOPS   | pstamp  | run   |     0 |       14 |         14 |              1 |           13 |            1 |             0 |     2012-06-21 00:20:15 | 
+| 182926 | cheee_20120620T143140             | WEB.UP | pstamp  | run   |     0 |      409 |        409 |            110 |          299 |           70 |             0 |     2012-06-21 00:36:34 |
+
+}}}
+  * initially restarting pstamp and update and started getting errors related to suspected problem PSS request update
+{{{
+config error for: chip_imfile.pl --threads @MAX_THREADS@ --exp_id 123499 --chip_id 55143 --chip_imfile_id 3148661 --class_id XY52 --uri neb://ipp033.0/gpc1/20100117/o5213g0177o/o5213g0177o.ota52.fits --camera GPC1 --run-state update  --deburned 0 --outroot neb://ipp033.0/gpc1/MD04.20100208/o5213g0177o.123499/o5213g0177o.123499.ch.55143 --redirect-output --dbname gpc1 --verbose
+
+gpc1/MD04.20100208/o5213g0177o.123499/o5213g0177o.123499.ch.55143.XY52.log
+gpc1/MD04.20100208/o5213g0177o.123499/o5213g0177o.123499.ch.55143.XY52.log.update
+
+Unable to parse camera.
+ -> psMetadataLookupMetadata (psMetadata.c:1148): I/O error
+     Couldn't find PPIMAGE.PATTERN in the metadata.
+ -> pmFPAfileDefineOutputForFormat (pmFPAfileDefine.c:187): I/O error
+     Can't find file rule PPIMAGE.PATTERN!
+ -> ppImageParseCamera (ppImageParseCamera.c:139): I/O error
+     Unable to generate output file from PPIMAGE.PATTERN
+--> very old data
+}}}
+  * tried some manually triggered cleanup+updates for QUB and MOPS, all fine but never recognized by pstamp/update to continue
+  * tried changing label priority with labeltool, seemed to change in -listlabels but not on PSS status page even after restarting
+  * tried tracing through, but giving up and just putting to hold. probably created a lot of cases for manual cleanup in future.
+
+
+
+
+
 === Saturday : YYYY.MM.DD ===