Jonathan Rochkind wrote: > When "mongrel_rails cluster::start" is run but does NOT actually > succesfully start up your mongrels, it doesn't neccesarily give you any > error messages. Is what I have noticed. I have had cluster::start fail > but not give me any error messages. > > So if cluster::stop is telling you "already stopped", I think that means > that you never succesfully started it in the first place, you just > didn't realize it. > > So now the real question is, Why didn't it succesfully start in the > first place, and how do you figure that out? That's the trick, I'm not > sure. > > Jonathan
how to find out the errors? but it is not showing any error when it is starting. -- Posted via http://www.ruby-forum.com/. _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
