Re: LDM failover to sunset

In a previous message to me, you wrote: 

 >Hi Pete,
 >
 >My usual LDM feed from across campus here at Purdue
 >is down so I am trying to failover to your sunset machine.
 >
 >ldmadmin gives me an error message that it cannot register
 >with sunset after a 60 second attempt.
 >
 >Is my machine 'shadow.agry.purdue.edu' still registered as
 >a failover on sunset?  In recent weeks 'shadow' has had more
 >trouble sustaining a failover feed to 'sunset' so I am
 >wondering if I need to find another failover?

Ken,

I do have an allow line for you

allow   DDPLUS|HRS|IDS|DIFAX    ^shadow.agry.purdue.edu$

Here's what it looks like from my end in my ldmd.log:

Jul 25 13:50:00 5Q:sunset shadow[3047640]: Connection from 
shadow.agry.purdue.edu
Jul 25 13:50:00 5Q:sunset shadow(feed)[3047640]: Starting Up: 
20020725124621.971 TS_ENDT {{DDPLUS,  ".*"},{IDS,  ".*"},{HDS,  ".*"}}
Jul 25 13:50:00 5Q:sunset shadow(feed)[3047640]: topo:  shadow.agry.purdue.edu 
WMO
Jul 25 13:50:00 3Q:sunset shadow(feed)[3047640]: SRUS55 KGJT 251246 /pRR3GJT: 
Unable to receive (4)
Jul 25 13:50:00 3Q:sunset shadow(feed)[3047640]: pq_sequence failed: I/O error 
(errno = 5)
Jul 25 13:50:00 5Q:sunset shadow(feed)[3047640]: Exiting
Jul 25 13:50:05 5Q:sunset rpc.ldmd[2768160]: child 3047640 exited with status 1


Jul 25 14:29:09 5Q:sunset shadow[3054120]: Connection from 
shadow.agry.purdue.edu
Jul 25 14:29:10 5Q:sunset shadow(feed)[3054120]: Starting Up: 
20020725132531.501 TS_ENDT {{DDPLUS,  ".*"},{IDS,  ".*"},{HDS,  ".*"}}
Jul 25 14:29:10 5Q:sunset shadow(feed)[3054120]: topo:  shadow.agry.purdue.edu 
WMO
Jul 25 14:29:10 3Q:sunset shadow(feed)[3054120]: SDUS40 PHFO 251310 /pRCMHKI: 
Unable to receive (4)
Jul 25 14:29:10 3Q:sunset shadow(feed)[3054120]: pq_sequence failed: I/O error 
(errno = 5)
Jul 25 14:29:10 5Q:sunset shadow(feed)[3054120]: Exiting
Jul 25 14:29:16 5Q:sunset rpc.ldmd[2768160]: child 3054120 exited with status 1

A traceroute looks like:

sunset 3% /usr/etc/traceroute shadow.agry.purdue.edu
traceroute to shadow.agry.purdue.edu (128.210.147.18), 30 hops max, 40 byte 
packets
 1  144.92.130.1 (144.92.130.1)  8 ms  4 ms  3 ms
 2  r-peer-at-1-1-0-21.net.wisc.edu (144.92.128.205)  2 ms (ttl=253!)  5 ms 
(ttl=253!)  4 ms (ttl=253!)
 3  144.92.201.62 (144.92.201.62)  7 ms (ttl=252!)  7 ms (ttl=252!)  8 ms 
(ttl=252!)
 4  mren-m10-lsd6509.startap.net (206.220.240.86)  7 ms  6 ms  25 ms
 5  chin-mren-ge.abilene.ucaid.edu (198.32.11.97)  8 ms  8 ms  7 ms
 6  ipls-chin.abilene.ucaid.edu (198.32.8.69)  27 ms  11 ms  10 ms
 7  192.12.206.250 (192.12.206.250)  20 ms (ttl=248!)  11 ms (ttl=248!)  11 ms 
(ttl=248!)
 8  cisco-tel-gp.tcom.purdue.edu (192.5.40.29)  14 ms  19 ms  14 ms
 9  cisco2-242.tcom.purdue.edu (128.210.242.7)  13 ms  14 ms  13 ms
10  shadow.agry.purdue.edu (128.210.147.18)  13 ms  15 ms  13 ms


so it looks clean.

Maybe try changing your request line to 'sunset.aos.wisc.edu'. I did
make a change to our dns on Monday that results in reverse
name lookups returning the aos.wisc.edu domain instead of
meteor.wisc.edu, in anticipation of eventually dropping the
meteor.wisc.edu all together, but I didn't think that would
impact data requests. I haven't heard anything adverse from
anyone else..

Pete


--
+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+
^ Pete Pokrandt                    V 1447  AOSS Bldg  1225 W Dayton St^
^ Systems Programmer               V Madison,         WI     53706    ^
^                                  V      address@hidden       ^
^ Dept of Atmos & Oceanic Sciences V (608) 262-3086 (Phone/voicemail) ^
^ University of Wisconsin-Madison  V       262-0166 (Fax)             ^
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+