Changes between Version 18 and Version 19 of PS1_IPP_Czarlog_20190510

Timestamp:

May 14, 2019, 12:06:39 PM (7 years ago)

Author:

tdeboer

Comment:

--

PS1_IPP_Czarlog_20190510

@@ -197 +197 @@
 mysql -hscidbm -uX -pX gpc1 -B -e ' select chip_id,warp_id,warpRun.label,warpRun.data_group,warpRun.state,chipRun.label,chipRun.state from warpRun join fakeRun using (fake_id) join camRun using (cam_id) join chipRun using (chip_id)  where warpRun.label like "update.%" and warpRun.data_group like "%" and warpRun.state like "full" and chipRun.state like "full" group by warp_id limit 1000; ' | grep -v data_group | awk '{print "chiptool -dbname gpc1 -updaterun -state full -set_state goto_cleaned -set_label goto_cleaned -chip_id "$1 }' | tcsh
 }}}
-
+ '''update 2019-05-14:'''
+ I have been steadily cleaning, and there are about 2k left as of right now. So, these will be done before too long, but future czars should keep an eye on them and periodically clean to save space.
  ----------------------
 
@@ -271 +272 @@
 }}}
 
-
-
  * TdB: at around 17:30, the IPPmonitor stalled. Turns out, mysql crashed on ippdb05. Let's check things:
 
@@ -462 +461 @@
 }}}
 
+ Machines ipp128 and ipp139 have been set to repair with warnings "Read SMART Self-Test Log Failed" and "smartd daemon complained about failures". According to an email from Haydn, both of these are spurious warnings, and not critical. Therefore, set them back to up.
+{{{
+neb-host --state up --host ipp128 --note 'TdB: repair->up, after being put in repair with spurious errors'
+neb-host --state up --host ipp139 --note 'TdB: repair->up, after being put in repair with spurious errors'
+}}}
 === Wednesday : 2019.05.15 ===