We have a webserver running Apache 1.3.36 on Solaris 9. If I try to add
more than 81 VHOSTS all of the vhosts start throwing errors:

[Wed Jun 21 12:29:31 2006] [crit] [client <REMOVED>] (24)Too many open
files: /path/to/www/content/.htaccess pcfg_openfile: unable to check
htaccess file, ensure it is readable

I've set rlim_rd_cur to 8192 in /etc/system (and rebooted), and
re-compiled apache with EXTRA_CFLAGS=-DHIGH_SLACK_LINE=256 all to no
avail. The data directories, configuration files, and log files are all
stored on an NFS filesystem (although, I'm pretty sure NFS isn't the
culprit here.)

Any our suggestions would be greatly appreciated.

Looks like you've raised the file descriptor soft limit, but not the
hard limit - try setting:

rlim_fd_max = 8192
rlim_fd_cur = 1024

in /etc/system.


Charles Plater wrote:
> We have a webserver running Apache 1.3.36 on Solaris 9. If I try to add
> more than 81 VHOSTS all of the vhosts start throwing errors:
>
> [Wed Jun 21 12:29:31 2006] [crit] [client <REMOVED>] (24)Too many open
> files: /path/to/www/content/.htaccess pcfg_openfile: unable to check
> htaccess file, ensure it is readable
>
> I've set rlim_rd_cur to 8192 in /etc/system (and rebooted), and
> re-compiled apache with EXTRA_CFLAGS=-DHIGH_SLACK_LINE=256 all to no
> avail. The data directories, configuration files, and log files are all
> stored on an NFS filesystem (although, I'm pretty sure NFS isn't the
> culprit here.)
>
> Any our suggestions would be greatly appreciated.

"Charles Plater" <cplater+usenet AT gmail DOT com> wrote:
> We have a webserver running Apache 1.3.36 on Solaris 9. If I try to add
> more than 81 VHOSTS all of the vhosts start throwing errors:
>
> [Wed Jun 21 12:29:31 2006] [crit] [client <REMOVED>] (24)Too many open
> files: /path/to/www/content/.htaccess pcfg_openfile: unable to check
> htaccess file, ensure it is readable
>
> I've set rlim_rd_cur to 8192 in /etc/system (and rebooted), and
> re-compiled apache with EXTRA_CFLAGS=-DHIGH_SLACK_LINE=256 all to no
> avail. The data directories, configuration files, and log files are all
> stored on an NFS filesystem (although, I'm pretty sure NFS isn't the
> culprit here.)

How many open file descriptors does your apache have
in your configuration when the problem occurs?
You might have to use a 64bit Apache.


Thomas

Hello,

It looks like we hit the same file descriptor ptoblem.I tried to
increase the number of allowed open fd though ulimit, but I got the
following error message:
"ksh: ulimit: exceeds allowable limit"

I checked /etc/system file and did not find
rlim_fd_max
rlim_fd_cur

Please advise on how I can increase # of allowed open file descriptors.

Is there a limit of number of threads (LWP) per process?


Thanks,
Alona

Phil Cordier wrote:
> Looks like you've raised the file descriptor soft limit, but not the
> hard limit - try setting:
>
> rlim_fd_max = 8192
> rlim_fd_cur = 1024
>
> in /etc/system.
>
>
> Charles Plater wrote:
> > We have a webserver running Apache 1.3.36 on Solaris 9. If I try to add
> > more than 81 VHOSTS all of the vhosts start throwing errors:
> >
> > [Wed Jun 21 12:29:31 2006] [crit] [client <REMOVED>] (24)Too many open
> > files: /path/to/www/content/.htaccess pcfg_openfile: unable to check
> > htaccess file, ensure it is readable
> >
> > I've set rlim_rd_cur to 8192 in /etc/system (and rebooted), and
> > re-compiled apache with EXTRA_CFLAGS=-DHIGH_SLACK_LINE=256 all to no
> > avail. The data directories, configuration files, and log files are all
> > stored on an NFS filesystem (although, I'm pretty sure NFS isn't the
> > culprit here.)
> >
> > Any our suggestions would be greatly appreciated.

