IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Initial Version and Version 1 of IppToPspsIngestOf3PiPv3


Ignore:
Timestamp:
Jun 2, 2016, 1:39:21 PM (10 years ago)
Author:
heather
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IppToPspsIngestOf3PiPv3

    v1 v1  
     1Notes on ingest of PV3 ipptopsps go here
     2
     3== Current version of ipptopsps ==
     4
     5using ippdvo2 account:
     6
     7{{{
     8ippdvo2@ippc19:/home/panstarrs/ippdvo2>psconfig
     9/home/panstarrs/ippdvo2/psconfig : ipptrunk.20160518 : lin64
     10}}}
     11
     12== Current status of ipptopsps ==
     13
     14 * all of these are located in datastores like 'PSPS_PV3_ST_SLICE_X'
     15 * IN - needs to be generated
     16 * OB - the boundaries need to be regenerated once Gene investigates
     17 * ST - edges are avoided; found 1 hole (non-boundary) so far with dvo duplicates, and 2 batches with invalid cmf info.
     18 * P2 - Wait for Gene
     19 * FW - Wait for Gene
     20 * FG/FO - Need to verify ffg minis before handoff to Gene, then wait for Gene.
     21 * DF/DO - addstar in progress. large number of faults due to missing files on space telescope machines
     22
     23== Fastest way to set up mysql on 'new' machines ==
     24
     25as root on the machine in question
     26{{{
     27cp /etc/mysql/my.cnf /etc/mysql/my.cnf.orig
     28cp ~heather/mysqlconfig/my.cnf /etc/mysql/my.cnf
     29/usr/bin/mysql_install_db
     30/etc/init.d/mysql restart
     31}}}
     32
     33wait a bit, it can take a bit of time to start, and the status it displays when doing mysql restart is generally useless. check if it is running with mysql -h localhost -u root
     34
     35now, as ippdvo2 on that machine (not sure why, but it doesn't take as root), the following will add the necessary accounts, initialize and install the scratch database.
     36
     37{{{
     38mysql -h localhost -u root
     39CREATE USER 'dvo'@'%' IDENTIFIED BY 'dvo';
     40GRANT ALL on *.* to 'dvo'@'%';
     41CREATE USER 'dvo'@'localhost' IDENTIFIED BY 'dvo';
     42GRANT ALL on *.* to 'dvo'@'localhost';   
     43create database ipptopsps_scratch;
     44flush privileges;
     45exit
     46ippjython setupScratchDb.py
     47}}}
     48
     49== current ipptopsps machines ==
     50
     51 * ipp006 is the database machine, name of database is ipptopsps2
     52 * ippx001 - ippx048 are currently set up for ipptopsps (correct schema, mysql, etc)
     53
     54== current checker scripts ==
     55
     56I am running ipptopsps on ippdvo2@ippc19 as a series of screens. 
     57
     58{{{
     59ippdvo2@ippc19:/home/panstarrs/ippdvo2>screen -list
     60There are screens on:
     61        16937.ippx038   (Detached)
     62        18061.ippx040   (Detached)
     63        21114.ipp0061   (Detached)
     64        14854.ippx025   (Detached)
     65        8346.ippx002    (Detached)
     66        17709.ippx039   (Detached)
     67        12913.ippx012   (Detached)
     68        12513.ippx011   (Detached)
     69        30664.ippx024   (Detached)
     70        6716.ippx001    (Detached)
     71        15710.ippx027   (Detached)
     72        28930.ippx015   (Detached)
     73        29697.ippx022   (Detached)
     74        9390.ippx032    (Detached)
     75        11759.ippx035   (Detached)
     76        15441.ippx026   (Detached)
     77        10147.ippx034   (Detached)
     78        14845.ippx048   (Detached)
     79        9809.ippx033    (Detached)
     80        31005.ippx029   (Detached)
     81        14303.ippx020   (Detached)
     82        29540.ippx021   (Detached)
     83        31320.ippx030   (Detached)
     84        27989.ippx008   (Detached)
     85        29405.ippx005   (Detached)
     86        13691.ippx018   (Detached)
     87        29204.ippx016   (Detached)
     88        16163.ippx028   (Detached)
     89        14377.ippx046   (Detached)
     90        20417.ippx031   (Detached)
     91        30106.ippx023   (Detached)
     92        11621.ippx009   (Detached)
     93        10348.ippx003   (Detached)
     94        13826.ippx044   (Detached)
     95        13109.ippx042   (Detached)
     96        11023.ippx004   (Detached)
     97        12503.ippx036   (Detached)
     98        12892.ippx041   (Detached)
     99        25079.ippx006   (Detached)
     100        13980.ippx045   (Detached)
     101        28605.ippx014   (Detached)
     102        14692.ippx047   (Detached)
     103        27623.ippx007   (Detached)
     104        13412.ippx017   (Detached)
     105        13945.ippx019   (Detached)
     106        13492.ippx043   (Detached)
     107        12115.ippx010   (Detached)
     108        16621.ippx037   (Detached)
     109        28308.ippx013   (Detached)
     11049 Sockets in /var/run/screen/S-ippdvo2.
     111}}}
     112
     113you can check the status of loaders by the following:
     114
     115{{{
     116cd ~heather/checkloaders
     117perl checkloaders.pl loaderlist.txt
     118}}}
     119
     120It will output the status of loaders:
     121
     122{{{
     123loader.py running on ippx018
     124loader.py running on ippx019
     125problem with ippx020
     126problem with ippx021
     127loader.py running on ippx022
     128loader.py running on ippx023
     129problem with ippx024
     130loader.py running on ippx025
     131problem with ippx026
     132problem with ippx027
     133loader.py running on ippx028
     134problem with ippx029
     135loader.py running on ippx030
     136problem with ippx031
     137problem with ippx032
     138loader.py running on ippx033
     139loader.py running on ippx034
     140loader.py running on ippx035
     141loader.py running on ippx036
     142loader.py running on ippx037
     143loader.py running on ippx038
     144}}}
     145
     146In general, only need to worry about the ones with 'problem'- attach to them (screen -r ippx031 for example), and see what's going on.   mysql/io/neb/gpc1 weirdness will cause the loaders to die if they encounter any problems.  Generally ok to hit up and resume, unless it indicates it is out of work:
     147
     148{{{
     1492016-06-02 13:38:05.658 |    INFO | --------------------------------------------------------------------------
     1502016-06-02 13:38:05.661 |    INFO | No outstanding boxes                    nothing to do here
     1512016-06-02 13:38:05.664 |    INFO | Boxes with unprocessed data             0
     1522016-06-02 13:38:05.664 |    INFO | numAttempts                             0
     1532016-06-02 13:38:05.664 |    INFO | done with processing boxes, numAttempts: 1
     154USING parallel
     1552016-06-02 13:38:05.677 |    INFO | No outstanding boxes                    nothing to do here
     1562016-06-02 13:38:05.677 |    INFO | Boxes with unprocessed data             0
     1572016-06-02 13:38:05.678 |    INFO | numAttempts                             1
     1582016-06-02 13:38:05.680 |    INFO | done with processing boxes, numAttempts: 2
     159USING parallel
     1602016-06-02 13:38:05.690 |    INFO | loader.py exited                        completed
     161}}}
     162
     163If it is out of work, move on to the next skychunk to load, being extra careful NOT to have the same skychunk loaded by 2 loaders at the same time (causes race conditions)