I am runnning 2.1.6 on Redhat Linux (Red Hat Enterprise Linux Server release 5.3 (Tikanga)). This server relays all records to an identical server radius-b and radius-c Similarly radius-b relays its records back to radius-a (except those from radius-a) radius-c is just for testing. All relaying appears to be working correctly. These server currently receiving accounting records only. radius-a seems to be getting the bulk of the radius records. Normally, it has a single process. Last night it spawned a bunch of children that seem to be loitering... radius-b and radius-c don't have more than a single radiusd process. Any idea what is going on? Why all the children? Do I need to be concerned? Is this normal?
From the detail log, is seems that the message rate increase to about 2000-2400/minute at that time for about 3 minutes, then dropped to <1000/min. [root@radius-a radius]# ps -aef | grep radiusd radiusd 5426 21400 0 03:32 ? 00:00:00 /usr/local/sbin/radiusd radiusd 5738 21400 0 03:29 ? 00:00:00 /usr/local/sbin/radiusd radiusd 8239 21400 0 03:32 ? 00:00:00 /usr/local/sbin/radiusd radiusd 8240 21400 0 03:32 ? 00:00:00 /usr/local/sbin/radiusd radiusd 8241 21400 0 03:32 ? 00:00:00 /usr/local/sbin/radiusd radiusd 8242 21400 0 03:32 ? 00:00:00 /usr/local/sbin/radiusd radiusd 8243 21400 0 03:32 ? 00:00:00 /usr/local/sbin/radiusd radiusd 8244 21400 0 03:32 ? 00:00:00 /usr/local/sbin/radiusd radiusd 9029 21400 0 03:32 ? 00:00:00 /usr/local/sbin/radiusd radiusd 9104 21400 0 03:29 ? 00:00:00 /usr/local/sbin/radiusd radiusd 14154 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 14426 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 15039 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 15040 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 16082 21400 0 03:36 ? 00:00:00 /usr/local/sbin/radiusd radiusd 17295 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd root 19242 20229 0 11:42 pts/0 00:00:00 grep radiusd radiusd 19974 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 20670 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 20673 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 20674 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 20675 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 20679 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 20680 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 21207 21400 0 03:31 ? 00:00:00 /usr/local/sbin/radiusd radiusd 21208 21400 0 03:31 ? 00:00:00 /usr/local/sbin/radiusd radiusd 21209 21400 0 03:31 ? 00:00:00 /usr/local/sbin/radiusd radiusd 21300 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 21301 21400 0 03:33 ? 00:00:00 /usr/local/sbin/radiusd radiusd 21400 1 0 Oct07 ? 00:02:40 /usr/local/sbin/radiusd radiusd 26543 21400 0 03:34 ? 00:00:00 /usr/local/sbin/radiusd radiusd 26683 21400 0 03:31 ? 00:00:00 /usr/local/sbin/radiusd radiusd 28411 21400 0 03:34 ? 00:00:00 /usr/local/sbin/radiusd radiusd 29065 21400 0 03:31 ? 00:00:00 /usr/local/sbin/radiusd radiusd 30648 21400 0 03:34 ? 00:00:00 /usr/local/sbin/radiusd radiusd 30649 21400 0 03:34 ? 00:00:00 /usr/local/sbin/radiusd radiusd 30893 21400 0 03:31 ? 00:00:00 /usr/local/sbin/radiusd
Thanks, -craig __________ Information from ESET Smart Security, version of virus signature database 4490 (20091008) __________ The message was checked by ESET Smart Security. http://www.eset.com