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

20030701: IP Number Changes at pscwx

>From: Jim Koermer <address@hidden>
>Organization: Plymouth State
>Keywords: 200307012322.h61NMFLd001850 IDD

Hi Jim,

>This afternoon, our ITS folks moved all of our computers over to their
>own subnet. This is in anticipation of moving them into our new building
>in August. Since the change has taken place the new IP configuration
>seems to have propogated through the DNS system to UIUC and I am getting
>my WMO and MCIDAS feeds satisfactorily, but I don't seem to be getting
>data from atm.geo.nsf.gov. I get the following errors in my ldmd. log:
>
>Jul 01 23:13:27 pscwx atm[13826]: Desired product class:
>20030701221327.633 TS_ENDT {{FNEXRAD,  "^(rad/|pnga2area)"}} 
>Jul 01 23:13:27 pscwx atm[13826]: ERROR: requester6.c:426;
>ldm_clnt.c:277: nullproc_6 failure to atm.geo.nsf.gov; ldm_clnt.c:141:
>RPC: Unable to receive; errno = Connection reset by peer 
>Jul 01 23:13:57 pscwx atm[13826]: Desired product class:
>20030701221327.633 TS_ENDT {{FNEXRAD,  "^(rad/|pnga2area)"}} 
>Jul 01 23:13:57 pscwx atm[13826]: ERROR: requester6.c:426;
>ldm_clnt.c:277: nullproc_6 failure to atm.geo.nsf.gov; ldm_clnt.c:141:
>RPC: Unable to receive; errno = Connection reset by peer
>
>I'm not sure if Tom set this up on the IP number on atm rather than
>address or if the DNS has not updated, but the DNS change took place
>around 2100UTC.  

The allows on atm were setup by name, not IP.  The failure you were seeing
was most likely due to atm's running of a caching name server.  I just
checked the LDM logs on atm and see that the denials stopped at 04:20:

Jul 02 04:02:20 atm.geo.nsf.gov pscwx(feed)[21635]: topo:  pscwx.plymouth.edu 
FNEXRAD

I guess it took that long for atm's DNS to recognize the new name/IP
association.

>This machine is pscwx.plymouth.edu (now 158.136.64.59). Formerly, it was
>158.136.73.192.

Things seem to be working this morning.  Please let us know if you see
anything else amiss.

Cheers,

Tom

>From address@hidden Thu Jul  3 11:32:18 2003

Tom,

Thanks. After ITS crashed our network yesterday moning in trying to fix
a networked printer problem, everything finally came up and became
stable yesterday afternoon. Thanks for checking.

Jim