Re: FW: Help! Cistron major failure in production! (fwd)

At 12:07 AM 26/07/01 +1200, Don Stokes wrote:

Matt Camp wrote:

...

After much playing with ktrace and kdump, found what it was barfing on.

The 192.168.0.33 and 192.168.0.34 addresses for the telecom DSL radius proxies... which weren't in /etc/hosts.

Adding them fixed it.

Now, the big question is, Why has this worked fine for 6 months, and only decided to crap out today?

I'd guess that it was being rather dumb about trying to look up reverse map entries for these in the DNS. 168.192.in-addr.arpa is delegated to blackhole.ep.net and blackhole.isi.edu, of which the ep.net name servers don't seem to be responding at the moment.

Strange, I don't see the same problem here, although I'm running 1.6.4, or it could be a difference in our DNS server setup. It's normal for radiusd to reverse look-up the NAS ip address since its possible to specify NAS's by hostname in raddb/clients, and if the DNS lookups are timing out very slowly it would definately cause problems...The /etc/hosts entry is probably a good idea....(/me goes and does it now to be sure :) And to Matt: If you're doing automated updates to the users file, etc, and propogating them to redundant servers without some good verification there are no mistakes in those files, I'd suggest you update to 1.6.4 so you can use the -C option to automatically check the new config files before applying them so your servers dont all go splat at once because of some silly little error in one of those files :) (It happens....) Regards, Simon --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog