Hi everyone, I''m having a problem starting rails on solaris. I have made the changes suggested in the joyeur article but it doesn''t make any difference. The error is below. Does anyone have any idea? /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in `register'': undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError) from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in `uri'' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:in `debug'' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in `debug'' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:in `cloaker_'' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in `listener'' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:in `cloaker_'' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in `initialize'' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:in `run'' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in `run'' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 from /opt/csw/bin/mongrel_rails:18 Thanks, Carl.
Sorry but I might not be seeing some sort of meta programming hidden around the place because when I look at the URIClassifier is see none of the methods that are described in the documentation: class URIClassifier attr_reader :handler_map # Returns the URIs that have been registered with this classifier so far. # The URIs returned should not be modified as this will cause a memory leak. # You can use this to inspect the contents of the URIClassifier. def uris @handler_map.keys end # Simply does an inspect that looks like a Hash inspect. def inspect @handler_map.inspect end end I''m confused. On 8/10/06, Carl Woodward <cjwoodward at gmail.com> wrote:> Hi everyone, I''m having a problem starting rails on solaris. I have > made the changes suggested in the joyeur article but it doesn''t make > any difference. The error is below. Does anyone have any idea? > > /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in > `register'': undefined method `resolve'' for nil:Mongrel::URIClassifier > (NoMethodError) > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in > `uri'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:in > `debug'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in > `debug'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:in > `cloaker_'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in > `listener'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:in > `cloaker_'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in > `initialize'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:in > `run'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in > `run'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 > from /opt/csw/bin/mongrel_rails:18 > > Thanks, > Carl. >-- Carl Woodward 0412218979 cjwoodward at gmail.com
Sorry guys, I''m an idiot. Its in C. ---------- Forwarded message ---------- From: Carl Woodward <cjwoodward at gmail.com> Date: Aug 10, 2006 5:45 PM Subject: Re: Error on Solaris To: mongrel-users at rubyforge.org Sorry but I might not be seeing some sort of meta programming hidden around the place because when I look at the URIClassifier is see none of the methods that are described in the documentation: class URIClassifier attr_reader :handler_map # Returns the URIs that have been registered with this classifier so far. # The URIs returned should not be modified as this will cause a memory leak. # You can use this to inspect the contents of the URIClassifier. def uris @handler_map.keys end # Simply does an inspect that looks like a Hash inspect. def inspect @handler_map.inspect end end I''m confused. On 8/10/06, Carl Woodward <cjwoodward at gmail.com> wrote:> Hi everyone, I''m having a problem starting rails on solaris. I have > made the changes suggested in the joyeur article but it doesn''t make > any difference. The error is below. Does anyone have any idea? > > /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in > `register'': undefined method `resolve'' for nil:Mongrel::URIClassifier > (NoMethodError) > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in > `uri'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:in > `debug'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in > `debug'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:in > `cloaker_'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in > `listener'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:in > `cloaker_'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in > `initialize'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:in > `run'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in > `run'' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 > from /opt/csw/bin/mongrel_rails:18 > > Thanks, > Carl. >-- Carl Woodward 0412218979 cjwoodward at gmail.com -- Carl Woodward 0412218979 cjwoodward at gmail.com
I believe the usual problem with Mongrel on Solaris is caused by mixing Sun''s C compiler and GCC. Make sure that Ruby and Mongrel are compiled with the same compiler. Scott On 8/10/06, Carl Woodward <cjwoodward at gmail.com> wrote:> Sorry guys, I''m an idiot. Its in C. > > ---------- Forwarded message ---------- > From: Carl Woodward <cjwoodward at gmail.com> > Date: Aug 10, 2006 5:45 PM > Subject: Re: Error on Solaris > To: mongrel-users at rubyforge.org > > > Sorry but I might not be seeing some sort of meta programming hidden > around the place because when I look at the URIClassifier is see none > of the methods that are described in the documentation: > > class URIClassifier > attr_reader :handler_map > > # Returns the URIs that have been registered with this classifier so far. > # The URIs returned should not be modified as this will cause a memory leak. > # You can use this to inspect the contents of the URIClassifier. > def uris > @handler_map.keys > end > > # Simply does an inspect that looks like a Hash inspect. > def inspect > @handler_map.inspect > end > end > > I''m confused. > > On 8/10/06, Carl Woodward <cjwoodward at gmail.com> wrote: > > Hi everyone, I''m having a problem starting rails on solaris. I have > > made the changes suggested in the joyeur article but it doesn''t make > > any difference. The error is below. Does anyone have any idea? > > > > /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in > > `register'': undefined method `resolve'' for nil:Mongrel::URIClassifier > > (NoMethodError) > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in > > `uri'' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:in > > `debug'' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in > > `debug'' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:in > > `cloaker_'' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in > > `listener'' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:in > > `cloaker_'' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in > > `initialize'' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:in > > `run'' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in > > `run'' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 > > from /opt/csw/bin/mongrel_rails:18 > > > > Thanks, > > Carl. > > > > > -- > Carl Woodward > 0412218979 > cjwoodward at gmail.com > > > -- > Carl Woodward > 0412218979 > cjwoodward at gmail.com > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >
Thanks for that. On 8/10/06, Scott Laird <scott at sigkill.org> wrote:> I believe the usual problem with Mongrel on Solaris is caused by > mixing Sun''s C compiler and GCC. Make sure that Ruby and Mongrel are > compiled with the same compiler. > > > Scott > > On 8/10/06, Carl Woodward <cjwoodward at gmail.com> wrote: > > Sorry guys, I''m an idiot. Its in C. > > > > ---------- Forwarded message ---------- > > From: Carl Woodward <cjwoodward at gmail.com> > > Date: Aug 10, 2006 5:45 PM > > Subject: Re: Error on Solaris > > To: mongrel-users at rubyforge.org > > > > > > Sorry but I might not be seeing some sort of meta programming hidden > > around the place because when I look at the URIClassifier is see none > > of the methods that are described in the documentation: > > > > class URIClassifier > > attr_reader :handler_map > > > > # Returns the URIs that have been registered with this classifier so far. > > # The URIs returned should not be modified as this will cause a memory leak. > > # You can use this to inspect the contents of the URIClassifier. > > def uris > > @handler_map.keys > > end > > > > # Simply does an inspect that looks like a Hash inspect. > > def inspect > > @handler_map.inspect > > end > > end > > > > I''m confused. > > > > On 8/10/06, Carl Woodward <cjwoodward at gmail.com> wrote: > > > Hi everyone, I''m having a problem starting rails on solaris. I have > > > made the changes suggested in the joyeur article but it doesn''t make > > > any difference. The error is below. Does anyone have any idea? > > > > > > /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in > > > `register'': undefined method `resolve'' for nil:Mongrel::URIClassifier > > > (NoMethodError) > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in > > > `uri'' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:in > > > `debug'' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in > > > `debug'' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:in > > > `cloaker_'' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in > > > `listener'' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:in > > > `cloaker_'' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in > > > `initialize'' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:in > > > `run'' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in > > > `run'' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 > > > from /opt/csw/bin/mongrel_rails:18 > > > > > > Thanks, > > > Carl. > > > > > > > > > -- > > Carl Woodward > > 0412218979 > > cjwoodward at gmail.com > > > > > > -- > > Carl Woodward > > 0412218979 > > cjwoodward at gmail.com > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-- Carl Woodward 0412218979 cjwoodward at gmail.com
On Thu, 2006-08-10 at 17:53 +1000, Carl Woodward wrote:> Sorry guys, I''m an idiot. Its in C.Also, try installing the pre-release as I''ve (hopefully) fixed things that cause the Sun C compiler to blow up (because they couldn''t read a spec if it was filled with porn). gem install mongrel --source=http://mongrel.rubyforge.org/releases/ -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?
When installing the 0.3.13.4 pre-release on Solaris I got the same error as on the Joyent blog: http://joyeur.com/2006/07/21/a-mongrel-endorsement-and-a-manual-fix-for-installing-mongrel-on-solaris-1011 Fix #1 there got it working and so far mongrel has been working. Thanks, Justin On 8/10/06, Zed Shaw <zedshaw at zedshaw.com> wrote:> > On Thu, 2006-08-10 at 17:53 +1000, Carl Woodward wrote: > > Sorry guys, I''m an idiot. Its in C. > > Also, try installing the pre-release as I''ve (hopefully) fixed things > that cause the Sun C compiler to blow up (because they couldn''t read a > spec if it was filled with porn). > > > gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-- Justin Chen Two-Bit Operation LLC http://www.twobitoperation.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060811/47cb293c/attachment.html
On Fri, 2006-08-11 at 12:32 -0500, Justin Chen wrote:> When installing the 0.3.13.4 pre-release on Solaris I got the same > error as on the Joyent blog: > http://joyeur.com/2006/07/21/a-mongrel-endorsement-and-a-manual-fix-for-installing-mongrel-on-solaris-1011 > > Fix #1 there got it working and so far mongrel has been working.Yeah, without their C compiler I doubt I could fix it in the source. Looks like it''s more than just stray ; characters causing this. Just do what his instructions say so that you''re using GCC (but I believe you have to make sure your ruby is compiled with that as well). -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?
Zed Shaw writes:> On Thu, 2006-08-10 at 17:53 +1000, Carl Woodward wrote: >> Sorry guys, I''m an idiot. Its in C. > > Also, try installing the pre-release as I''ve (hopefully) fixed things > that cause the Sun C compiler to blow up (because they couldn''t read a > spec if it was filled with porn). > > > gem install mongrel --source=http://mongrel.rubyforge.org/releases/Sun C does not blow up, it emits some warnings. The warnings aren''t errors, they are warnings. That''s what the word "warning" at the beginning of those lines means. Empty declarations really are illegal in C99. They really are syntax errors. I wonder where you differ from Sun on the spec. I''d like to see your derivation of '';'' from the grammar in Annex A.2.2. If anyone is inordinately bothered by the warnings, they can get rid of them by adding -xc99=%none to their compiler flags. Then an empty decl will be converted to ''int;'' like C89 and GCC do. Better to fix the bug (as has already been done) however. Granted, using the word "error" in the body of a warning is confusing to people who miss the word "warning" immediately preceding it. That''s why I used phrases like "Mostly just FYI", and "I get some warnings" in my bug report. The single remaining warning is also a warning. GCC will also emit this warning, but they hide this feature behind -Wunreachable-code. Try it (3.4.3 here) and you will learn why they hide it. It flags over 100 lines. I removed the crazy #line directives (1,106,24,110,26,114?) from the generated C file (0.3.13.3) and compiled to find that the warning is on line 297. That line really is unreachable. The warning really should be there. Having unreachable lines isn''t exactly a crime for a parser generator. If anyone is inordinately bothered by the warning they can add -erroff=E_STATEMENT_NOT_REACHED to their compiler flags. Mongrel runs great when compiled with Sun C! So does Ruby. Maybe I should have noted in my bug report that I was using it with great success, would love to buy you a beverage, etc. GCC is periodically broken in horrible ways on SPARC. They even managed to break printf("%.2lf", x). I haven''t caught up on whether they ever succeeded in correctly implementing the standard calling convention. Steve
kigsteronline at mac.com
2006-Aug-18 01:34 UTC
[Mongrel] error starting mongrel: undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError)
$ mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000 /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/ mongrel.rb:666:in `register'': undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError) from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel.rb:850:in `uri'' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel.rb:1018:in `debug'' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel.rb:1016:in `debug'' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/bin/mongrel_rails:108:in `cloaker_'' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel.rb:832:in `listener'' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/bin/mongrel_rails:96:in `cloaker_'' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel.rb:750:in `initialize'' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/bin/mongrel_rails:83:in `run'' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel/command.rb:199:in `run'' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/bin/mongrel_rails:235 from /usr/local/ruby/bin/mongrel_rails:18 What am I missing? I installed it using "sudo gem install mongrel --include-dependencies" Thanks! Konstantin
kigsteronline at mac.com
2006-Aug-18 01:45 UTC
[Mongrel] Avoiding sudo when starting/stopping mongrel_cluster
Hello! I apologize for newbie questions, but I am setting up capistrano and mongrel_cluster for the first time on Linux RS2. During "cap cold_deploy" from a development machine to a production box, I see the following: ** transaction: commit * executing task restart * executing task restart_mongrel_cluster * executing task stop_mongrel_cluster * executing "sudo mongrel_rails cluster::stop -C /data/apps/blurby/ current/config/mongrel_cluster.yml" I am running remote user as special application user, not root. Since mongrel cluster does not need privileged port, I would prefer if I didn''t need to use SUDO to start/stop the cluster. Is there a way to remove "sudo" from the above command and run cluster as application user? Thanks for any input, Konstantin
Nick Sieger
2006-Aug-18 01:49 UTC
[Mongrel] Avoiding sudo when starting/stopping mongrel_cluster
On 8/17/06, kigsteronline at mac.com <kigsteronline at mac.com> wrote:> > Is there a way to remove "sudo" from the above command and run > cluster as application user?"set :use_sudo, false" in your cap recipes file. Cheers, /Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060817/47f6dc00/attachment.html
Nick Sieger
2006-Aug-18 01:52 UTC
[Mongrel] error starting mongrel: undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError)
On 8/17/06, kigsteronline at mac.com <kigsteronline at mac.com> wrote:> > $ mongrel_rails start > ** Starting Mongrel listening at 0.0.0.0:3000 > /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/ > mongrel.rb:666:in `register'': undefined method `resolve'' for > nil:Mongrel::URIClassifier (NoMethodError) > > What am I missing? > > I installed it using "sudo gem install mongrel --include-dependencies"Go back and install again and watch for errors. The most likely culprit is that the /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/mongrel- 0.3.13.3/ext/http11/http11.so didn''t get moved to /usr/local/ruby-1.8.4 /lib/ruby/gems/1.8/gems /mongrel-0.3.13.3/lib/http11.so during the installation process. HTH, /Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060817/61ce1e50/attachment.html
Ed Hickey
2006-Aug-18 14:09 UTC
[Mongrel] error starting mongrel: undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError)
i believe i had this problem and it was because i didn''t install gcc. make sure you have the gcc package installed, uninstall mogrel, install mongrel and try again. ed On 8/17/06, Nick Sieger <nicksieger at gmail.com> wrote:> > On 8/17/06, kigsteronline at mac.com <kigsteronline at mac.com> wrote: > > > $ mongrel_rails start > ** Starting Mongrel listening at 0.0.0.0:3000 > /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/ > mongrel.rb:666:in `register'': undefined method `resolve'' for > nil:Mongrel::URIClassifier (NoMethodError) > > What am I missing? > > I installed it using "sudo gem install mongrel --include-dependencies" > > Go back and install again and watch for errors. The most likely culprit > is that the /usr/local/ruby- 1.8.4/lib/ruby/gems/1.8/gems/mongrel- > 0.3.13.3/ext/http11/http11.so didn''t get moved to /usr/local/ruby-1.8.4 > /lib/ruby/gems/1.8/gems > /mongrel- 0.3.13.3/lib/http11.so during the installation process. > > HTH, > /Nick > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060818/5f8b25da/attachment.html
kigsteronline at mac.com
2006-Aug-18 17:54 UTC
[Mongrel] error starting mongrel: undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError)
This was some weird permissions problem... I''ve rebuilt everything from scratch and made sure that /usr/local/ruby was readable by all users, and now it''s all working. Thanks for the help! K On Aug 18, 2006, at 7:09 AM, Ed Hickey wrote:> i believe i had this problem and it was because i didn''t install > gcc. make sure you have the gcc package installed, uninstall > mogrel, install mongrel and try again. > > ed > > On 8/17/06, Nick Sieger <nicksieger at gmail.com> wrote: > On 8/17/06, kigsteronline at mac.com < kigsteronline at mac.com> wrote: > $ mongrel_rails start > ** Starting Mongrel listening at 0.0.0.0:3000 > /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/ > mongrel.rb:666:in `register'': undefined method `resolve'' for > nil:Mongrel::URIClassifier (NoMethodError) > > What am I missing? > > I installed it using "sudo gem install mongrel --include-dependencies" > > Go back and install again and watch for errors. T he most likely > culprit is that the /usr/local/ruby- 1.8.4/lib/ruby/gems/1.8/gems/ > mongrel-0.3.13.3/ext/http11/http11.so didn''t get moved to /usr/ > local/ruby- 1.8.4/lib/ruby/gems/1.8/gems > /mongrel- 0.3.13.3/lib/http11.so during the installation process. > > HTH, > /Nick > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060818/cf412578/attachment.html
snacktime
2006-Aug-18 17:55 UTC
[Mongrel] error starting mongrel: undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError)
There is something wrong with that version of mongrel. I had this exact same issue. Downgrade it work fine, upgrade to pre release it work fine. stay at 0.3.13.3 I get that error. clean out everything try again same result. That was on freebsd 6.1. Tried it on two different 6.1 servers same result.
Zed Shaw
2006-Aug-18 19:54 UTC
[Mongrel] error starting mongrel: undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError)
On Fri, 2006-08-18 at 09:09 -0500, Ed Hickey wrote:> i believe i had this problem and it was because i didn''t install gcc. > make sure you have the gcc package installed, uninstall mogrel, > install mongrel and try again.Yep, the ever present "gems installs even if nothing builds" problem. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?