Hi, I''m in the process of moving my blog over from lighttpd -> apache 2.2 + mongrel. Everything works fine as long as I don''t reboot :) On reboot apache comes up but mongrel_cluster doesn''t start up the pooches... I have added the mongrel_cluster call to my startup scripts like so: www:/etc/init.d# update-rc.d mongrel_cluster defaults Adding system startup for /etc/init.d/mongrel_cluster ... /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster www:/etc/init.d# Specs: mongrel 0.3.13.3 mongrel_cluster 0.2.0 on debian sarge (rimu). Any ideas? -- Zack Chandler http://depixelate.com
On Aug 15, 2006, at 3:55 PM, Zack Chandler wrote:> Hi, > > I''m in the process of moving my blog over from lighttpd -> apache 2.2 > + mongrel. Everything works fine as long as I don''t reboot :) > > On reboot apache comes up but mongrel_cluster doesn''t start up the > pooches... > > I have added the mongrel_cluster call to my startup scripts like so: > > www:/etc/init.d# update-rc.d mongrel_cluster defaults > Adding system startup for /etc/init.d/mongrel_cluster ... > /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > www:/etc/init.d# > > Specs: > mongrel 0.3.13.3 > mongrel_cluster 0.2.0 on > debian sarge (rimu). > > Any ideas?What happens when you run that startup script on it''s own? Often the problem with these (like cronjobs on reboot) is that you need full paths to everything. On reboot root will do things like use the sh shell to get things going and it doesn''t know where to look. - J
On 8/15/06, Jason A. Hoffman <jason at joyent.com> wrote:> On Aug 15, 2006, at 3:55 PM, Zack Chandler wrote: > > Hi, > > > > I''m in the process of moving my blog over from lighttpd -> apache 2.2 > > + mongrel. Everything works fine as long as I don''t reboot :) > > > > On reboot apache comes up but mongrel_cluster doesn''t start up the > > pooches... > > > > I have added the mongrel_cluster call to my startup scripts like so: > > > > www:/etc/init.d# update-rc.d mongrel_cluster defaults > > Adding system startup for /etc/init.d/mongrel_cluster ... > > /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > > www:/etc/init.d# > > > > Specs: > > mongrel 0.3.13.3 > > mongrel_cluster 0.2.0 on > > debian sarge (rimu). > > > > Any ideas? > > What happens when you run that startup script on it''s own? > > Often the problem with these (like cronjobs on reboot) is that you > need full paths to everything. On reboot root will do things like use > the sh shell to get things going and it doesn''t know where to look. > > - J > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >Jason,>sudo /etc/init.d/mongrel_cluster startworks fine from the command line. Any other ideas? -- Zack Chandler http://depixelate.com
> Jason, > >> sudo /etc/init.d/mongrel_cluster start > works fine from the command line. > > Any other ideas?What are the permissions on the file (ls -aol /etc/init.d/ mongrel_cluster) and the contents? - J
On Aug 15, 2006, at 5:26 PM, Zack Chandler wrote:> On 8/15/06, Jason A. Hoffman <jason at joyent.com> wrote: >> On Aug 15, 2006, at 3:55 PM, Zack Chandler wrote: >>> Hi, >>> >>> I''m in the process of moving my blog over from lighttpd -> apache >>> 2.2 >>> + mongrel. Everything works fine as long as I don''t reboot :) >>> >>> On reboot apache comes up but mongrel_cluster doesn''t start up the >>> pooches... >>> >>> I have added the mongrel_cluster call to my startup scripts like >>> so: >>> >>> www:/etc/init.d# update-rc.d mongrel_cluster defaults >>> Adding system startup for /etc/init.d/mongrel_cluster ... >>> /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> www:/etc/init.d#You know what, looking at this the rc6.d (from what I recall, I''m a solaris/BSD person) is that run level 6 is the System reboot runtime for debian, and when something is a "K" it disables the service and keeps it stopped. 2,3,4,5 are probably all multiuser and they''re "S", that''s why it works from the command line once it''s up. Maybe rename all the K20mongrel_cluster ones to S20mongrel_cluster. - Jason
On 8/15/06, Jason A. Hoffman <jason at joyent.com> wrote:> On Aug 15, 2006, at 5:26 PM, Zack Chandler wrote: > > On 8/15/06, Jason A. Hoffman <jason at joyent.com> wrote: > >> On Aug 15, 2006, at 3:55 PM, Zack Chandler wrote: > >>> Hi, > >>> > >>> I''m in the process of moving my blog over from lighttpd -> apache > >>> 2.2 > >>> + mongrel. Everything works fine as long as I don''t reboot :) > >>> > >>> On reboot apache comes up but mongrel_cluster doesn''t start up the > >>> pooches... > >>> > >>> I have added the mongrel_cluster call to my startup scripts like > >>> so: > >>> > >>> www:/etc/init.d# update-rc.d mongrel_cluster defaults > >>> Adding system startup for /etc/init.d/mongrel_cluster ... > >>> /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > >>> www:/etc/init.d# > > You know what, looking at this the rc6.d (from what I recall, I''m a > solaris/BSD person) is that run level 6 is the System reboot runtime > for debian, and when something is a "K" it disables the service and > keeps it stopped. > > 2,3,4,5 are probably all multiuser and they''re "S", that''s why it > works from the command line once it''s up. Maybe rename all the > K20mongrel_cluster ones to S20mongrel_cluster. > > - Jason > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >> > >Jason, I found out Rimuhosting supports console-over-ssh. That is sweet! Once I logged in I noticed this line: command not found: mongrel_cluster_ctl I guess /usr/local/bin is not in the boot PATH. I symlinked the following ln -s /usr/local/bin/mongrel_cluster_ctl mongrel_cluster_ctl ln -s /usr/local/bin/mongrel_rails mongrel_rails and it worked like a charm. Thanks! -- Zack Chandler http://depixelate.com
> > > Jason, > > I found out Rimuhosting supports console-over-ssh. That is sweet! > Once I logged in I noticed this line: >Where did you notice this? I can''t get my mongrels to restart on boot. I''m running debian on rimu, if that''s important. Any help is appreciated. -Kelly -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20061011/f2b1d5c2/attachment.html
Kelly, You probably need to symlink mongrel_cluster_ctl and mongrel_rails to /usr/bin as /usr/local/bin is not in the debian boot path. You can see how I did it here: http://depixelate.com/2006/8/15/switched-to-mongrel I would also recommend using Rimu''s console-over-ssh to sniff out the problem. Hope this helps, Zack On 10/11/06, Kelly Felkins <railsinator at gmail.com> wrote:> > > > > Jason, > > > > I found out Rimuhosting supports console-over-ssh. That is sweet! > > Once I logged in I noticed this line: > > > > Where did you notice this? I can''t get my mongrels to restart on boot. > > I''m running debian on rimu, if that''s important. > > Any help is appreciated. > > -Kelly > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > >