Re: Testing Mongrel Configuration

Matt Pelletier
Tue, 17 Oct 2006 00:03:12 -0000

On 10/14/06, Will Gant
<williamwgant-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
wrote:
>
> I tried creating the config file as you suggested. I think something else
> may be broken:
>
> wgant@sauron:/etc/mongrel/sites-enabled$ mongrel_rails start -G
> test.config -e production
> !!! Path to log file not valid: log/mongrel.log
> start reported an error. Use mongrel_rails start -h to get help.


Are you calling this from within a Rails application''s root
(doesn''t look
like it)? You should be.

Matt

I then tried the following:
>
> wgant@sauron:/etc/mongrel/sites-enabled$ mongrel_rails start -G
> test.config -e production -l /home/wgant/mongrel.log
> !!! Path to pid file not valid: log/mongrel.pid
> start reported an error. Use mongrel_rails start -h to get help.
> wgant@sauron:/etc/mongrel/sites-enabled$ mongrel_rails start -G
> test.config -e production -l /home/wgant/mongrel.log -p
> /home/wgant/mongrel.pid
> !!! Path to pid file not valid: log/mongrel.pid
> start reported an error. Use mongrel_rails start -h to get help.
> wgant@sauron:/etc/mongrel/sites-enabled$ mongrel_rails start -G
> test.config -e production -l /home/wgant/mongrel.log -P
> /home/wgant/mongrel.pid
> !!! Path to docroot not valid: public
> start reported an error. Use mongrel_rails start -h to get help.
>
> By the way, are you "the" Zed that wrote Mongrel?


He answers to many names. "Zed" is one of them.

Thanks,
> Will
>
> *"Zed A. Shaw"
<zedshaw-dd7LMGGEL7NBDgjK7y7TUQ@public.gmane.org>* wrote:
>
>
> On Fri, 13 Oct 2006 08:03:41 -0700 (PDT)
> Will Gant wrote:
>
> > Hello all,
> > Here are the contents of my /etc/mongrel/sites-enabled/test.config
file:
> > #RAILS_ROOT of your application
> > dir=/home/wgant/Desktop/test
> > #port the first mongrel instance should listen to, additional
instances
> listen to ports above
> > port=8100
> > #number of instances
> > servers=3
> > #port pen will listen on
> > proxy_port=8001
> >
>
> Don''t write your own config file by hand, use the -G option to
Mongrel so
> that it gets generated correctly. You can then modify it from there. You do
> it like this:
>
> mongrel_rails start -G test.config -e production ...
>
> (where ... is any other options you need)
>
> It''ll then tell you it created test.config and you just need to
run it
> with:
>
> mongrel_rails start -C test.config
>
> And that''s it.
>
> --
> Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu
> http://www.zedshaw.com/
> http://mongrel.rubyforge.org/
> http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.
>
> ------------------------------
> Get your own web address for just $1.99/1st yr. We''ll help. Yahoo!
Small
>
Business<http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/>.
>
> >