On 2006-06-22 14:32:24 -0400, "Thomas Dehn" <thomas-usenet@arcor.de> said:

>
> "Charles Plater" <cplater+usenet AT gmail DOT com> wrote:
>> We have a webserver running Apache 1.3.36 on Solaris 9. If I try to add
>> more than 81 VHOSTS all of the vhosts start throwing errors:
>>
>> [Wed Jun 21 12:29:31 2006] [crit] [client <REMOVED>] (24)Too many open
>> files: /path/to/www/content/.htaccess pcfg_openfile: unable to check
>> htaccess file, ensure it is readable
>>
>> I've set rlim_fd_cur to 8192 in /etc/system (and rebooted), and
>> re-compiled apache with EXTRA_CFLAGS=-DHIGH_SLACK_LINE=256 all to no
>> avail. The data directories, configuration files, and log files are all
>> stored on an NFS filesystem (although, I'm pretty sure NFS isn't the
>> culprit here.)
>
> How many open file descriptors does your apache have
> in your configuration when the problem occurs? You might have to use a
> 64bit Apache.

According to LSOF, apache has 297 open files when running w/ no
problems, and 300 open files when it is having problems.

For the record, I've set the hard file descriptor limit (rlim_fd_max),
and that didn't make a difference.

On 2006-06-22 14:32:24 -0400, "Thomas Dehn" <thomas-usenet@arcor.de> said:

>
> "Charles Plater" <cplater+usenet AT gmail DOT com> wrote:
>> We have a webserver running Apache 1.3.36 on Solaris 9. If I try to add
>> more than 81 VHOSTS all of the vhosts start throwing errors:
>>
>> [Wed Jun 21 12:29:31 2006] [crit] [client <REMOVED>] (24)Too many open
>> files: /path/to/www/content/.htaccess pcfg_openfile: unable to check
>> htaccess file, ensure it is readable
>>
>> I've set rlim_fd_cur to 8192 in /etc/system (and rebooted), and
>> re-compiled apache with EXTRA_CFLAGS=-DHIGH_SLACK_LINE=256 all to no
>> avail. The data directories, configuration files, and log files are all
>> stored on an NFS filesystem (although, I'm pretty sure NFS isn't the
>> culprit here.)
>
> How many open file descriptors does your apache have
> in your configuration when the problem occurs? You might have to use a
> 64bit Apache.

According to LSOF, apache has 297 open files when running w/ no
problems, and 300 open files when it is having problems.

For the record, I've set the hard file descriptor limit (rlim_fd_max),
and that didn't make a difference.

"Charles Plater" <cplater+usenet AT gmail DOT com> wrote:
> On 2006-06-22 14:32:24 -0400, "Thomas Dehn" <thomas-usenet@arcor.de> said:
>
> >
> > "Charles Plater" <cplater+usenet AT gmail DOT com> wrote:
> >> We have a webserver running Apache 1.3.36 on Solaris 9. If I try to add
> >> more than 81 VHOSTS all of the vhosts start throwing errors:
> >>
> >> [Wed Jun 21 12:29:31 2006] [crit] [client <REMOVED>] (24)Too many open
> >> files: /path/to/www/content/.htaccess pcfg_openfile: unable to check
> >> htaccess file, ensure it is readable
> >>
> >> I've set rlim_fd_cur to 8192 in /etc/system (and rebooted), and
> >> re-compiled apache with EXTRA_CFLAGS=-DHIGH_SLACK_LINE=256 all to no
> >> avail. The data directories, configuration files, and log files are all
> >> stored on an NFS filesystem (although, I'm pretty sure NFS isn't the
> >> culprit here.)
> >
> > How many open file descriptors does your apache have
> > in your configuration when the problem occurs? You might have to use a
> > 64bit Apache.
>
> According to LSOF, apache has 297 open files when running w/ no
> problems, and 300 open files when it is having problems.

Then the problem might be that 32-bit Apache uses fopen(),
which is limited to 255 fds in Solaris because of
binary compatibility reasons.

The most popular such fopen() problem is in mod_ssl.
Here is the Apache 2 version:

http://issues.apache.org/bugzilla/show_bug.cgi?id=14219

Reading the last two comments probably is sufficient
to understand whats going on.


Thomas