[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #MKY-400850]: Continuing issue with no TIRC headers getting into secondary LDM box

Gilbert,

It's possible that a typo somewhere is messing things up. Do the following very 
carefully:

On ldm01.allisonhouse.com, execute the command

    notifyme -vl- -f NOTHER -p TIRC

in one window and, in another window, the command

    notifyme -vl- -f NOTHER -p TIRC -h <bird01_hostname>

(where <bird01_hostname> is the fully-qualified hostname of Bird01). Then on 
Bird01, execute the command

    notifyme -vl- -f NOTHER -p TIRC

Cut and paste the commands so that there are no typos.

You should see something from the first two notifyme(1)s shortly after seeing 
something from the notifyme(1) executing on Bird01. If not, then send me the 
output from all three notifyme(1)s. Truncate the output if it's too voluminous 
but make sure that the timestamps overlap. Also include the output from 
executing the command

    uldbutil | fgrep ldm01

on Bird01 *before* terminating the notifyme(1) that's executing on Ldm01 and 
requesting from Bird01.

> As it turns out, even with the adjustment of the time servers, and
> verifying that we have no isses there, we continue to have issues
> relaying GOES-16 data to a second box. Our satellite ingester, bird01,
> receives the data just fine:
> 
> From bird01:
> /home/gilbert.sebenste% notifyme -vl- -p TINC
> /home/gilbert.sebenste% clear
> /home/gilbert.sebenste% notifyme -vl- -p TIRC
> Aug 26 18:50:01 notifyme[13283] NOTE: Starting Up: localhost: 
> 20170826185001.961 TS_ENDT {{ANY,  "TIRC"}}
> Aug 26 18:50:01 notifyme[13283] NOTE: LDM-5 desired product-class: 
> 20170826185001.961 TS_ENDT {{ANY,  "TIRC"}}
> Aug 26 18:50:01 notifyme[13283] INFO: Resolving localhost to 127.0.0.1 took 
> 0.000377 seconds
> Aug 26 18:50:01 notifyme[13283] NOTE: NOTIFYME(localhost): OK
> Aug 26 18:50:08 notifyme[13283] INFO:   858117 20170826185008.373  NOTHER 
> 13426787  TIRC05 KNES 261847 PAS
> Aug 26 18:50:08 notifyme[13283] INFO:   861317 20170826185008.662  NOTHER 
> 13426788  TIRC03 KNES 261847 PAS
> Aug 26 18:50:09 notifyme[13283] INFO:   858997 20170826185009.137  NOTHER 
> 13426789  TIRC01 KNES 261847 PAS
> Aug 26 18:50:09 notifyme[13283] INFO:   389285 20170826185009.371  NOTHER 
> 13426790  TIRC01 KNES 261847 PAY
> Aug 26 18:50:09 notifyme[13283] INFO:   381148 20170826185009.593  NOTHER 
> 13426791  TIRC05 KNES 261847 PAY
> Aug 26 18:50:09 notifyme[13283] INFO:   395190 20170826185009.654  NOTHER 
> 13426792  TIRC03 KNES 261847 PAY
> Aug 26 18:50:09 notifyme[13283] INFO:   228910 20170826185009.864  NOTHER 
> 13426793  TIRC02 KNES 261847 PCU
> Aug 26 18:50:10 notifyme[13283] INFO:  1552952 20170826185010.616  NOTHER 
> 13426794  TIRC02 KNES 261847 PDH
> ^CAug 26 18:50:10 notifyme[13283] NOTE: exiting
> 
> Yet, when we request TIRC products on another server, they stop after a
> little while.
> 
> notifyme -vl- -p TIRC
> 20170826T184754.841161Z notifyme[31144] NOTE notifyme.c:385:main() Starting 
> Up: localhost: 20170826184754.840992 TS_ENDT {{ANY, "TIRC"}}
> 20170826T184754.841194Z notifyme[31144] NOTE ldm5_clnt.c:460:forn5() LDM-5 
> desired product-class: 20170826184754.840992 TS_ENDT {{ANY, "TIRC"}}
> 20170826T184754.841459Z notifyme[31144] INFO error.c:236:err_log() Resolving 
> localhost to 127.0.0.1 took 0.000219 seconds
> 20170826T184754.843834Z notifyme[31144] NOTE ldm5_clnt.c:294:forn_signon() 
> NOTIFYME(localhost): OK
> ^C20170826T185248.464532Z notifyme[31144] NOTE notifyme.c:66:cleanup()
> exiting
> 
> (nothing)
> 
> uldbutil on bird01, our satellite ingester, shows:
> 
> 16358 6 feeder ldm01.allisonhouse.com 20170826144427.589 TS_ENDT {{NOTHER, 
> "TIRC[0-1][0-9] KNES"}} primary
> 16361 6 feeder ldm01.allisonhouse.com 20170826144427.589 TS_ENDT {{NOTHER, 
> "TIS.[0-1][0-9] KNES"}} primary
> 
> Again: I am now synchronizing all our time servers (and just did this
> morning, a manual restart of ntp), and this is still occurring.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: MKY-400850
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.