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

20031029: New System at UNI (cont.)

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: 20031029: New System at UNI (cont.)
  • Date: Wed, 29 Oct 2003 13:52:09 -0700
>From: "Patrick O'Reilly" <address@hidden>
>Organization: UNI
>Keywords: 200310241337.h9ODbAOb017830 IDD node

Patrick,

>Got the new system set up with the LDM and am trying to feed it from my
>current LDM machine.  Getting no data.  From the feed machine's (Solaris 8)
>ldm log:
>
>blizzard rpc.ldmd: Denying connection from thunder.storm.uni.edu
>
>From thunder.storm.uni.edu (RedHat 9) log:
>
>thunder blizzard ERROR requester6:c:459; ldm_clnt.c:286: nullproc_6 failure
>to blizzard.storm.uni.edu; ldm_clnt.c:142: RPC: Unable to receive; errno=
>Connection reset by peer
>
>I will research this, but was hoping you gurus have an idea why blizzard is
>denying connection from thunder.

The most likely reason for this is that reverse name lookup has not
yet been established for your new machine, thunder.storm.uni.edu.

This is bourne out by using nslookup for forward and reverse lookups:

% nslookup thunder.storm.uni.edu
Server:         128.117.140.62
Address:        128.117.140.62#53

Non-authoritative answer:
Name:   thunder.storm.uni.edu
Address: 134.161.223.209

% nslookup 134.161.223.209
Server:         128.117.140.62
Address:        128.117.140.62#53

Non-authoritative answer:
209.223.161.134.in-addr.arpa    name = thunder.storm.uni.edu.

To get things working while the DNS setup is being finished, you could
add an entry in blizzards /etc/hosts file:

134.161.223.209 thunder.storm.uni.edu

If you decide to go this route, you should make sure to remember to
remove the entry after the DNS issue is resolved.

Tom