[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[IDD #QZH-192791]: I can't receive NIMAGE from either papagayo or idd.unidata
- Subject: [IDD #QZH-192791]: I can't receive NIMAGE from either papagayo or idd.unidata
- Date: Tue, 25 Apr 2006 14:07:13 -0600
Hi Pete (and Clint),
re:
> I have been unable to receive the NIMAGE feed from either my
> primary (papagayo.unl.edu) or the alternate I've been using
> for some time (idd.unidata.ucar.edu)
For some reason reverse DNS for your machine is not working:
less ~ldm/logs/ldmd.log
...
Apr 25 19:33:51 uni1 rpc.ldmd[12890] WARN: Couldn't resolve "144.92.131.244" to
a hostname in 19.9999
seconds
Apr 25 19:33:51 uni1 rpc.ldmd[12890] NOTE: Denying connection from
"144.92.131.244"
...
% nslookup f5.aos.wisc.edu
Server: 128.117.140.62
Address: 128.117.140.62#53
Non-authoritative answer:
Name: f5.aos.wisc.edu
Address: 144.92.131.244
% nslookup 144.92.131.244
;; Got SERVFAIL reply from 128.117.140.62, trying next server
Server: 128.117.140.56
Address: 128.117.140.56#53
** server can't find 244.131.92.144.in-addr.arpa: SERVFAIL
Mike Schmidt, our system administrator, told me that we have been
seeing DNS problems for your domain (aos.wisc.edu) for some time
now (approx. 3 weeks). Can you check this out?
> [ldm@f5 ~]$ ldmping idd.unidata.ucar.edu
> Apr 25 18:59:37 INFO: State Elapsed Port Remote_Host
> rpc_stat
> Apr 25 18:59:37 INFO: Resolving idd.unidata.ucar.edu to 128.117.140.3 took
> 0.003316 seconds
> Apr 25 18:59:47 ERROR: H_CLNTED 9.998604 388 idd.unidata.ucar.edu
> select: RPC: Timed out
>
> [ldm@f5 ~]$ ldmping papagayo.unl.edu
> Apr 25 19:00:05 INFO: State Elapsed Port Remote_Host
> rpc_stat
> Apr 25 19:00:05 INFO: Resolving papagayo.unl.edu to 129.93.52.150 took
> 0.117162 seconds
> Apr 25 19:00:15 ERROR: H_CLNTED 10.006840 388 papagayo.unl.edu select:
> RPC: Timed out
What is happening here is that the toplevel server process (rpc.ldmd) is off
trying
to do get the information for reverse lookup from a DNS server. While it is
waiting,
it is unavailable to respond to things like 'ldmping' and new connection
requests
(which get queued).
> The messages I was getting in my ldmd.log were:
>
> Apr 25 12:16:40 f5 idd.unidata.ucar.edu[5277] ERROR: Terminating due to LDM
> failure; nullproc_6 failure to idd.unidata.ucar.edu; RPC: Unable to receive;
> errno = Connection reset by peer
> Any ideas?
Yes, DNS does not appear to be working/consistent for aos.wisc.edu.
> Is there another NIMAGE feed I should be using for a backup
> other than idd.unidata.ucar.edu?
unidata2.ssec.wisc.edu
This might be a better machine for you to feed from anyway considering
that it is in the same building as you :-)
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: QZH-192791
Department: Support IDD
Priority: Normal
Status: Closed
>From address@hidden Wed Apr 26 09:14:28 2006
>Pete,
>I have not done anything at this end recently. When did this problem
>start? Are you getting any other data from us?
>Clint
>From address@hidden Wed Apr 26 09:31:30 2006
>Clint,
>We were having DNS issues, that was why we couldn't get data from you.
>I have a work-around going now until I can get the root problem solved.
>Data is flowing again from both you and Unidata.
>Thanks,
>Pete