Changes between Version 5 and Version 6 of ProcedureBurntoolDoesNotStart

Timestamp:

Sep 1, 2010, 10:36:55 AM (16 years ago)

Author:

Serge CHASTEL

Comment:

--

ProcedureBurntoolDoesNotStart

@@ -1 +1 @@
 = Procedure: What to do when ''burntool'' does not start =
 
-== One image was not copied from the summit ==
+== One image was not copied from the summit. The IMAGE is VALID ==
+Do not use this procedure if the image is NOT valid.
 
 * '''Step 1:''' Check in the relevant log file (that is: ''~ipp/summitcopy/pantasks_stdout.log'') what was the reason for the failure
@@ -42 +43 @@
 }}}
 
-* '''Step 4:''' Use ''pztool'' to revert (!I did this step differently!)
+* '''Step 4:''' Use ''pztool'' to revert (!Note: I did this step differently!)
 
 {{{
-pztool -revertcopied 
+pztool -revertcopied
 }}}
 
-Note: the status of the faulty file can be checked in the gpc1 database.
+''Note:'' the status of the faulty file can be checked in the ''gpc1'' database.
 {{{
 ipp@ipp051>>> mysql -h ippdb01 -u ipp -pipp gpc1
@@ -58 +59 @@
 +-------------+--------+----------—+-------+----------+------------------------------------------------------------------------+-------+-------+----------+-------+--------+
 }}}
+The faulty entry can then be deleted:
+{{{
+mysql> delete from pzDownloadImfile where exp_name='o5440g0622o' and class_id='ota45';
+Query OK, 1 row affected (0.01 sec)
+mysql> quit
+}}}