Forum: Ruby on Rails dispatch.cgi -> Anonymous modules have no name

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Aafa8848c4b764f080b1b31a51eab73d?d=identicon&s=25 Phlip (Guest)
on 2007-02-04 01:10
(Received via mailing list)
I upgraded to Rails 1.2.1 and deployed to my ISP, who has 1.2.1 ready
and waiting.

The site disappeared into an HTTP 500 error.

So I get into the site, run public/dispatch.cgi or dispatch.rb, and get
this:

# ./dispatch.rb
Status: 400 Bad Request
/usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/dependencies.rb:405:in
`to_constant_name': Anonymous modules have no name to be referenced by
(ArgumentError)
        from
/usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/dependencies.rb:215:in
`qualified_name_for'
        from
/usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/dependencies.rb:477:in
`const_missing'
        from
/usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/dispatcher.rb:117:in
`reset_after_dispatch'
        from
/usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/dispatcher.rb:51:in
`dispatch'
        from ./dispatch.rb:10

Google has a few hits for that, and one of them tells me to do this:

  rake rails:update

Well, that crunched a whole lot of my code (I had been wondering how
to upgrade the site-side code to a new Rails...). But it didn't fix
the problem. I can also reproduce the same problem on my development
workstation.

One big irritation is dispatch.rb:10 doesn't have an anonymous module,
it has Dispatcher, which is imported just a few lines above.

What's going on??

--
  Phlip
  http://c2.com/cgi/wiki?ZeekLand  <-- NOT a blog!!
Aafa8848c4b764f080b1b31a51eab73d?d=identicon&s=25 Phlip (Guest)
on 2007-02-04 05:07
(Received via mailing list)
> # ./dispatch.rb
> Status: 400 Bad Request

We figured it out. dispatch.rb is supposed to do that, but its
permissions
must be exactly 755...
This topic is locked and can not be replied to.