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

[LDM #HHK-349534]: LDM data feed down

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #HHK-349534]: LDM data feed down
  • Date: Mon, 24 Jul 2017 13:37:43 -0600
Hi Wanhong,

re:
> Tested on our servers: weather.uky.edu     and      weather3.ca.uky.edu
> 
> 
> 
> [ldm@weather3 ~]$ notifyme -vl- -f "IDS|DDPLUS" -h idd.unidata.ucar.edu -o 
> 3600
> Jul 24 18:53:00 notifyme[24344] NOTE: Starting Up: idd.unidata.ucar.edu: 
> 20170724175300.955 TS_ENDT {{IDS|DDPLUS, ".*"}}
> Jul 24 18:53:00 notifyme[24344] NOTE: LDM-5 desired product-class: 
> 20170724175300.955 TS_ENDT {{IDS|DDPLUS,  ".*"}}
> Jul 24 18:53:00 notifyme[24344] INFO: Resolving idd.unidata.ucar.edu to 
> 128.117.140.3 took 0.001386 seconds
> Jul 24 18:53:01 notifyme[24344] ERROR: NOTIFYME(idd.unidata.ucar.edu): 7: 
> Access denied by remote server
> Jul 24 18:53:26 notifyme[24344] NOTE: LDM-5 desired product-class: 
> 20170724175300.955 TS_ENDT {{IDS|DDPLUS,  ".*"}}
> Jul 24 18:53:26 notifyme[24344] INFO: Resolving idd.unidata.ucar.edu to 
> 128.117.140.3 took 0.000971 seconds
> Jul 24 18:53:26 notifyme[24344] ERROR: NOTIFYME(idd.unidata.ucar.edu): 7: 
> Access denied by remote server
> ^CJul 24 18:53:36 notifyme[24344] NOTE: exiting

This is very strange since the LDM log files on all of the real server backends
of the idd.unidata.ucar.edu cluster have no entries for attempted 'notifyme'
connections from any machine from the uky.edu domain, nor do they show that
any 'notifyme' connections from machines from the 208.67 domain are being 
denied.

What is the result of:

<as 'ldm'>
telnet idd.unidata.ucar.edu 388

Also, what is the result of:

<as 'ldm'>
notifyme -vl- -f ANY -h idd.tamu.edu

and:

notifyme -vl- -f ANY -h idd.meteo.psu.edu

re:
> [ldm@weather3 ~]$ notifyme -vl- -f "IDS|DDPLUS" -h weather2.admin.niu.edu -o 
> 3600
> Jul 24 18:54:14 notifyme[24345] NOTE: Starting Up: weather2.admin.niu.edu: 
> 20170724175414.370 TS_ENDT {{IDS|DDPLUS, ".*"}}
> Jul 24 18:54:14 notifyme[24345] NOTE: LDM-5 desired product-class: 
> 20170724175414.370 TS_ENDT {{IDS|DDPLUS,  ".*"}}
> Jul 24 18:54:14 notifyme[24345] INFO: Resolving weather2.admin.niu.edu to 
> 131.156.224.26 took 0.001468 seconds
> Jul 24 18:55:04 notifyme[24345] NOTE: LDM-5 desired product-class: 
> 20170724175414.370 TS_ENDT {{IDS|DDPLUS,  ".*"}}
> Jul 24 18:55:04 notifyme[24345] INFO: Resolving weather2.admin.niu.edu to 
> 131.156.224.26 took 0.000993 seconds
> ^CJul 24 18:55:17 notifyme[24345] NOTE: exiting

The output from this 'notifyme' test and my test of the same here in Unidata 
show
that there is no LDM running on weather2.admin.niu.edu, or, if there is one
running, it is not responding.

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: HHK-349534
Department: Support IDD
Priority: Normal
Status: Open
===================
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.