However, I'm setting up a staging environment right now, and I'm getting what looks like three mongrel processes *all listening on the same port* for each mongrel instance I start. Should I be seeing this?
ps -ef | grep mongrel
root 8971 1 6 13:37 ? 00:00:00 /usr/local/bin/ruby /usr/local/bin/mongrel_rails start -d -e production -p 8020 -a 127.0.0.1 -l /var/www/apps/thoth/current/log/mongrel.log -P /var/www/apps/thoth/current/log/mongrel.8020.pid -c /var/www/apps/thoth/current
root 8972 8971 0 13:37 ? 00:00:00 /usr/local/bin/ruby /usr/local/bin/mongrel_rails start -d -e production -p 8020 -a 127.0.0.1 -l /var/www/apps/thoth/current/log/mongrel.log -P /var/www/apps/thoth/current/log/mongrel.8020.pid -c /var/www/apps/thoth/current
root 8973 8972 0 13:37 ? 00:00:00 /usr/local/bin/ruby /usr/local/bin/mongrel_rails start -d -e production -p 8020 -a 127.0.0.1 -l /var/www/apps/thoth/current/log/mongrel.log -P /var/www/apps/thoth/current/log/mongrel.8020.pid -c /var/www/apps/thoth/current
root 8975 8919 0 13:37 pts/0 00:00:00 grep mongrel
Background facts:
- Overall setup: VPS at Rimu; custom compiled Apache 2.2 w/mod proxy -> mongrel cluster
- distro: centos 4
- mongrel: 0.3.13.4
- ruby: 1.8.4
Here's a console session showing the three processes. Here I'm starting a single instance, but the same thing happens when I start a cluster (I get 3x process for each mongrel server).
-------------------------------------------------------------
root$/var/www/apps/thoth/current/log >ps -ef | grep mongrel
root 8968 8919 0 13:36 pts/0 00:00:00 grep mongrel
root$/var/www/apps/thoth/current/log >/usr/local/bin/mongrel_rails start -d -e production -p 8020 -a 127.0.0.1 -l /var/www/apps/thoth/current/log/mongrel.log -P /var/www/apps/thoth/current/log/mongrel.8020.pid -c /var/www/apps/thoth/current
root$/var/www/apps/thoth/current/log >ps -ef | grep mongrel
root 8971 1 6 13:37 ? 00:00:00 /usr/local/bin/ruby /usr/local/bin/mongrel_rails start -d -e production -p 8020 -a 127.0.0.1 -l /var/www/apps/thoth/current/log/mongrel.log -P /var/www/apps/thoth/current/log/mongrel.8020.pid -c /var/www/apps/thoth/current
root 8972 8971 0 13:37 ? 00:00:00 /usr/local/bin/ruby /usr/local/bin/mongrel_rails start -d -e production -p 8020 -a 127.0.0.1 -l /var/www/apps/thoth/current/log/mongrel.log -P /var/www/apps/thoth/current/log/mongrel.8020.pid -c /var/www/apps/thoth/current
root 8973 8972 0 13:37 ? 00:00:00 /usr/local/bin/ruby /usr/local/bin/mongrel_rails start -d -e production -p 8020 -a 127.0.0.1 -l /var/www/apps/thoth/current/log/mongrel.log -P /var/www/apps/thoth/current/log/mongrel.8020.pid -c /var/www/apps/thoth/current
root 8975 8919 0 13:37 pts/0 00:00:00 grep mongrel
root$/var/www/apps/thoth/current/log >ls
total 48
drwxrwxrwx 2 deploy deploy 4096 Nov 4 13:37 .
drwxr-xr-x 6 deploy deploy 4096 Nov 3 20:06 ..
-rw-rw-rw- 1 root root 4 Nov 4 13:37 mongrel.8020.pid
-rw-rw-rw- 1 root root 590 Nov 4 13:37 mongrel.log
-rw-r--r-- 1 root root 31632 Nov 3 21:20 production.log
root$/var/www/apps/thoth/current/log >cat mongrel.log
** Daemonized, any open files are closed. Look at /var/www/apps/thoth/current/log/mongrel.8020.pid and /var/www/apps/thoth/current/log/mongrel.log for info.
** Starting Mongrel listening at 127.0.0.1:8020
** Starting Rails with production environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart).
** Rails signals registered. HUP => reload (without restart). It might not work well.
** Mongrel available at 127.0.0.1:8020
** Writing PID file to /var/www/apps/thoth/current/log/mongrel.8020.pid
root$/var/www/apps/thoth/current/log >
--
[EMAIL PROTECTED]
My tech blog: http://earthcode.com
Wifi cafes: http://wifi.earthcode.com
_______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
