IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 10 and Version 11 of PS1_IPP_Czarlog_20190218


Ignore:
Timestamp:
Feb 21, 2019, 12:26:43 PM (7 years ago)
Author:
tdeboer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PS1_IPP_Czarlog_20190218

    v10 v11  
    2828 * MEH: large warp update process continuing to run in ~ippmops/stdscience on the ippc31-c63, ipps00-14, ipp067-ipp123 nodes
    2929  * ps_ud% chips and warps label changed to update.hold20190219 so not to be cleaned by accident
     30
     31=== Wednesday : 2019.02.20 ===
    3032
    3133 * TdB: John, Roger and myself went through the logfiles to figure out what went wrong yesterday with ipp113. We looked through the reports for ipp113 on Ganglia, noticing the spiking load after 18:00 until 20:00. We went into the serial console using:
     
    8385}}}
    8486
     87=== Thursday : 2019.02.21 ===
     88 * TdB: ipp125 experienced stalling after high load and high wait yesterday night. messages in /var/log/messages showed some issues related to the swapper and the raid. Conferring with Haydn, the raid looks fine and a reboot is warranted.
     89   We went into the pantasks_client in ippqub:stdscience_ws to stop all the current processing:
     90{{{
     91pantasks_client
    8592
     93stop
     94}}}
     95  To check that all current processing was properly synced, we did:
     96{{{
     97sudo sync
     98}}}
     99  This showed nothing, indicating everything is synced correctly. Following this, we logged in to the machine using the serial console and did a regular reboot using:
     100{{{
     101sudo reboot -f
     102}}}
     103  boot messages indicate the Superblock last mount time was in the future and the clock was not set. Haydn confirmed the system clock does not automatically set on this motherboard/kernel combination, and set the clock manually using:
     104{{{
     105 ntpdate -u galileo
     106}}}
     107  which fixes the clock issue. The machine has subsequently been set back to repair to monitor its activity and load levels.
    86108
    87 === Wednesday : YYYY.MM.DD ===
     109 * TdB: several machines need a kernel update, among which ippx052. We removed it for current processing by going into the ps2 stdscience pantasks_client at ~ippps2/stdscience and doing:
     110{{{
     111controller status
     112controller host off ippx052 (6 times)
     113controller host delect ippx052 (6 times)
     114}}}
     115 After this, I let Gavin know the machineis ready for upgrade.
    88116
    89 === Thursday : YYYY.MM.DD ===
    90117
    91118=== Friday : YYYY.MM.DD ===