(RADIATOR) Radiator crashes without trace

Dave Kitabjian dave at netcarrier.com
Wed Jul 20 11:09:54 CDT 2005


I think you said you're running at debug level 3? Try 4.

We had a situation a few years ago where garbled usernames were coming in and messing things up, causing processes to die (in our case it was the LDAP process that died, but it could just have conceivably been radiusd). And since the NAS didn't get a reply from the Radiator server, it "failed over" to the other Radiator server and "killed" that one, too.

So the fact that both are dying suggests to me that you probably have them in a failover scenario and there is some type of rogue RADIUS request that's coming in and taking them both out, one at a time. Trace 4 should help track down the rogue request and its contents...

D


> -----Original Message-----
> From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] On
> Behalf Of Martin Wallner
> Sent: Wednesday, July 20, 2005 11:23 AM
> To: Dave Kitabjian; radiator at open.com.au
> Subject: RE: (RADIATOR) Radiator crashes without trace
> 
> 
> 
> Thanks for your fast answer.
> 
> > So when you say "crashes" and "stops", is the perl process
> > that's running radiusd still in the process list or is it gone?
> 
> No, radiusd is gone with the perl process.
> 
> >
> > Does your system log show anything (eg, /var/log/messages)?
> 
> I searched every possible logfile, no avail... :-/
> 
> >
> > Are you low on disk or RAM?
> 
> Both Systems have 1GB RAM, and are dedicated RADIUS-Server..
> 
> >
> > Does the box get too hot?
> 
> Climatized, and in 2 different locations.
> 
> >
> > Do you have any patches installed?
> 
> WhiteBox 3 with all upgrades. Perl is on 5.8.0...
> 
> 
> >
> > You might want to try swapping out the RAM from the
> > problematic box with the box that's working fine and see what
> > happens...
> 
> That is the problem: the error is on _both_ boxes (they are identical
> DL360 with the same hardware stuffed in...). The radiator-installation I
> talked about which is NOT crashing has nothing to do with these two
> boxes... And since _everything else_ running on the questionable boxes is
> running perfectly, I'm a bit stuck...
> 
> There is the possibility that I'm running the radiusd under the wrapper,
> but that would be fighting the symptom, and not the problem...
> 
> Yes, that I forgot: I'm running Radiator 3.11...
> 
> regards
> Martin Wallner (=mw=)
> 
> -----
> Eunet Telekom GmbH			e-mail 'martin.wallner at eunet.co.at
> vorm. Nextra Österreich			e-mail 'martin.wallner at nextranet.at'
> vorm. ViP EDV-Dienstleistungs GesmbH	e-mail 'hostmaster at vip.at'
> vorm. Gramtel Austria GmbH.		e-mail 'hostmaster at gramtel.at'
> Systems					RIPE:     WM355-RIPE
> Nussdorfer Lände 23			NicAT:    WM503823-NICAT
> 1190 Wien, Vienna, Austria		Tel. +43 (0) 59 1 59 - 1354
> 
> --
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.


--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.


More information about the radiator mailing list