| | 1 | == PS1 IPP Czar Logs for the week 2019.05.10 - 2019.05.16 == |
| | 2 | [[PageOutline]] |
| | 3 | |
| | 4 | (Up to [wiki:PS1_IPP_CzarLogs PS1 IPP Czar Logs]) |
| | 5 | |
| | 6 | === Friday : 2019.05.10 === |
| | 7 | '''CZAR HANDOVER''' by CCL |
| | 8 | |
| | 9 | * Haydn mentioned he will check them on 5/13 (remind him maybe) |
| | 10 | - ipp128: Device: /dev/bus/0 [megaraid_disk_15], Read SMART Self-Test Log Failed |
| | 11 | - ipp139: Device: /dev/bus/0 [megaraid_disk_37], Read SMART Self-Test Log Failed |
| | 12 | - ippc72 is down: details mentioned above, not sure what the next action will be (another hardware issue) |
| | 13 | - ippc129, ippc135, ippc145, ippc149, ippc150: drive issue |
| | 14 | |
| | 15 | - update.LAP.PV3: 15k warp prcessing jobs on ippmonitor, some of them might have been processed to be "full" state by queue their data_state in the warpSkyfile table. Their data quality is not equal to 0 which may affect the state keep "update". |
| | 16 | - QUB have put in a lot of stamp requests, you may need to restart pstamp a couple more times today (when jobs done >100k). |
| | 17 | - these huge jobs may cause ipp restart unsuccessfully (stdscience happened twice), make sure all server are running by check_system.sh |
| | 18 | |
| | 19 | === Saturday : 2019.05.11 === |
| | 20 | |
| | 21 | === Sunday : 2019.05.12 === |
| | 22 | |
| | 23 | === Monday : 2019.05.13 === |
| | 24 | |
| | 25 | === Tuesday : 2019.05.14 === |
| | 26 | |
| | 27 | === Wednesday : 2019.05.15 === |
| | 28 | |
| | 29 | === Thursday : 2019.05.16 === |
| | 30 | |
