Radius server Crashing

[Chris Bell]

Hello All -

A newbie I am so please be patient with me.  I am a Junior Network Admin who
has unexpectedly inherited a Senior Admin position.  I also inherited a
problem with our Radius servers.

We are running freeradius-1.1.3-1.2.el5.i386.  Our Network backup daemon
(Rancid) logs in to each network device on the hour to check for changes,
backup the configs, etc... 

The radius server crashes after a period of time.  I think the Rancid
service is crashing it.  When I log into the box running the radius server,
and check the running processes associated with radius, I get:

radiusd  21873     1  0 05:01 ?        00:00:05 /usr/sbin/radiusd -y
radiusd  22006 21873  0 05:41 ?        00:00:00 [netstat] <defunct>
radiusd  22115 21873  0 06:40 ?        00:00:00 [netstat] <defunct>
radiusd  22417 21873  0 07:40 ?        00:00:00 [netstat] <defunct>
radiusd  22612 21873  0 08:41 ?        00:00:00 [netstat] <defunct>
radiusd  22937 21873  0 10:41 ?        00:00:00 [netstat] <defunct>
root     23300 23197  0 12:14 pts/0    00:00:00 grep rad

The radius server(s) are running on Centos 5 if that makes a difference.
After these "defunct" processes build up to about 10 or 12... Radius no
work. Boss get mad.   

I've searched the net and found no answers... If the answer to my problem is
painfully obvious, please remember that I started this email with a
declaration of newbness.

Centos 5

Chris Bell
Systems




CONFIDENTIAL NOTICE: This email including any attachments, contains 
confidential information belonging to the sender. It may also be 
privileged or otherwise protected by work product immunity or other 
legal rules. This information is intended only for the use of the 
individual or entity named above.  If you are not the intended 
recipient, you are hereby notified that any disclosure, copying, 
distribution or the taking of any action in reliance on the contents 
of this emailed information is strictly prohibited.  If you have 
received this email in error, please immediately notify us by 
reply email of the error and then delete this email immediately.