grsecurity forums

Short: I suspect the grsecurity patch is somewhat involved in the max. amount of log files that apache is willing to write to.

Long:

We are experiencing a strange problem witch our apache webserver. The more users we add, the less apache log files are written to. Each time we add another user, some log files suddenly stop being filled.

Of course, we initially thought this was a max-open-files limit that could be adjusted with sysctl, but :

Code: Select all

madoka:~# cat /proc/sys/fs/file-nr
1986    538     27368


As you can see, it's not even near the allowed number of files.

Our second idea was that ulimit's had something to do with it. So:

Code: Select all

madoka:~# ulimit -n 20000
madoka:~# /etc/init.d/apache restart


Unfortunately, this attempt was also insuccesful.

3th attempt: upgrading apache to version 1.3.27 (previously installed: 1.3.26-0woody3 (debian package)). Insuccesful.

Double checked file permissions/ownership of existing log files to make sure apache could write to them. No problem there...

No error's about this in the syslog or apache error.log...

We have no idea what's causing this problem... perhaps someone here has an idea?

a bit more information:

kernel: 2.4.20 with grsecurity-1.9.9e
gradm v1.9.9f
distribution: debian woody

additional info will gladly be provided.