Changes between Version 5 and Version 6 of PS1_IPP_Czarlog_20190304

Timestamp:

Mar 5, 2019, 4:52:29 PM (7 years ago)

Author:

fairlamb

Comment:

--

PS1_IPP_Czarlog_20190304

@@ -170 +170 @@
 }}}
 
+JRF (afternoon ft czarlord Mark): 
+
+doing the updates of lots of 2014 data we finally got some faults reported on ippmonitor. Following the link, and checking the updates most issues appear to be related to trying to fetch files from a busy node e.g. ippb04. To fix this you can turn chip.revert off and on again or run: 
+{{{
+chiptool -revertprocessedimfile -fault 2 -label update.OSS -dbname gpc1
+}}}
+This will set the chip to revert and try again.
+
+
+'''Consolerc and SVN commiting:'''
+
+ipp129 seems to be working so it should be set to up in nebulous (done). However, if the machine is to become unresponsive then we would need to be able to log into the console to cycle it. Therefore, an entry needs to be made for ipp129 in the dotConsolerc file:
+{{{
+  ipp126:
+    console: itc-i12-con.ifa.hawaii.edu
+  ipp129:
+    console: itc-i12-con.ifa.hawaii.edu
+
+  ippc17:
+    console: itc-i10-con.ifa.hawaii.edu
+}}}
+The actual console entry came from the google sheets hardware document that says that ipp129 is in rack i13. "But John, you put the console as i12?!" - True, but that is because i12 actually manages i12 AND i13. There isn't necessarily a separate console for each rack. The i12 rack is fancy too, allows you to exit with 'Ctrl+z' then 'exit'
+
+I changed this file on the ippitc account, and my svn checkout. A couple of useful svn commands:
+
+To view the status i.e. the files that have changes in yuor local copy
+{{{
+svn st
+}}}
+
+To view the change log for a file:
+{{{
+svn log hardware/dotConsolerc
+}}}
+...which looks like:
+{{{
+------------------------------------------------------------------------
+r40635 | fairlamb | 2019-03-05 16:17:19 -1000 (Tue, 05 Mar 2019) | 1 line
+
+adding ipp129 to consolerc
+------------------------------------------------------------------------
+r40455 | mhuber | 2018-06-25 08:48:50 -1000 (Mon, 25 Jun 2018) | 1 line
+
+update .Consolerc for added nodes
+}}}
+
+To see the info on a file, such as last changed date (and by who):
+{{{
+svn info hardware/dotConsolerc 
+}}}
+...looks like this:
+{{{
+Path: hardware/dotConsolerc
+Name: dotConsolerc
+Working Copy Root Path: /home/john/ipp-clone/trunk
+URL: https://svn.pan-starrs.ifa.hawaii.edu/repo/ipp/trunk/hardware/dotConsolerc
+Relative URL: ^/trunk/hardware/dotConsolerc
+Repository Root: https://svn.pan-starrs.ifa.hawaii.edu/repo/ipp
+Repository UUID: 60eb6cdc-a59c-4636-a4e0-dba66a9721fd
+Revision: 40635
+Node Kind: file
+Schedule: normal
+Last Changed Author: fairlamb
+Last Changed Rev: 40635
+Last Changed Date: 2019-03-05 16:17:19 -1000 (Tue, 05 Mar 2019)
+Text Last Updated: 2019-03-05 16:05:14 -1000 (Tue, 05 Mar 2019)
+Checksum: 06cf3f1a18c8f5b2af639cacdb0d55231218c0cf
+}}}
+
+To see the differences between your local file and the repository version:
+{{{
+svn diff https://svn.pan-starrs.ifa.hawaii.edu/repo/ipp/trunk/hardware/dotConsolerc hardware/dotConsolerc 
+}}}
+
+Finally to commit a file doing the following:
+{{{
+svn commit hardware/dotConsolerc -m 'adding ipp129 to consolerc'
+}}}
+
+'''Other'''
+
+ipp127, ipp128 -> Haydn says that these machines are fine, and we're just getting fluff emails.