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

20040517: LDM problem: Denying connection from localhost.loca l domain

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: 20040517: LDM problem: Denying connection from localhost.loca l domain
  • Date: Mon, 17 May 2004 16:48:09 -0600
Rodney,

[I'm really sorry.  I forgot about you.  I'm taking care of my wife
while she recovers from rotator-cuff surgery and my work-routine is all
messed up.]

>Date: Mon, 17 May 2004 15:23:59 -0700
>From: "Jacques, Rodney" <address@hidden>
>Organization: US NAVY/NAVPACMETOCCEN
>To: "'Steve Emmerson'" <address@hidden>
>Subject: RE: 20040513: LDM problem: Denying connection from localhost.loca l 
>domain 
> Keywords: 200405121919.i4CJJRtK023189

The above message contained the following:

> I am bit confused with the error that is in the ldmd.log file. Our sys
> admin person checked the etc/hosts file and all appeared in order.
>
> Could you review the attached files and see if anything is out of
> order with our ldm configuration?

The following logfile entries:

    May 17 21:29:04 granite rpc.ldmd[30504]: Starting Up (version: 6.0.10; 
built: Apr 30 2003 16:46:37) 
    ...
    May 17 21:29:09 granite rpc.ldmd[30504]: Denying connection from 
localhost.localdomain 
    May 17 21:29:09 granite feedme[7973]: FEEDME(localhost): 7: Access denied 
by remote server 
    May 17 21:29:34 granite rpc.ldmd[30504]: Denying connection from 
localhost.localdomain 
    May 17 21:29:34 granite feedme[7973]: FEEDME(localhost): 7: Access denied 
by remote server 

indicate that a feedme(1) process is running on Granite and is requesting
data-products from the LDM.  The feedme(1) program is a holdover from LDM-4.
It is completely unnecessary, useless, deprecated, and shouldn't exist.

Why is it running?  I didn't see an EXEC entry for it in your LDM 
configuration-file (ldmd.conf).

Oddly, the feedme(1) process shouldn't be rejected by the LDM -- even
though it shouldn't be running.  The following entry in your LDM 
configuration-file

    ALLOW       ANY     
^((localhost|loopback)|(127\.0\.0\.1\.?$)|([a-z].*\.unidata\.ucar\.edu\.?$))

should allow requests for data from host "localhost...", of which 
"localhost.localdomain" is but one example.

Find out where that feedme(1) process is being started and stop it!

Can you successfully execute a notifyme(1) process on Granite that connects
to the LDM on Granite?

Regards,
Steve Emmerson