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

[LDM #HNT-424908]: Fwd: FW: Ldm mcidas

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 #HNT-424908]: Fwd: FW: Ldm mcidas
  • Date: Wed, 12 Jul 2006 09:47:48 -0600
Randy,

> Here is the log file from noaapnew
> Jul 12 15:25:55 noaapnew pqcheck[4340]: Starting Up
> (4332)
> Jul 12 15:25:55 noaapnew pqcheck[4340]: The
> writer-counter of the product-queue is 0
> Jul 12 15:25:55 noaapnew pqcheck[4340]: Exiting
> Jul 12 15:25:55 noaapnew rpc.ldmd[4364]: Starting Up
> (version: 6.2.1; built: Mar  2 2005 23:14:33)
> Jul 12 15:25:55 noaapnew dvbs_multicast[4365]:
> Starting Up 1.1.3
> Jul 12 15:25:55 noaapnew readnoaaport[4367]: Starting
> Up 1.1.3
> Jul 12 15:30:56 noaapnew rpc.ldmd[4364]: Denying
> connection from noaapxcd
> Jul 12 15:31:29 noaapnew last message repeated 7 times

The fact that the LDM on Noaapnew says that it's denying
a connection from the not fully-qualified hostname "noaapxcd"
indicates that the gethostbyaddr() system call on Noaapnew
is returning that as the fully-qualified hostname (which it
isn't).  Because the hostname isn't fully-qualified, it won't
match the ALLOW entry

    allow   ANY     ^[a-z]*\.it-protect\.com$

I think you'll either have to fix your resolver installation
so that the gethostbyaddr() system-call returns a fully-qualified
hostname or add an ALLOW entry like this

    allow ANY ^noaapxcd$

to the LDM configuration-file on Noaapnew.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: HNT-424908
Department: Support LDM
Priority: Normal
Status: Closed