[Mongrel] mongrel startup fails now: already initialized constant OPTIONS

Ian Pancham lists at ruby-forum.com
Thu Nov 29 10:29:03 EST 2007


I had a similar problem today that was resolved by uninstalling and 
re-installing mongrel. I don't have ruport installed. I tried 
uninstalling gem_plugin first and then reinstalling, but that seemed to 
make no difference, mongrel still died with the "options" method error 
for Array.  In case it helps, here are the relevant lines:

Ian$ script/server
=> Booting Mongrel (use 'script/server webrick' to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Exiting
/usr/local/lib/ruby/gems/1.8/gems/rails-1.2.6/lib/commands/servers/mongrel.rb:15: 
warning: already initialized constant OPTIONS
/usr/local/lib/ruby/gems/1.8/gems/rails-1.2.6/lib/commands/servers/mongrel.rb:18: 
undefined method `options' for #<Array:0x136ef38> (NoMethodError)
....

Ian$ sudo gem uninstall mongrel
Successfully uninstalled mongrel version 1.1
Remove executables and scripts for
'mongrel_rails' in addition to the gem? [Yn]  y
Removing mongrel_rails
...

Ian$ sudo gem install mongrel
Select which gem to install for your platform (powerpc-darwin8.10.0)
 1. mongrel 1.1.1 (ruby)
 2. mongrel 1.1.1 (jruby)
 3. mongrel 1.1.1 (mswin32)
 4. mongrel 1.1 (mswin32)
 5. mongrel 1.1 (ruby)
 6. mongrel 1.1 (jruby)
 7. Skip this gem
 8. Cancel installation
> 5
Install required dependency daemons? [Yn]  y
Install required dependency fastthread? [Yn]  y
Select which gem to install for your platform (powerpc-darwin8.10.0)
 1. fastthread 1.0.1 (mswin32)
 2. fastthread 1.0.1 (ruby)
 3. Skip this gem
 4. Cancel installation
> 2
Building native extensions.  This could take a while...
Building native extensions.  This could take a while...
Successfully installed mongrel-1.1
Successfully installed daemons-1.0.9
Successfully installed fastthread-1.0.1
...

Ian$ script/server
=> Booting Mongrel (use 'script/server webrick' to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with development environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  TERM => stop.  USR2 => restart.  INT => stop (no 
restart).
** Rails signals registered.  HUP => reload (without restart).  It might 
not work well.

I then upgraded to mongrel 1.1.1 and this also worked.





Stephen Bannasch wrote:
> fyi:
> 
> Gregory Brown, the developer of Ruport reports:
> 
> At 8:02 AM -0500 11/15/07, Gregory Brown wrote:
>>If you have versions 0.8.10 -> 0.8.14 laying around and are
>>experiencing this problem, try deleting them.
>>
>>Also, thanks for pointing this problem out, I've seen it before but
>>only in weird cases, and was wondering what happened.
> 
> Sounds like it could be a problem with gem_plugin, or interactions 
> between gem_plugin and rails, or gem_plugin ,rails, mongrel, ruby 1.8.6, 
> and ruport <1.0

-- 
Posted via http://www.ruby-forum.com/.


More information about the Mongrel-users mailing list