Maybe it's a pound problem. We started to get the same error under heavy load
after the update to the latest pound version (not happend before).
Also the ulimit -n will increase the max number of open file for the current shell
session. But what if pound is started from the boot scripts? Maybe adding
ulimit -n to the startup script will help. Still i think there is some file not closed problem
with the latest pound.
This is not really a pound problem - set "open files" to a higher value, e.g. I''ve set to 8000.ulimit -n 8000(to see the current value)ulimit -a/David
On 9/20/05, Alexander Meis <firstname.lastname@example.org> wrote:Hi...
i got the Problem that under high traffic sometimes there is:
Sep 20 10:07:00 cook8 pound: HTTP accept: Too many open files
Sep 20 10:07:00 cook8 pound: backend xxx.xxx.xxx.xx:80 create: Too many
in the log files. So the Server sends 503 Errors.
Is there some way to fix the Problem?