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

[LDM #TFK-703998]: Products not pulled into LDM queue



Justin,

Was the LDM on the backup computer, vm-lnx-ncodf1, running and receiving data 
*before* it was made the main LDM?

The log messages

> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] NOTE: 
> Data-product with signature 5287fd0a33c9eca90dbf1eee94a1f8fe wasn't found in 
> product-queue
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] NOTE: 
> Starting Up(6.12.14/6): 20180522181822.589 TS_ENDT {{WMO, "^[A-Z].*"}}, 
> SIG=5287fd0a33c9eca90dbf1eee94a1f8fe, Primary
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] NOTE: 
> topo:  vm-lnx-ncodf1.ncep.noaa.gov {{WMO, (.*)}}
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] INFO: 
> sending:      20213 20180522185032.317     HDS 55167869  SDUS62 KMLB 
> 221849/pNSWMLB
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] INFO: 
> sending:        119 20180522185032.493 IDS|DDPLUS 8897828  SRGA20 KWAL 221850

indicate that 1) the backup LDM connected successfully; 2) the last product the 
backup LDM successfully received wasn't in the NOAAPort LDM's queue (I wouldn't 
expect it to be); and 3) the first WMO product the NOAAPort LDM sent to the 
backup LDM was created at 18:50:32Z -- almost a half-hour earlier. This product 
would have been near the oldest end of the queue because the NOAAAPort LDM 
would have tried to start sending products from one hour ago (from around 
18:18:22Z).

This is exactly what should have happened.

This was in your previous email:

> As a point of reference the next WUUS51 product was at 19:25Z and I see it 
> was sent to vm-lnx-ncodf1
...
> May 22 19:25:35 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] INFO: 
> sending: 2134 20180522192535.014 IDS|DDPLUS 55276307 WUUS51 KLWX 221925 
> /pSVRLWX

So by 19:25:35, everything was working as it should.

I don't understand how the products in question were not received by your 
downstream user.

One question, though, how do you know they weren't received?

> Sure, here they are:
> 
> May 22 19:18:22 vm-lnx-sbn2 ldmd[20540] INFO: Resolving 140.90.100.144 to
> vm-lnx-ncodf1.ncep.noaa.gov took 0.015153 seconds
> May 22 19:18:22 vm-lnx-sbn2 ldmd[20542] INFO: Resolving 140.90.100.144 to
> vm-lnx-ncodf1.ncep.noaa.gov took 0.015152 seconds
> May 22 19:18:22 vm-lnx-sbn2 ldmd[20543] INFO: Resolving 140.90.100.144 to
> vm-lnx-ncodf1.ncep.noaa.gov took 0.000584 seconds
> May 22 19:18:22 vm-lnx-sbn2 ldmd[20541] INFO: Resolving 140.90.100.144 to
> vm-lnx-ncodf1.ncep.noaa.gov took 0.016074 seconds
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov[20540] INFO:
> Connection from vm-lnx-ncodf1.ncep.noaa.gov
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov[20543] INFO:
> Connection from vm-lnx-ncodf1.ncep.noaa.gov
> May 22 19:18:22 vm-lnx-sbn2 ldmd[20539] INFO: Resolving 140.90.100.144 to
> vm-lnx-ncodf1.ncep.noaa.gov took 0.016527 seconds
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov[20540] INFO:
> Resolving 140.90.100.144 to vm-lnx-ncodf1.ncep.noaa.gov took 6e-06 seconds
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov[20542] INFO:
> Connection from vm-lnx-ncodf1.ncep.noaa.gov
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov[20543] INFO:
> Resolving 140.90.100.144 to vm-lnx-ncodf1.ncep.noaa.gov took 7e-06 seconds
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov[20542] INFO:
> Resolving 140.90.100.144 to vm-lnx-ncodf1.ncep.noaa.gov took 7e-06 seconds
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov[20539] INFO:
> Connection from vm-lnx-ncodf1.ncep.noaa.gov
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov[20539] INFO:
> Resolving 140.90.100.144 to vm-lnx-ncodf1.ncep.noaa.gov took 7e-06 seconds
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov[20541] INFO:
> Connection from vm-lnx-ncodf1.ncep.noaa.gov
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov[20541] INFO:
> Resolving 140.90.100.144 to vm-lnx-ncodf1.ncep.noaa.gov took 7e-06 seconds
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] INFO:
> [node.c:1128] No such value "enable-anti-DOS" in node "/server"
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] INFO:
> [globals.c:412] Using default value: TRUE
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20539] INFO:
> [node.c:1128] No such value "enable-anti-DOS" in node "/server"
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20539] INFO:
> [globals.c:412] Using default value: TRUE
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20540] INFO:
> [node.c:1128] No such value "enable-anti-DOS" in node "/server"
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20540] INFO:
> [globals.c:412] Using default value: TRUE
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20543] INFO:
> [node.c:1128] No such value "enable-anti-DOS" in node "/server"
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20543] INFO:
> [globals.c:412] Using default value: TRUE
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20541] INFO:
> [node.c:1128] No such value "enable-anti-DOS" in node "/server"
> May 22 19:18:22 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20541] INFO:
> [globals.c:412] Using default value: TRUE
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] NOTE:
> Data-product with signature 5287fd0a33c9eca90dbf1eee94a1f8fe wasn't found
> in product-queue
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] NOTE:
> Starting Up(6.12.14/6): 20180522181822.589 TS_ENDT {{WMO, "^[A-Z].*"}},
> SIG=5287fd0a33c9eca90dbf1eee94a1f8fe, Primary
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] NOTE:
> topo:  vm-lnx-ncodf1.ncep.noaa.gov {{WMO, (.*)}}
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] INFO:
> sending:      20213 20180522185032.317     HDS 55167869  SDUS62 KMLB 221849
> /pNSWMLB
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20542] INFO:
> sending:        119 20180522185032.493 IDS|DDPLUS 8897828  SRGA20 KWAL
> 221850
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20539] NOTE:
> Data-product with signature 0332d0418c33d4235f50c0f73e07ed8b wasn't found
> in product-queue
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20539] NOTE:
> Starting Up(6.12.14/6): 20180522181822.583 TS_ENDT {{NGRID, "(YAX|YLX)...
> KKCI"}}, SIG=0332d0418c33d4235f50c0f73e07ed8b, Primary
> May 22 19:18:23 vm-lnx-sbn2 vm-lnx-ncodf1.ncep.noaa.gov(feed[20539] NOTE:
> topo:  vm-lnx-ncodf1.ncep.noaa.gov {{NGRID, (.*)}}


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: TFK-703998
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.