You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by User for SpamAssassin Mail List <sp...@pcez.com> on 2005/12/01 21:54:17 UTC
spamd: fatal: setuid
Hello,
I'm getting these errors on some user when the spamd program tries to
setuid to the users ID. Here is some of the log file showing the error:
Dec 1 09:24:38 mail spamd[1897]: connection from localhost [127.0.0.1] at port 57112
Dec 1 09:24:38 mail spamd[1897]: fatal: setuid to chuck failed
Dec 1 09:24:38 mail spamd[1897]: error: Died at /usr/sbin/spamd line 1399, <GEN505> line 2._ , continuing
Dec 1 09:24:39 mail spamd[2696]: connection from localhost [127.0.0.1] at port 57115
Dec 1 09:24:39 mail spamd[2696]: fatal: setuid to stingrea failed
Dec 1 09:24:39 mail spamd[2696]: error: Died at /usr/sbin/spamd line 1399, <GEN513> line 2._ , continuing
We are running spamassassin ver - Debian 3.0.3-2 on this system.
Any idea on what to look for to solve this problem?
Thanks,
Ken Rea
Re: spamd: fatal: setuid
Posted by User for SpamAssassin Mail List <sp...@pcez.com>.
As a follow up I did find this on a Debian web site:
echo "65536" > /proc/sys/fs/file-max # for 2.2 and 2.4 kernel
echo "131072" > /proc/sys/fs/inode-max # for 2.2 kernel only
So it looks like you don't have to worry about inodes on a 2.4 kernel.
Ken Rea
On Thu, 1 Dec 2005, User for SpamAssassin Mail List wrote:
>
> Matt,
>
>
> It's a Debian Stable system, and I did bump up that file and also put in a
> script on boot up to raise that number. Some of the ideas I found (after
> doing a google search) suggested changing the inode-max as well but I
> could not find that in the proc file system.
>
> We will see if that solves the problem.
>
> Thanks,
>
> Ken Rea
>
>
> On Thu, 1 Dec 2005, Matt Kettler wrote:
>
> > User for SpamAssassin Mail List wrote:
> > >
> > > I think this is where the problems is coming in. Looking through the logs
> > > I found this:
> > >
> > > Dec 1 09:13:20 mail spamd[31417]: DCC -> check failed: cannot fork: Too many open files in system
> > > at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 1019, <GEN2184> line 101.
> > >
> > > Dec 1 09:13:20 mail spamd[31417]: clean message (-2.2/6.0) for jbrugger:2917 in 0.8 seconds,
> > > 4001 bytes.
> > >
> > >
> > >
> > > So how does one fix the problem of to many open files on a system?
> >
> > What kind of OS is it?
> >
> > On most linux kernels you can adjust the system-wide file handle limit using
> > /proc/sys/fs/file-max.
> >
> >
> > Stealing an example from http://www.linuxforum.com/linux-filesystem/proc.html
> >
> > # cat /proc/sys/fs/file-max
> > 4096
> >
> > # echo 8192 > /proc/sys/fs/file-max
> > # cat /proc/sys/fs/file-max
> > 8192
> >
>
Re: spamd: fatal: setuid
Posted by User for SpamAssassin Mail List <sp...@pcez.com>.
Matt,
It's a Debian Stable system, and I did bump up that file and also put in a
script on boot up to raise that number. Some of the ideas I found (after
doing a google search) suggested changing the inode-max as well but I
could not find that in the proc file system.
We will see if that solves the problem.
Thanks,
Ken Rea
On Thu, 1 Dec 2005, Matt Kettler wrote:
> User for SpamAssassin Mail List wrote:
> >
> > I think this is where the problems is coming in. Looking through the logs
> > I found this:
> >
> > Dec 1 09:13:20 mail spamd[31417]: DCC -> check failed: cannot fork: Too many open files in system
> > at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 1019, <GEN2184> line 101.
> >
> > Dec 1 09:13:20 mail spamd[31417]: clean message (-2.2/6.0) for jbrugger:2917 in 0.8 seconds,
> > 4001 bytes.
> >
> >
> >
> > So how does one fix the problem of to many open files on a system?
>
> What kind of OS is it?
>
> On most linux kernels you can adjust the system-wide file handle limit using
> /proc/sys/fs/file-max.
>
>
> Stealing an example from http://www.linuxforum.com/linux-filesystem/proc.html
>
> # cat /proc/sys/fs/file-max
> 4096
>
> # echo 8192 > /proc/sys/fs/file-max
> # cat /proc/sys/fs/file-max
> 8192
>
Re: spamd: fatal: setuid
Posted by Matt Kettler <mk...@evi-inc.com>.
User for SpamAssassin Mail List wrote:
>
> I think this is where the problems is coming in. Looking through the logs
> I found this:
>
> Dec 1 09:13:20 mail spamd[31417]: DCC -> check failed: cannot fork: Too many open files in system
> at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 1019, <GEN2184> line 101.
>
> Dec 1 09:13:20 mail spamd[31417]: clean message (-2.2/6.0) for jbrugger:2917 in 0.8 seconds,
> 4001 bytes.
>
>
>
> So how does one fix the problem of to many open files on a system?
What kind of OS is it?
On most linux kernels you can adjust the system-wide file handle limit using
/proc/sys/fs/file-max.
Stealing an example from http://www.linuxforum.com/linux-filesystem/proc.html
# cat /proc/sys/fs/file-max
4096
# echo 8192 > /proc/sys/fs/file-max
# cat /proc/sys/fs/file-max
8192
Re: spamd: fatal: setuid
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
On 01/12/2005 5:30 PM, User for SpamAssassin Mail List wrote:
>
> I think this is where the problems is coming in. Looking through the logs
> I found this:
>
> Dec 1 09:13:20 mail spamd[31417]: DCC -> check failed: cannot fork: Too many open files in system
> at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 1019, <GEN2184> line 101.
>
> Dec 1 09:13:20 mail spamd[31417]: clean message (-2.2/6.0) for jbrugger:2917 in 0.8 seconds,
> 4001 bytes.
>
> So how does one fix the problem of to many open files on a system?
FWIW, this is a result of SA 3.0 with net tests enabled using a socket
for each DNS request. It's not an issue with SA 3.1 where all DNS
requests are done with a single socket (well, possibly a couple).
Daryl
Re: spamd: fatal: setuid
Posted by User for SpamAssassin Mail List <sp...@pcez.com>.
I think this is where the problems is coming in. Looking through the logs
I found this:
Dec 1 09:13:20 mail spamd[31417]: DCC -> check failed: cannot fork: Too many open files in system
at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 1019, <GEN2184> line 101.
Dec 1 09:13:20 mail spamd[31417]: clean message (-2.2/6.0) for jbrugger:2917 in 0.8 seconds,
4001 bytes.
So how does one fix the problem of to many open files on a system?
Thanks,
Ken Rea
On Thu, 1 Dec 2005, User for SpamAssassin Mail List wrote:
>
>
>
> Yes the users do exist and usually it works fine.
>
> Ken
>
>
>
> On Thu, 1 Dec 2005, Theo Van Dinter wrote:
>
> > On Thu, Dec 01, 2005 at 12:54:17PM -0800, User for SpamAssassin Mail List wrote:
> > > I'm getting these errors on some user when the spamd program tries to
> > > setuid to the users ID. Here is some of the log file showing the error:
> >
> > Do those users actually exist? Does your perl support setuid?
> >
> > > Dec 1 09:24:38 mail spamd[1897]: fatal: setuid to chuck failed
> > > Dec 1 09:24:39 mail spamd[2696]: fatal: setuid to stingrea failed
> >
> > --
> > Randomly Generated Tagline:
> > "Imagination is more important than knowledge." - Albert Einstein
> >
>
Re: spamd: fatal: setuid
Posted by User for SpamAssassin Mail List <sp...@pcez.com>.
Yes the users do exist and usually it works fine.
Ken
On Thu, 1 Dec 2005, Theo Van Dinter wrote:
> On Thu, Dec 01, 2005 at 12:54:17PM -0800, User for SpamAssassin Mail List wrote:
> > I'm getting these errors on some user when the spamd program tries to
> > setuid to the users ID. Here is some of the log file showing the error:
>
> Do those users actually exist? Does your perl support setuid?
>
> > Dec 1 09:24:38 mail spamd[1897]: fatal: setuid to chuck failed
> > Dec 1 09:24:39 mail spamd[2696]: fatal: setuid to stingrea failed
>
> --
> Randomly Generated Tagline:
> "Imagination is more important than knowledge." - Albert Einstein
>
Re: spamd: fatal: setuid
Posted by Theo Van Dinter <fe...@apache.org>.
On Thu, Dec 01, 2005 at 12:54:17PM -0800, User for SpamAssassin Mail List wrote:
> I'm getting these errors on some user when the spamd program tries to
> setuid to the users ID. Here is some of the log file showing the error:
Do those users actually exist? Does your perl support setuid?
> Dec 1 09:24:38 mail spamd[1897]: fatal: setuid to chuck failed
> Dec 1 09:24:39 mail spamd[2696]: fatal: setuid to stingrea failed
--
Randomly Generated Tagline:
"Imagination is more important than knowledge." - Albert Einstein