MailScanner dying

[Craig Bates]

There is one important piece of evidence that I over looked in the maillog:
maillog:Dec  6 08:27:38 mx3 sendmail[26163]: File descriptors missing on 
startup: stdin, stdout, stderr; Bad file descriptor

This happens a couple of times per day, not every time something is processed.
Thanks,

Craig


On Friday 06 December 2002 08:33, you wrote:
> Without any more information about whether or not it is actually a
> MailScanner problem or not, there is not much I can do.
>
> Is anyone out there suffering the same problem?
>
> At 19:26 05/12/2002, you wrote:
> >It was set to around 1800, I increased it to 8192, but Mailscanner
> > processes are still dying off.  Only 2 of the 6 that started 9 hours ago
> > are running. Any other idea?  Is it possible that spam assassin, razor,
> > or the RBL checks are sometimes causing it to die, without logging
> > anything??
> >
> >Craig
> >
> >On Thursday 05 December 2002 10:43, you wrote:
> > > At 21:29 04/12/2002, you wrote:
> > > >I'm running 6 MailScanner processes, they seem to die off over a day
> > > > or so. After a few hours there may only be 4 processes running.  I'm
> > > > using f-prot, spam assassin, RAZOR and RBL checks.  There is nothing
> > > > in the logs indicating that anything has gone wrong.  I'm running
> > > > FreeBSD 4.7 and the latest version of mailscanner.  Any Ideas?
> > >
> > > Check how many filehandles you have available. I have a nasty feeling
> > > this figure is very low on BSD. Do
> > >          ulimit -a
> > > to see the figure (it will probably be labelled "open files"). If it is
> > > less than a few thousand, you should be able to raise it with
> > >          ulimit -n 4000
> > > Then re-run MailScanner and it should be happier.