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

[LDM #ZOC-298338]: Missing data problems



Lou,
 
> It looks like the data we're receiving on ldm1 for this region is old
> data.  Here's an example.  As you can see this data is (48-15=33)
> minutes old which appears as down by most people even though its just
> very high latency.
> 
> > Jun 15 15:48:06 pqutil INFO:    11397 20070615150259.395 NEXRAD2 872017  
> > L2-BZIP2/KBMX/20070615150156/872/17

I'm seeing up-to-date data-products from the Southern Region being
received by NWS-LDM1.  Here's and example of what the SRHQ is
receiving:

bash-3.00$ notifyme -vl- -f NEXRAD2 -h 216.38.80.15
Jun 15 19:37:35 notifyme[12736] NOTE: Starting Up: 216.38.80.15: 
20070615193735.087 TS_ENDT {{NEXRAD2,  ".*"}}
Jun 15 19:37:35 notifyme[12736] NOTE: LDM-5 desired product-class: 
20070615193735.087 TS_ENDT {{NEXRAD2,  ".*"}}
Jun 15 19:37:35 notifyme[12736] NOTE: NOTIFYME(216.38.80.15): OK
Jun 15 19:37:42 notifyme[12736] INFO:     4647 20070615193735.394 NEXRAD2 
185045  L2-BZIP2/KMRX/20070615193448/185/45
Jun 15 19:37:42 notifyme[12736] INFO:    23522 20070615193735.155 NEXRAD2 
327019  L2-BZIP2/KAMA/20070615193508/327/19
Jun 15 19:37:42 notifyme[12736] INFO:    12686 20070615193735.423 NEXRAD2 
539048  L2-BZIP2/KMAF/20070615193438/539/48
...

and here's an example of what the LDM on NWS-LDM1 is receiving
from the southern region (I used the command above to get a list
of station identifiers):

bash-3.00$ ldmadmin watch -p 'KMLB|KAMX|KSRX|KLBB|KMAF|KGWX|KHTX|KSHV|KSJT|KTLH'
Jun 15 19:38:23 pqutil INFO:    12250 20070615193815.980 NEXRAD2 124046  
L2-BZIP2/KCAE/20070615193520/124/46
Jun 15 19:38:23 pqutil INFO:    17211 20070615193815.920 NEXRAD2 28008  
L2-BZIP2/KJAX/20070615193719/28/8
Jun 15 19:38:23 pqutil INFO:    16269 20070615193815.967 NEXRAD2 26021  
L2-BZIP2/KLTX/20070615193535/26/21

Incidentally,  the LDM configuration-file, etc/ldmd.conf, 
executes the "pqact" utility, whose configuration-file,
etc/pqact.conf, contains some actions --- but not for
radar data.  If you're not going to receive and data on
which "pqact" should act, then you should comment-out
the "pqact" EXEC entry in the LDM configuration-file to
reduce the load on the CPU.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ZOC-298338
Department: Support LDM
Priority: Urgent
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.