[Mongrel] Weird Mongrel error: Not starting.

Rafael G. rgo at aspgems.com
Thu Dec 13 09:27:57 EST 2007


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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: rgo.vcf
Type: text/x-vcard
Size: 251 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20071213/342c7a54/attachment-0001.vcf 


More information about the Mongrel-users mailing list