On Dec 7, 2006, at 3:44 PM, Zed A. Shaw wrote: > > There is kind of a dumb race condition I've gotta fix this week > where if you stop a mongrel process, but mongrel needs to wait on > some threads to finish, and then start a new one, all hell breaks > loose. > > Check if this is the case by doing this: > > 1) Tail the mongrel.log in a window off to the side. > 2) Start some requests or something that's common usage. > 3) Stop mongrel and look for log messages saying that process is > waiting on threads to finish. > 4) Right away start a new mongrel to replace this one. The .pid > file gets wiped out by this, and since the previous process is > waiting, the new process can't bind. > 5) Once the original process dies you'll be in the situation you've > got. > > See if that's the problem. If it is then hang on as I'm beefing up > the start/stop logic to be a bit smarter about this.
Yep, that's it. Thanks for the reply - I'll just hang on for now. Cheers _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
