Kostas Zorbadelos wrote: > radiusd -X confirms that the configuration is correct, however I have > this problem behaviour in large scale. My initial suspitions go to the > proxying code to be honest, but I need to take a good look to grasp > it.
I would try running the production radius in debugging mode and send the output to a file that you can review for anomalies. If it is happening often enough and you don't want to run the primary radius in debug mode, you could do it on the secondary and force a failover for a short time and try to catch it. -- Dennis Skinner Systems Administrator BlueFrog Internet http://www.bluefrog.com - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
