Try adding -a option:
/usr/bin/mongrel_rails start -c /srv/rails/appname -P
/srv/rails/appname/log/mongrel.pid -l /srv/rails/appname/log/mongrel.log
-e production -d -p 3013 -a 127.0.0.1
Only for check if run.
Nii amon Dsane escribió:
Hi Rafael,
Thanks for the quick response.
I am not using mongrel_cluster yet. I am just starting each
mongrel_rails instance manually. The command I use is below:
/usr/bin/mongrel_rails start -c /srv/rails/appname -P
/srv/rails/appname/log/mongrel.pid -l /srv/rails/appname/log/mongrel.log
-e production -d -p 3013.
I cd to RAILS_ROOT and then issue that command as root and then the
error appears.
Thanks
Nii Amon
Rafael García wrote:
Nii Amon Dsane escribió:
Hi list,
Hi Nii,
3. After the reboot mongrel_rails fails to load for one particular
application though I have other applications running on the same
server without any issues. This is the error that I get:
** Starting Mongrel listening at 0.0.0.0:3013 <http://0.0.0.0:3013>
In your config/mongrel_cluster.yml try setting address parameter to
127.0.0.1 and explain results.
Regards
--
Rafael Garcia Ortega
begin:vcard
fn;quoted-printable:Rafael Garc=C3=ADa Ortega
n;quoted-printable:Garc=C3=ADa Ortega;Rafael
org:ASPgems S.L.
email;internet:[EMAIL PROTECTED]
tel;work:692686533
x-mozilla-html:FALSE
url:http://www.aspgems.com
version:2.1
end:vcard
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
