[Mongrel] Mongrel server file descriptor leak?
John Nestoriak
lists at ruby-forum.com
Tue Feb 10 15:06:28 EST 2009
Benjamin Grant wrote:
> Can you post the content of your mongrel_cluster.yml (or equivalent
> command
> line options in use) & mongrel version...?
>
> Also the output of "ulimit -a" for the mongrel process owner.
>
> --
The mongrels are started under CPanel and we're not using clusters.
>From ps it looks like they're just started with:
/usr/bin/ruby /usr/bin/mongrel_rails start -p 12005 -d -e production -P
log/mongrel.pid
It's running mongrel 1.1.5
ruby 1.8.7 (2008-06-20 patchlevel 22) [i686-linux]
I'm not sure exactly how many file descriptors causes it to die - though
I've seen 400+ and it running fine and I'm guessing it dies at 512.
Ulimit doesn't seem like it's changed at all.
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 73728
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
--
Posted via http://www.ruby-forum.com/.
More information about the Mongrel-users
mailing list