I have installed mongrel and mongrel_cluster fine and have them running great with my app. I tried using the init.d script provided with mongrel_cluster 2.1 to start it up on boot but it doesn''t. mongrel_cluster_ctl works fine for me by hand and so does /etc/init.d./mongrel_cluster start. I am on Debian so I installed the service links with sudo update-rc.d mongrel_cluster defaults. And yes I chmod''ed it. I checked and double checked /etc/mongrel_cluster and my yml file and everything I can think of. Finally out of frustration I hand linked the system boot stuff like this: sudo ln -s /etc/init.d/mongrel_cluster /etc/rc0.d/S84mongrel_cluster sudo ln -s /etc/init.d/mongrel_cluster /etc/rc3.d/S84mongrel_cluster sudo ln -s /etc/init.d/mongrel_cluster /etc/rc6.d/S84mongrel_cluster And still no luck. Again if I start em up by hand everything works like it should. Thanks for the help, Kyle
On 11/30/06, Kyle Kochis <kylekochis at gmail.com> wrote:> I have installed mongrel and mongrel_cluster fine and have them > running great with my app. I tried using the init.d script provided > with mongrel_cluster 2.1 to start it up on boot but it doesn''t. > mongrel_cluster_ctl works fine for me by hand and so does > /etc/init.d./mongrel_cluster start. I am on Debian so I installed the > service links with sudo update-rc.d mongrel_cluster defaults. And yes > I chmod''ed it. I checked and double checked /etc/mongrel_cluster and > my yml file and everything I can think of. Finally out of frustration > I hand linked the system boot stuff like this: > sudo ln -s /etc/init.d/mongrel_cluster /etc/rc0.d/S84mongrel_cluster > sudo ln -s /etc/init.d/mongrel_cluster /etc/rc3.d/S84mongrel_cluster > sudo ln -s /etc/init.d/mongrel_cluster /etc/rc6.d/S84mongrel_cluster > > And still no luck. Again if I start em up by hand everything works > like it should. > > Thanks for the help, > > KyleWithout appropriate error message only god can help you. -- There was only one Road; that it was like a great river: its springs were at every doorstep, and every path was its tributary.
Make sure the paths needed are available at boot. I had a similar
problem on FreeBSD and was helped out by Andrew Bennett. Here''s what
he had to say:
Hey Jamie,
Yeah, I found that out after using my own script for a while. It is
caused by the way mongrel_cluster starts each of the mongrel servers.
It actually calls the command line "mongrel_rails start ..." on each
of the specified directories. However, when FreeBSD starts up, the
PATH hasn''t been set correctly yet, so calling
"mongrel_rails" results
in a "not found" error because "/usr/local/bin"
hasn''t been added to
the PATH yet.
I just cheated and added the following to /usr/local/etc/rc.d/
mongrel_cluster
...
stop_cmd="stop_cmd"
status_cmd="status_cmd"
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/
local/bin:/usr/X11R6/bin
restart_cmd()
{
...
I added the surrounding lines so you can tell where I''m talking about.
I''m not sure if there is a better way to do this, but it works for
now.
On Nov 30, 2006, at 5:04 AM, hemant wrote:
> On 11/30/06, Kyle Kochis <kylekochis at gmail.com> wrote:
>> I have installed mongrel and mongrel_cluster fine and have them
>> running great with my app. I tried using the init.d script provided
>> with mongrel_cluster 2.1 to start it up on boot but it
doesn''t.
>> mongrel_cluster_ctl works fine for me by hand and so does
>> /etc/init.d./mongrel_cluster start. I am on Debian so I installed the
>> service links with sudo update-rc.d mongrel_cluster defaults. And yes
>> I chmod''ed it. I checked and double checked
/etc/mongrel_cluster and
>> my yml file and everything I can think of. Finally out of frustration
>> I hand linked the system boot stuff like this:
>> sudo ln -s /etc/init.d/mongrel_cluster /etc/rc0.d/S84mongrel_cluster
>> sudo ln -s /etc/init.d/mongrel_cluster /etc/rc3.d/S84mongrel_cluster
>> sudo ln -s /etc/init.d/mongrel_cluster /etc/rc6.d/S84mongrel_cluster
>>
>> And still no luck. Again if I start em up by hand everything works
>> like it should.
>>
>> Thanks for the help,
>>
>> Kyle
>
> Without appropriate error message only god can help you.
>
> --
> There was only one Road; that it was like a great river: its springs
> were at every doorstep, and every path was its tributary.
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
On 11/30/06, Jamie Orchard-Hays <jamie at dangosaur.us> wrote:> > Make sure the paths needed are available at boot. I had a similar > problem on FreeBSD and was helped out by Andrew Bennett. Here''s what > he had to say: > > Hey Jamie, > > Yeah, I found that out after using my own script for a while. It is > caused by the way mongrel_cluster starts each of the mongrel servers. > It actually calls the command line "mongrel_rails start ..." on each > of the specified directories. However, when FreeBSD starts up, the > PATH hasn''t been set correctly yet, so calling "mongrel_rails" results > in a "not found" error because "/usr/local/bin" hasn''t been added to > the PATH yet. > > I just cheated and added the following to /usr/local/etc/rc.d/ > mongrel_cluster > > ... > stop_cmd="stop_cmd" > status_cmd="status_cmd" > > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/ > local/bin:/usr/X11R6/bin > > restart_cmd() > { > ... > > I added the surrounding lines so you can tell where I''m talking about. > I''m not sure if there is a better way to do this, but it works for > now. > > On Nov 30, 2006, at 5:04 AM, hemant wrote: > > > On 11/30/06, Kyle Kochis <kylekochis at gmail.com> wrote: > >> I have installed mongrel and mongrel_cluster fine and have them > >> running great with my app. I tried using the init.d script provided > >> with mongrel_cluster 2.1 to start it up on boot but it doesn''t. > >> mongrel_cluster_ctl works fine for me by hand and so does > >> /etc/init.d./mongrel_cluster start. I am on Debian so I installed the > >> service links with sudo update-rc.d mongrel_cluster defaults. And yes > >> I chmod''ed it. I checked and double checked /etc/mongrel_cluster and > >> my yml file and everything I can think of. Finally out of frustration > >> I hand linked the system boot stuff like this: > >> sudo ln -s /etc/init.d/mongrel_cluster /etc/rc0.d/S84mongrel_cluster > >> sudo ln -s /etc/init.d/mongrel_cluster /etc/rc3.d/S84mongrel_cluster > >> sudo ln -s /etc/init.d/mongrel_cluster /etc/rc6.d/S84mongrel_cluster > >> > >> And still no luck. Again if I start em up by hand everything works > >> like it should. > >> > >> Thanks for the help, > >> > >> Kyle > > > > Without appropriate error message only god can help you. > > > > -- > > There was only one Road; that it was like a great river: its springs > > were at every doorstep, and every path was its tributary. > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > >
Sorry about the double post. Thanks. That fixed the problem. Kyle On 11/30/06, Kyle Kochis <kylekochis at gmail.com> wrote:> On 11/30/06, Jamie Orchard-Hays <jamie at dangosaur.us> wrote: > > > > Make sure the paths needed are available at boot. I had a similar > > problem on FreeBSD and was helped out by Andrew Bennett. Here''s what > > he had to say: > > > > Hey Jamie, > > > > Yeah, I found that out after using my own script for a while. It is > > caused by the way mongrel_cluster starts each of the mongrel servers. > > It actually calls the command line "mongrel_rails start ..." on each > > of the specified directories. However, when FreeBSD starts up, the > > PATH hasn''t been set correctly yet, so calling "mongrel_rails" results > > in a "not found" error because "/usr/local/bin" hasn''t been added to > > the PATH yet. > > > > I just cheated and added the following to /usr/local/etc/rc.d/ > > mongrel_cluster > > > > ... > > stop_cmd="stop_cmd" > > status_cmd="status_cmd" > > > > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/ > > local/bin:/usr/X11R6/bin > > > > restart_cmd() > > { > > ... > > > > I added the surrounding lines so you can tell where I''m talking about. > > I''m not sure if there is a better way to do this, but it works for > > now. > > > > On Nov 30, 2006, at 5:04 AM, hemant wrote: > > > > > On 11/30/06, Kyle Kochis <kylekochis at gmail.com> wrote: > > >> I have installed mongrel and mongrel_cluster fine and have them > > >> running great with my app. I tried using the init.d script provided > > >> with mongrel_cluster 2.1 to start it up on boot but it doesn''t. > > >> mongrel_cluster_ctl works fine for me by hand and so does > > >> /etc/init.d./mongrel_cluster start. I am on Debian so I installed the > > >> service links with sudo update-rc.d mongrel_cluster defaults. And yes > > >> I chmod''ed it. I checked and double checked /etc/mongrel_cluster and > > >> my yml file and everything I can think of. Finally out of frustration > > >> I hand linked the system boot stuff like this: > > >> sudo ln -s /etc/init.d/mongrel_cluster /etc/rc0.d/S84mongrel_cluster > > >> sudo ln -s /etc/init.d/mongrel_cluster /etc/rc3.d/S84mongrel_cluster > > >> sudo ln -s /etc/init.d/mongrel_cluster /etc/rc6.d/S84mongrel_cluster > > >> > > >> And still no luck. Again if I start em up by hand everything works > > >> like it should. > > >> > > >> Thanks for the help, > > >> > > >> Kyle > > > > > > Without appropriate error message only god can help you. > > > > > > -- > > > There was only one Road; that it was like a great river: its springs > > > were at every doorstep, and every path was its tributary. > > > _______________________________________________ > > > Mongrel-users mailing list > > > Mongrel-users at rubyforge.org > > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > > > > >