I followed the instructions for this. I can start with mongrel_cluster_ctl no problem, but on reboot, the mongrel servers are not starting.
I'm running user/group as www It wouldn't start when trying to write the pid files to /var/run, so I'm writing to the app's log dir. Nothing is written to the mongrel log on reboot, so it doesn't seem to be doing anything. tail gives: ** TERM signal received. ** TERM signal received. ** TERM signal received. for the last three lines from system restart. rc.conf: mongrel_cluster_enable="YES" mongrel_cluster_config="/usr/local/etc/mongrel_cluster" conf file is nlx.yml FreeBSD 6.1 Rails edge latest prerelease mongrel latest mongrel_cluster Looking for ideas. Thanks, Jamie On Jul 28, 2006, at 4:04 PM, Andrew Bennett wrote: > I wanted to be able to specify in my /etc/rc.conf file whether > mongrel_cluster should be enabled and the mongrel_cluster_config file > for the init script, so I wrote this simple rc.d style script. > > Just throw it in /usr/local/etc/rc.d/ and do a chmod +x > /usr/local/etc/rc.d/mongrel_cluster.sh > > To enable the script, add mongrel_cluster_enable="YES" to /etc/rc.conf > and optionally add mongrel_cluster_config="/etc/mongrel_cluster" > > The default config path is /usr/local/etc/mongrel_cluster > > Would be nice if mongrel_cluster_ctl had some sort of "status" switch > to see if the servers are actually running and what their pids are. > > Andrew Bennett > [EMAIL PROTECTED] > <mongrel_cluster.sh> > _______________________________________________ > Mongrel-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/mongrel-users _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
