used gem to install mongrel 1.0.1. seemed to go w/o errors.
“mongrel_rails start -d” spits out this error
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/http11.bundle:
Failed to load
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/http11.bundle
(LoadError)
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in require' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:11 from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:ingem_original_require’
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in require' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/bin/mongrel_rails:9 from /usr/local/bin/mongrel_rails:16:inload’
from /usr/local/bin/mongrel_rails:16
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
`require’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:11
It seems there is no bundle (compiled extension) for http11, which is
need by Mongrel.
installed again with --include-dependencies
still getting same error.
lost. need a flashlight.
Do you have everything to compile ruby extensions in place? Which
version of ruby are you using? the broken one that came with OSX or
compiled by hand?
What’s the output of gem install mongrel? You should see the details
about “building native extensions”…
–
Luis L.
Multimedia systems
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi
On 10/11/07, Greg W. [email protected] wrote:
It seems there is no bundle (compiled extension) for http11, which is
need by Mongrel.
Do you have everything to compile ruby extensions in place?
Unknown. (ruby newbie).
Which version of ruby are you using?
The one from here: http://rubyosx.rubyforge.org/ – which I see should
already have Mongrel in it, but then I installed… oh, hang on. Maybe I
broke it by monkeying with gem installs afterwards.
OK, I just re-installed using that installer, and now mongrel launches,
but complains about a log path being invalid.
So, I’m further along. I’ll see if I can figure out the log thing.
Thanks Luis, that got me to re-evaluate what I had done.
The one from here: http://rubyosx.rubyforge.org/ – which I see should
already have Mongrel in it, but then I installed… oh, hang on. Maybe I
broke it by monkeying with gem installs afterwards.
Yeah, Ruby for OSX have Mongrel pre-compiled (along with Ruby) so you
don’t need a compilation/build environment in place.
Is like One-Click-Installer on Windows
OK, I just re-installed using that installer, and now mongrel launches,
but complains about a log path being invalid.
you’re runnin mongrel_rails start inside the root of your Rails
application? maybe there isn’t a log folder inside it, or the
permissions aren’t valid.
So, I’m further along. I’ll see if I can figure out the log thing.
Could you post the messages mongrel_rails start is showing you? that
could help us provide you better support
Thanks Luis, that got me to re-evaluate what I had done.
No problem, I’m glad being helpful.
–
Luis L.
Multimedia systems
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi
I guess we could make “mongrel_rails” script more intelligent about
where you are and if that folder is a Rails one
There is also Locomotive [1] which provides a simpler way to configure
mongrels for your applications. It differs from Ruby OSX is that is
tailored for Rails (and rubyosx is more ruby generic).
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi
There is also Locomotive [1] which provides a simpler way to configure
mongrels for your applications. It differs from Ruby OSX is that is
tailored for Rails (and rubyosx is more ruby generic).
My thought was maybe that would isolate me too much from what’s going
on. After I get my feet wet a little bit with just getting some stuff
running and working in Rails, I’ll probably go back and uninstall
everything and try it by hand.
Wandering off into another (related) topic…
Right now I’m trying to figure out how to get multiple apps running on
mongrels with dev URLs
I’m used to using www.XYZ.dev and www.ABC.dev in my browser, and then
using NetInfo machines or even hosts to map those to 127.0.0.1
I thought 127.0.0.1:3000 www.abc.dev would work but it didn’t.
I understand that I’ll have to run multiple mongrels on unique ports,
but haven’t figured out how to map a URL to the localhost:port yet
OK, I just re-installed using that installer, and now mongrel launches,
but complains about a log path being invalid.
you’re runnin mongrel_rails start inside the root of your Rails
application? maybe there isn’t a log folder inside it, or the
permissions aren’t valid.
Yeah I was one dir above my app, so that was the problem. All looks good
now.
(lots of voodoo to get this stuff running compared to what I am used to
– Lasso)
Right now I’m trying to figure out how to get multiple apps running on
mongrels with dev URLs
I’m used to using www.XYZ.dev and www.ABC.dev in my browser, and then
using NetInfo machines or even hosts to map those to 127.0.0.1
I thought 127.0.0.1:3000 www.abc.dev would work but it didn’t.
btw, I know I can use Apache 2.2 mod_proxy_balancer – I actually helped
set one of those up (though I didn’t do the mongerl stuff then), so I
can just do that I guess. Just more junk to install since using Apache
1.3 is fine for everything else I do on my dev system.
used gem to install mongrel 1.0.1. seemed to go w/o errors.
“mongrel_rails start -d” spits out this error
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/http11.bundle:
Failed to load
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/http11.bundle
(LoadError)
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in require' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:11 from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:ingem_original_require’
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in require' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/bin/mongrel_rails:9 from /usr/local/bin/mongrel_rails:16:inload’
from /usr/local/bin/mongrel_rails:16
installed again with --include-dependencies
still getting same error.
lost. need a flashlight.
– gw
Hi,
Im a newbie to ruby and rails. I installed mongrel using the command:
sudo gem install mongrel --include-dependencies
When i try to start mongrel with
mongrel_rails start -d, its throwing the same error as it did to you:
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in gem_original_require': no such file to load -- http11 (LoadError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:inrequire’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3-java/lib/mongrel.rb:12
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in gem_original_require' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:inrequire’
from
/usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/mongrel_rails:17
from /usr/local/bin/mongrel_rails:19:in `load’
from /usr/local/bin/mongrel_rails:19
Can you please share some thoughts/experiences…Im not too sure where i
should be looking into.
