IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 2 and Version 3 of PS1_IPP_Czarlog_20190204


Ignore:
Timestamp:
Feb 5, 2019, 3:29:24 PM (7 years ago)
Author:
fairlamb
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PS1_IPP_Czarlog_20190204

    v2 v3  
    2727  JRF: Will be meeting with Mark later to go through some errors that were reported in the logs (TODO: update this)
    2828
     29JRF: stdscience error log reported too many connections to the database. This had come up previously (in the past month):
     30{{{
     31 -> psDBAlloc (psDB.c:166): Database error generated by the server
     32     Failed to connect to database.  Error: Too many connections
     33 -> faketoolConfig (faketoolConfig.c:373): unknown psLib error
     34     Can't configure database
     35 -> main (faketool.c:70): (null)
     36     failed to configure
     37Unable to perform faketool -addproces
     38
     39config error for: fake_imfile.pl --exp_id 1450315 --fake_id 2062988 --class_id XY31 --chiproot=neb://ipp090.0/gpc1/OSS.nt/2019/02/05//o8519g0140o.1450315/o8519g0140o.1450315.ch.2127506 --camroot=neb://any/gpc1/OSS.nt/2019/02/05//o8519g0140o.1450315/o8519g0140o.1450315.cm.2093978 --camera GPC1 --outroot neb://ipp090.0/gpc1/OSS.nt/2019/02/05//o8519g0140o.1450315/o8519g0140o.1450315.fk.2062988 --reduction SWEETSPOT --dbname gpc1 --verbose
     40job exit status: 3
     41job host: ippc69
     42job dtime: 3.755007
     43job exit date: Mon Feb  4 20:22:07 2019
     44*** stdout ***
     45stdout 13038
     46}}}
     47
     48and another:
     49
     50{{{
     51 -> psDBAlloc (psDB.c:166): Database error generated by the server
     52     Failed to connect to database.  Error: Too many connections
     53 -> faketoolConfig (faketoolConfig.c:373): unknown psLib error
     54     Can't configure database
     55 -> main (faketool.c:70): (null)
     56     failed to configure
     57Unable to perform faketool -addproces
     58
     59config error for: fake_imfile.pl --exp_id 1450315 --fake_id 2062988 --class_id XY54 --chiproot=neb://ipp112.0/gpc1/OSS.nt/2019/02/05//o8519g0140o.1450315/o8519g0140o.1450315.ch.2127506 --camroot=neb://any/gpc1/OSS.nt/2019/02/05//o8519g0140o.1450315/o8519g0140o.1450315.cm.2093978 --camera GPC1 --outroot neb://ipp112.0/gpc1/OSS.nt/2019/02/05//o8519g0140o.1450315/o8519g0140o.1450315.fk.2062988 --reduction SWEETSPOT --dbname gpc1 --verbose
     60job exit status: 3
     61job host: ippc79
     62job dtime: 3.872324
     63job exit date: Mon Feb  4 20:22:07 2019
     64*** stdout ***
     65stdout 11212
     66}}}
     67
     68JRF: The stdscience log last night on PS1 showed a bunch of errors reported around 20:30. The majority of these were on ippc118. Look at the ganglia logs there was a spike in network activity, up to about 17Mb, but not too large that it should cause an issue. Either way the tasks that failed reverted successfully and continued on after this.
     69
     70JRF: MEH will look into the reported nightly_science.pl errors. Some are reported for gpc2 in the gpc1 logs!!
     71e.g.
     72
     73{{{
     74failure for: nightly_science.pl --queue_diffs --date 2019-02-05 --dbname gpc2 --camera GPC2
     75job exit status: 2
     76job host: localhost
     77job dtime: 8.072818
     78job exit date: Mon Feb  4 21:04:02 2019
     79}}}
     80Commented out the use of gpc2 dates in the 'stdscience/input' file. Believe this is the reason that there are gpc2 errors being reported in the gpc1 logs above.
     81
     82JRF: killed a 4 day old job in the database that was run as ippuser to query something. WARNING: very dangerous to go around killing jobs.
    2983
    3084=== Wednesday : 2019.02.06 ===
     85
     86JRF: ME, MEH, and TdB shall be going though reprocessing some data for Rob without some pixels removed (as an NEO is suspected to be falling into a masked area).
    3187
    3288=== Thursday : 2019.02.07 ===