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

[IDD #MPQ-937932]: Local Data Manager Question



Hi Mary,

re:
> I do see all the LDM e-mails and try to digest what I can. Sure appreciate
> your diagnosing the problem! I should have written in December when I
> wondered if that was something I should pay attention to.

No worries from my point of view.

re:
> My user reports still not getting the LIGHTNING data:
> 
> ----------------------------------------------------------------------------------------------------------------
> John Graham <address@hidden>
> 1:36 PM (17 minutes ago)
> to jjgraham, Mary, Dan
> Here is what I see
> 
> [ldm@aether nldn]$ notifyme -vl - -h aeolus.ucsd.edu -f LIGHTNING
> May 10 18:05:38 notifyme[16125] NOTE: Starting Up: aeolus.ucsd.edu: 
> 20160510180538.660 TS_ENDT {{LIGHTNING,  ".*"}}
> May 10 18:05:38 notifyme[16125] NOTE: LDM-5 desired product-class: 
> 20160510180538.660 TS_ENDT {{LIGHTNING,  ".*"}}
> May 10 18:05:38 notifyme[16125] INFO: Resolving aeolus.ucsd.edu to 
> 132.239.114.58 took 0.210779 seconds
> May 10 18:05:38 notifyme[16125] NOTE: NOTIFYME(aeolus.ucsd.edu): OK
> 
> 
> May 10 18:06:02 notifyme[16125] INFO:     1204 20160510180554.556 LIGHTNING 
> 000  2016131180554
> May 10 18:07:02 notifyme[16125] INFO:     1036 20160510180654.701 LIGHTNING 
> 000  2016131180654
> May 10 18:08:03 notifyme[16125] INFO:      784 20160510180754.847 LIGHTNING 
> 000  2016131180754
> May 10 18:09:03 notifyme[16125] INFO:     1176 20160510180855.000 LIGHTNING 
> 000  2016131180854
> May 10 18:10:03 notifyme[16125] INFO:      840 20160510180955.170 LIGHTNING 
> 000  2016131180955
> May 10 18:11:03 notifyme[16125] INFO:      868 20160510181055.339 LIGHTNING 
> 000  2016131181055
> May 10 18:12:03 notifyme[16125] INFO:      896 20160510181155.491 LIGHTNING 
> 000  2016131181155
> May 10 18:13:03 notifyme[16125] INFO:     1456 20160510181255.653 LIGHTNING 
> 000  2016131181255
> May 10 18:14:04 notifyme[16125] INFO:     1372 20160510181355.807 LIGHTNING 
> 000  2016131181355
> May 10 18:15:04 notifyme[16125] INFO:     1428 20160510181455.957 LIGHTNING 
> 000  2016131181455
> May 10 18:16:04 notifyme[16125] INFO:     1484 20160510181556.111 LIGHTNING 
> 000  2016131181556
> May 10 18:17:04 notifyme[16125] INFO:     1232 20160510181656.239 LIGHTNING 
> 000  2016131181656
> 
> These just look like a heartbeat saying im alive but no data

No, these are not heartbeats.  Heartbeat products would all be 84 bytes
in length.  The 'notifyme' listing shows that the size of the products
vary (the size in bytes is the field just to the right of INFO:), but
they are not very large.  It is not surprising that the product sizes
are not large as we are not yet in lightning season.

> ------------------------------------------------------------------------------------------------------
> 
> When I run this on aeolus I get:
> 
> [ldm@aeolus ~]$ notifyme -vl- -f LIGHTNING
> 
> May 10 20:55:26 notifyme[17848] NOTE: Starting Up: localhost: 
> 20160510205526.410 TS_ENDT {{LIGHTNING,  ".*"}}
> May 10 20:55:26 notifyme[17848] NOTE: LDM-5 desired product-class: 
> 20160510205526.410 TS_ENDT {{LIGHTNING,  ".*"}}
> May 10 20:55:26 notifyme[17848] INFO: Resolving localhost to 127.0.0.1 took 
> 0.002844 seconds
> May 10 20:55:26 notifyme[17848] NOTE: NOTIFYME(localhost): OK
> 
> Does something seem amiss to you?

No.

When I ran 'notifyme' on aeolus just now, I see products being received:

[ldm@aeolus ~]$ notifyme -vl- -f LIGHTNING -o 3600
May 10 21:43:32 notifyme[21618] NOTE: Starting Up: localhost: 
20160510204332.514 TS_ENDT {{LIGHTNING,  ".*"}}
May 10 21:43:32 notifyme[21618] NOTE: LDM-5 desired product-class: 
20160510204332.514 TS_ENDT {{LIGHTNING,  ".*"}}
May 10 21:43:32 notifyme[21618] INFO: Resolving localhost to 127.0.0.1 took 
0.003223 seconds
May 10 21:43:32 notifyme[21618] NOTE: NOTIFYME(localhost): OK
May 10 21:43:36 notifyme[21618] INFO:     4452 20160510213625.828 LIGHTNING 000 
 2016131213625
May 10 21:43:45 notifyme[21618] INFO:     6076 20160510213725.984 LIGHTNING 000 
 2016131213725
May 10 21:43:55 notifyme[21618] INFO:     4536 20160510213826.127 LIGHTNING 000 
 2016131213826
 ...

So, there definitely is NLDN data being received on aeolus in the IDD
LIGHTNING data feed.

While logged onto aeolus as 'ldm' just now, I looked through the LDM
log file to see who is REQUESTing LIGHTNING data:

[ldm@aeolus ~]$ grep topo logs/ldmd.log | grep LIGHTNING
May 10 10:51:14 aeolus aether.ucsd.edu(noti)[1462] NOTE: topo:  aether.ucsd.edu 
LIGHTNING
May 10 11:05:38 aeolus aether.ucsd.edu(noti)[2880] NOTE: topo:  aether.ucsd.edu 
LIGHTNING
May 10 13:34:45 aeolus aether.ucsd.edu(noti)[16213] NOTE: topo:  
aether.ucsd.edu LIGHTNING
May 10 13:55:26 aeolus 127.0.0.1(noti)[17849] NOTE: topo:  127.0.0.1 LIGHTNING
May 10 14:43:32 aeolus 127.0.0.1(noti)[21619] NOTE: topo:  127.0.0.1 LIGHTNING

The 'noti' entries are from someone (you?) running a 'notifyme'; the
other entries shows that the machine aether.ucsd.edu has REQUESTed the
LIGHTNING feed AND has been granted access.

Now, assuming that John's machine is aether.ucsd.edu, I went to our
real-time stats pages to see if it is receiving the LIGHTNING feed:

Unidata HomePage
http://www.unidata.ucar.edu

  Data -> IDD Operational Status
  http://rtstats.unidata.ucar.edu/rtstats/

    Statistics by Host (dropdown under Real-Time IDD Statistics at top)
    http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex

      aether.ucsd.edu [6.12.6]
      http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex?aether.ucsd.edu

        LIGHTNING volume
        
http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?LIGHTNING+aether.ucsd.edu

The plot generated at the last link shows that aether.ucsd is receiving
the same volume of LIGHTNING data as aeolus.ucsd.edu.  The volume plot
of LIGHTNING data on aeolus can be seen at:

http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?LIGHTNING+aeolus.ucsd.edu

This means that aether.ucsd.edu _is_ receiving the LIGHTNING data.
If aether.ucsd.edu is, in fact, John's machine, then it means that he
is not processing the LIGHTNING data that he is receiving.

re:
> Appreciate your help!

No worries.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: MPQ-937932
Department: Support IDD
Priority: Normal
Status: Closed