Hi,
As far as I can see, the people on the list have provided you with a
lot of very useful suggestions on what could cause the problem. As I
said earlier (let me clarify) and to help you narrow things a little
bit - it's probably due to the RADIUS response timing out hence the
NAS complains the server is dead and later when it responds finally it
marks it as alive again. The reasons can be different depending on
your setup - slow network, database, custom module (like rlm_perl/
python etc) or as I suggested (from my personal experiences)
improperly configured concurrence settings of FR itself. See which
component of your setup is causing the slow responds (it can be the
backend, or messed up FR configuration) and fix it. Just for
completeness check your NASs manuals - most have these settings
configurable - response timeouts, retransmits, marking the server as
dead etc but playing with the NAS while possibly useful is probably
not the main issue in your setup - check what is slowing things down.
On 27.04.2009, at 15:41, a.l.m.bu...@lboro.ac.uk wrote:
Hi,
Same box.
and you do live accounting database insertions? This sounds
to me very much like the classic 'tables have now grown just too
big' - everything works fine then barfs one day. the
request isnt getting serviced in time therefore its marking
as dead..check your query times...remove wrong/unused indexes
or move to 'out of band' accounting inserts - very easy with 2.1.x
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
