Re: (RADIATOR) PMWHO killing radiator?

Wed, 31 May 2000 19:30:12 -0700 

Hi John,

I just read your Radiator email in the Radiator archive about PMWHO
killing radiator.  That exact thing happen to one of our Total Controls
and Radiator would not authenticate anyone.  I tried to restart radiusd
but it said:

# Could not bind authentication socket: Address already in use at
/usr/bin/radiusd line 351.

Well it seems that PMWHO was the culprit, so I stopped using it to
simultaneous-use check our TCs.  Did you find a solution to what NasType
to use instead of PMWHO?

http://www.thesite.com.au/~radiator/199912/msg00286.html

Your response is greatly appreciated!
Thanks,
Janet del Mundo
Title: Re: (RADIATOR) PMWHO killing radiator?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (RADIATOR) PMWHO killing radiator?


Hello John -

On Thu, 30 Dec 1999, [EMAIL PROTECTED] wrote:
> I have a problem where my radiator stops responding sometimes a 
> few times a day (at least every few days).  Luckily, I have a backup 
> radius and a paging program that calls me when this happens, but 
> it is still annoying.  When I attempt to start my radiator back up, I 
> run my shell script that kills any currently running copies and 
> starts a fresh one.  The fresh one comes up and indicates that it 
> could not bind to the port.  I then run:
> ps auwwx | grep telnet
> 
> and find the telnet session to my 3com modem bank that is 
> hanging around and kill that pid.  After that, radiator can get going 
> normally again.  I suspect that pmwho is checking the double 
> logins and happened to grab port 1645 to make that connection to 
> the modem bank.  Has anyone else had something like this?  I'm 
> going to take out all the "NasType" listings in the config file and 
> see if that helps.  I'd still like to fix it for good though.
> 

I think the problem is with the modem bank not answering the pmwho query which
causes Radiator to hang waiting for a response. Because the telnet process is
stuck, the radius sockets don't get cleaned up and hence your problem. You will
have to find a more reliable NasType method that doesn't get stuck.

hth

Hugh


-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody

===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to