Re: (RADIATOR) Stop Responding

2000-09-26 Thread Ron Hensley

Hugh,

Think i keyed onto the problem already, so im goign to hold off.
The one change that has been made was to start limited simultaneous
usage, with DBM and with BayFinger as the NasTYPE.

I believe the fingers were backing up, or slow to respond and were the
culprit.

After switching to Bay, (snmp version), its run consitantly overnight 
and thismorning on the problem server.

The one other possibilty is the 10bT link between the 2 radius servers,
sharinf an NFS link to the SessionDatabase file, perhaps a file locking
problem. The computer having the problems is the one with the actual local
file however, so i wouldnt think its nfs access time problems, as that
would show on the other serer that actually has to write to the file over
the network.

If it continues to behave strangely ill send over the configs requested.

Thanks much.

--
Ron Hensley  ([EMAIL PROTECTED]) CCNA #10082337
Network Administrator - ICNet Internet Services
--

On Tue, 26 Sep 2000, Hugh Irvine wrote:

 
 Hello Ron -
 
 On Tue, 26 Sep 2000, Ron Hensley wrote:
  Ive had a strange occurance today on one of my radius servers.
  It just stops responding though its still running after being up no more
  then
  5 minutes. Stopped/Started many times, a few times with trace level 4 for
  heavy debug info.
  Nothing... just stops apparantly in the middle of logging someone in.
  
  Its been working fine for the week ive been using it.
  
  At one point i noticed my server getting slow as well, and TOP showed the
  radiusd taking
  up 25% CPU resources.
  
  Any hints on how to track down what could be making it hang?
  
 
 Could you please send me what version of Perl you are using, what version of
 Radiator, and what hardware and software platform you are running on. I will
 also need to see a copy of your configuration file (no secrets), together with
 the trace 4 debug.
 
 thanks
 
 Hugh
 
 
 -- 
 Radiator: the most portable, flexible and configurable RADIUS server 
 anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
 Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
 Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
 
 


===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.



RE: (RADIATOR) Stop Responding

2000-09-26 Thread Chris Given

Have you considered a diffrent database? We run 5 radius servers off one
database with no issues.

-Original Message-
From: Ron Hensley [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 26, 2000 7:38 AM
To: Hugh Irvine
Cc: [EMAIL PROTECTED]
Subject: Re: (RADIATOR) Stop Responding


Hugh,

Think i keyed onto the problem already, so im goign to hold off.
The one change that has been made was to start limited simultaneous
usage, with DBM and with BayFinger as the NasTYPE.

I believe the fingers were backing up, or slow to respond and were the
culprit.

After switching to Bay, (snmp version), its run consitantly overnight 
and thismorning on the problem server.

The one other possibilty is the 10bT link between the 2 radius servers,
sharinf an NFS link to the SessionDatabase file, perhaps a file locking
problem. The computer having the problems is the one with the actual local
file however, so i wouldnt think its nfs access time problems, as that
would show on the other serer that actually has to write to the file over
the network.

If it continues to behave strangely ill send over the configs requested.

Thanks much.

--
Ron Hensley  ([EMAIL PROTECTED]) CCNA #10082337
Network Administrator - ICNet Internet Services
--

On Tue, 26 Sep 2000, Hugh Irvine wrote:

 
 Hello Ron -
 
 On Tue, 26 Sep 2000, Ron Hensley wrote:
  Ive had a strange occurance today on one of my radius servers.
  It just stops responding though its still running after being up no more
  then
  5 minutes. Stopped/Started many times, a few times with trace level 4
for
  heavy debug info.
  Nothing... just stops apparantly in the middle of logging someone in.
  
  Its been working fine for the week ive been using it.
  
  At one point i noticed my server getting slow as well, and TOP showed
the
  radiusd taking
  up 25% CPU resources.
  
  Any hints on how to track down what could be making it hang?
  
 
 Could you please send me what version of Perl you are using, what version
of
 Radiator, and what hardware and software platform you are running on. I
will
 also need to see a copy of your configuration file (no secrets), together
with
 the trace 4 debug.
 
 thanks
 
 Hugh
 
 
 -- 
 Radiator: the most portable, flexible and configurable RADIUS server 
 anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
 Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
 Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
 
 


===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.



Re: (RADIATOR) Stop Responding

2000-09-26 Thread Hugh Irvine


Hello Ron -

On Wed, 27 Sep 2000, Ron Hensley wrote:
 Hugh,
 
 Think i keyed onto the problem already, so im goign to hold off.
 The one change that has been made was to start limited simultaneous
 usage, with DBM and with BayFinger as the NasTYPE.
 
 I believe the fingers were backing up, or slow to respond and were the
 culprit.
 
 After switching to Bay, (snmp version), its run consitantly overnight 
 and thismorning on the problem server.
 
 The one other possibilty is the 10bT link between the 2 radius servers,
 sharinf an NFS link to the SessionDatabase file, perhaps a file locking
 problem. The computer having the problems is the one with the actual local
 file however, so i wouldnt think its nfs access time problems, as that
 would show on the other serer that actually has to write to the file over
 the network.
 

I would be very suspicious of running a shared DBM session database over NFS.
Radiator does not lock the DBM file, so problems are almost guaranteed. I would
strongly suggest that you use an SQL session database instead.

regards

Hugh

-- 
Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.



===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.



(RADIATOR) Stop Responding

2000-09-25 Thread Ron Hensley

Ive had a strange occurance today on one of my radius servers.
It just stops responding though its still running after being up no more
then
5 minutes. Stopped/Started many times, a few times with trace level 4 for
heavy debug info.
Nothing... just stops apparantly in the middle of logging someone in.

Its been working fine for the week ive been using it.

At one point i noticed my server getting slow as well, and TOP showed the
radiusd taking
up 25% CPU resources.

Any hints on how to track down what could be making it hang?


===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.