On Thu, Jun 25, 2009 at 2:07 AM, Michael Pliskin wrote:
> Hi all,
>
>
>
> Some disclaimer first: I am a complete newbie in mongrel and this list, so
> please forgive me if I say something weird. I have a problem, I’ve googled
> for a solution for quite a while and failed so far, so decided to ask h
Dear Luis,
Thanks a lot for replying, I followed your advice and it revealed the problem:
it was the --prefix switch that caused it. When I start it like
E:\RailsApps\3vi>mongrel_rails start -e development -p 3001 -a 127.0.0.1 -l
"e:/RailsApps/3vi/log/1.log" -P "e:/RailsApps/3vi/log/mongrel.pid
Are you using Rails 2.2?
The latest version of mongrel available by gem is broken with --prefix
and Rails 2.2. I'd still expect it to simply report an error instead of
consuming all CPU, so that's odd (but I've never developed Rails on
Windows before either).
But if you are using Rails 2.2
Ah, actually reading your stack trace, I see it is indeed the --prefix
and modern versions of Rails issue. I still don't know why that
consumes all CPU instead of just reporting an error.
But mongrel is trying to call a method that no longer exists in RAils
2.3 like you have. (I think it diss
On Thu, Jun 25, 2009 at 11:04 AM, Jonathan Rochkind wrote:
> Are you using Rails 2.2?
> The latest version of mongrel available by gem is broken with --prefix and
> Rails 2.2. I'd still expect it to simply report an error instead of
> consuming all CPU, so that's odd (but I've never developed Rail
