similar to: Mongrel doesn''t start under Rails 2.0.2/Win XP

I''m running jruby trunk which has integrated rubygems 1.0.0 and when I try and install mongrel with gem it blows up when the fastthread dependency tries to do a native compilation. I couldn''t find a copy of the gemspec in the svn checkout but looking at the one installed when gem installing mongrel didn''t show any platform differentiation. There is platform

Something suddenly went wrong in my ruby install. When installing Mongrel on my Windows XP laptop, it incorrectly tries to build it as a native extension. I don''t even get the selection where I can choose to install a compiled version. I would appreciate any help/links or similar, as I frankly don''t understand what''s going on and why I dont get the usual selection box.

I''m confused. Wasn''t threading fixed in 1.8.6, negating the need for fastthread? Why is fastthread still a requirement of Mongrel? Just curious. :)

Hey so, People are asking about Mongrel Ruby 1.9 compatibility. Isn''t the point of 1.9 for library developers to have time to get ready for 2.0? It''s not like 1.9 is a production release. Evan -- Evan Weaver Cloudburst, LLC

Guys, Subject says everything: http://www.frederico-araujo.com/2007/12/18/my-first-successful-booting-rails-2-0-2-ruby-1-9-attempt Even ActionView uses Proc.binding (which isn''t correctly supported in 1.9) it appears that lot of folks will try to put their hands in Ruby 1.9 when it comes out, and of course, try to get Rails with Mongrel running in it. Zed, Wayne, Evan and ry: maybe we

Hi, I just did a clean install of Ruby 1.8.5 Rubygems 0.9.0 and the Mongrel and Mongrel_Cluster gems. I used only the Debian Etch package manager, nothing compiled myself. Now, on a testapp when I do a script/server, I get the: ** Ruby version is not up-to-date; loading cgi_multipart_eof_fix warning. But it''s not serving my app. Ruby is immediately on 100% CPU load (and 0.7%

FYI. -- - Brian Gupta http://opensolaris.org/os/project/nycosug/

Hello Guys, I''ll like to suggest a small release fix before we start doing big changes: platform fixes. Current we''re setting MSWIN32 (mswin32) as platform for Windows gem, but we should be using Gem::Platform::CURRENT instead (i386-mswin32 as current Ruby windows implementation). Also, the jruby/java platform need to be defined. That change will ease the compatibility path

I can''t get mongrel installed on a Win XP. I keep getting some unknown error with this "win32-service-0.5.2". While it states results are logged, the file is empty - not much help. I even tried complete uninstall of ruby and reinstalled ruby 1.8.5-21. But no luck. Oddly, I had no problem installing earlier on a Win 2K machine. Is there something special about XP? here

Hey Daniel, I''m trying to leave you a comment on this article you wrote: http://djberg96.livejournal.com/168403.html But since you disabled OpenID and anonyous, I''m not fond to register for another account just to reply your comments. Quoting your post: "" Unfortunately, I''ve slammed into the cold hard fact that FFI just isn''t the grand solution

Hi all, There is a bug with Mongrel on JRuby 1.0.3 that the JRuby guys want fixed before they release it. If it''s ok with people I''d like to fix that, revert (at least for now) the proxy response change, and tag that as 1.1.2 and release it. Anything wrong with this plan? Evan -- Evan Weaver Cloudburst, LLC

Hi, I''m trying to start a Mongrel (1.1.3) Server, running as a Windows Service, via mongrel_rails service::install -N FDS_Server_4001 -p 4001 -e production But I get the following error message : ERROR RUNNING ''service::install'': Plugin /service::install does not exist in category /commands I never had this problem before (Win XP, Vista), until I tried installing on

Hello Guys, I''m reviewing the code for 1.9, and forgot about this when we first spoke on this subject. The current way we stop threads is using Thread#raise to spread StopServer exception, which will not work as expected in 1.9. 1.9 will treat raised exceptions as #kill, like JRuby does, so the worker threads will not finish serving the client and _then_ exiting, but will be

I am using Rspec 1.1.2 on Windows XP SP2 I am receiving the following error when I run ''rake spec'' from a brand new project: C:/SVN_Projects/rspec/vendor/plugins/rspec/lib/spec/runner/options.rb:107:in `colour='': You must gem install win32console to use colour on Windows (RuntimeError) I have the win32console gem installed and the error still occurs. It seems that the

It appears that Mongrel is now the default development server for Rails as of 2.x. I''m assuming this because I''m unable to run Mongrel (for reasons I don''t totally understand yet - I am running Windows and I keep getting asked for MSVCR80.dll which is a _64 bit_ dll on my Win XP machine) and if I issue ruby script/server, I see the same errors that I get when I try to

It looks like fastthread was rolled into 1.8.6: http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/tags/v1_8_6/NEWS?revision=12055&view=markup Does that mean once we upgrade to 186 we can forget about rubygem version? - Rob

Hello Mongrel Users, I''m writing a web server called Ebb. It''s written in C, makes use of the Mongrel HTTP parser, and uses libev its event loop. The goal is to be small, fast, and language independent server that can host web frameworks. I have written a small Ruby binding which provides a Rack handler - this will allow Ebb to host Rails, Merb, and other Ruby frameworks. In the

* Apologies for starting a new thread; I just subscribed. Has anyone been able to make this exploit happen if requests are being proxied to Mongrel through Apache? I''ve been trying variations on the double-encoding thing and can''t trigger the exploit through Apache. Hitting Mongrel directly does expose the problem. I''ll still upgrade my servers, of course, but I

Is anybody testing mongrel on ruby 1.9. I just tried installing mongrel on trunk 1.9 and trunk rubygems and got this error compiling fastthread: /Users/stephen/dev/ruby/1.9_trunk/bin/ruby extconf.rb install mongrel --no-rdoc creating Makefile make gcc -I. -I/Users/stephen/dev/ruby/1.9_trunk/include/ruby-1.9/i686-darwin8.10.1 -I/Users/stephen/dev/ruby/1.9_trunk/include/ruby-1.9 -I.

Hi all, I''d really appreciate some help with this... As you see below, I tried to install mongrel after updating my gems, but I get the error shown: sudo gem install mongrel Select which gem to install for your platform (i486-linux) 1. mongrel 1.0.1 (ruby) 2. mongrel 1.0.1 (mswin32) 3. mongrel 1.0 (mswin32) 4. mongrel 1.0 (ruby) 5. Skip this gem 6. Cancel installation > 1