On Thu, Mar 25, 2004 at 03:43:36PM +0200, Richard Mayhew wrote: > Hi > > Thanks for the reply. > > The basic setup is as follows. > > We have incoming SMTP servers running Exim 4.30 with the latest ExiScan > patch. Mail is then palmed off to the spamd run on another server. Mail > is then scanned and a report is supplied back to the Exim MTA. The only > monitoring I am doing is a ps check counting the number of spamd procs > that are running, if there is 0 = problem or >251 = problem. I don't > think that is the prob seeing that when I did used to check the port, it > would crash with an error such as this. The spamd server(s) is also > behind a firewall and the only connection made to it is from the > incoming smtp servers.
I think I'd trace the port anyway to see if that was a cause. > Feb 25 17:30:21 01-spam spamd[24273]: Use of uninitialized value in > subroutine entry at > /usr/lib/perl5/5.8.1/i386-linux-thread-multi/Socket.pm > line 370. > I can send more of the strace if you would like as I have about 11GB of > it :) I can aslo include debug info for the spamd process. I'm still on 5.6.1 ... and I don't allow network connections, so I haven't seen what the problem actually looks like, sorry. > I did review > the debug output from the spamd proc when it died and it looks likes > like it would normally complete a message, just the spamd dies so it > never spawns any more probs... Ill keep looking. Are you running it under daemontools ? That ought to restart it when it dies, so the outage should be short. > This particularly happens when I enable health monitoring from a Radware > Load Balancer Switch. What can be done about spamd dying when a simple > nmap or telnet to port 783 takes place. I know there's a bug open on it, but I'm not sure what its status is. Nick
