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 [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
