[ANN] Mongrel 0.3.13.3 -- Ruby Licensed Release

Ruby
1

Hello Everyone,

This is the official 0.3.13.3 release of Mongrel.

Mongrel is now released under the Ruby license instead of the LGPL.
I’m hoping this increases the adoption of Mongrel even further and
hopefully I can start pushing to get Mongrel included in Ruby directly.

INSTALL

As usual, you install it with your friendly gem install method of
choice:

gem install mongrel

Or whatever works for you. If the mirror doesn’t update for you fast
enough, you can also grab it with:

gem install mongrel --source=http://mongrel.rubyforge.org/releases/

CHANGES

There was just a small fix to get object count logging with the -B
option working again. Let me know if this blows up for you when you
turn it on.

Also, this release will print the access log to the screen when you’re
not in daemon mode. Let me know if you like or dislike this.

A NEW BUGS MASCOT!

I counted the votes today at about 5pm and it looks like Jake won. You
can see a graph of the results at:

http://mongrel.rubyforge.org/images/bug_votes.png

And take a look at Jake at:

http://www.sonoma-marinfair.org/uglydogvote.shtml

I’ll be contacting Jake’s owner soon to see if I can use him on the
Mongrel site as the mascot for the Bugs page.

–
Zed A. Shaw

http://mongrel.rubyforge.org/
http://www.railsmachine.com/ – Need Mongrel support?

2

Using rails 1.1.4 I get this:

catalog1# mongrel_rails start -C config/mongrel.conf
** Loading settings from config/mongrel.conf (they override command
line).
** Starting Mongrel listening at 69.25.136.52:80
** Loading additional MIME types from config/mime.types
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in
register': undefined methodresolve’ for nil:Mongrel::URIClassifier
(NoMethodError)
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in
uri' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:indebug’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in
debug' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:incloaker_’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in
listener' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:incloaker_’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in
initialize' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:inrun’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in
`run’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235
from /usr/local/bin/mongrel_rails:18

3

I just installed and checked it, but could you shoot me your
mongrel.conf off list so i can look? Might be something related to some
merging wizardry I was doing.

Also, try to uninstall and then reinstall.

4

Oops that wasn’t supposed to go to the list…

5

On 6/30/06, Zed S. [email protected] wrote:

I just installed and checked it, but could you shoot me your
mongrel.conf off list so i can look? Might be something related to some
merging wizardry I was doing.

:daemon: false
:cwd: /tmp/seca/web
:includes:

  • mongrel
    :log_file: log/mongrel.log
    :config_script:
    :debug: false
    :pid_file: log/mongrel.pid
    :group:
    :num_processors: 1024
    :docroot: public
    :user:
    :environment: development
    :host: 69.25.136.52
    :timeout: 0
    :mime_map: config/mime.types
    :port: 80

Also, try to uninstall and then reinstall.

Did that a couple of times didn’t make any difference.

6

Zed S. wrote:

CHANGES

There was just a small fix to get object count logging with the -B
option working again. Let me know if this blows up for you when you
turn it on.

Also, this release will print the access log to the screen when you’re
not in daemon mode. Let me know if you like or dislike this.

For windows users, I suggest adding a start option for the access
logging (on/off).

Ed

7

I demand a recount - Victoria should have won that hands down.

8

On 6/30/06, Zed S. [email protected] wrote:

I just installed and checked it, but could you shoot me your
mongrel.conf off list so i can look? Might be something related to some
merging wizardry I was doing.

Works for me!

9

I demand a recount - Victoria should have won that hands down.

I rigged that election like Castro.

At least now we know that we have a leader who can and will take matters
in
his own hands.

-se

10

I don’t like how errors are intercepted in the new version. Is it
possible to show the whole callstack or at least the line number of
the showed line ?

–
Cheers,
zimbatm

11

On Sat, 2006-07-01 at 08:38 -0500, Larry W. wrote:

I demand a recount - Victoria should have won that hands down.

I rigged that election like Castro.

–
Zed A. Shaw

http://mongrel.rubyforge.org/
http://www.railsmachine.com/ – Need Mongrel support?

12

On 03/07/06, Zed S. [email protected] wrote:

Hey Jonas, I believe they’ve always been stuffed if they’re typical
errors which don’t really seem important (like client closed the
socket). If you can shoot me the error message I can look at how I
might make this optional.

Hi Zed :slight_smile:

Thanks for taking care about my opinion. Yesterday I was building some
Camping extension. For the test, I have a small app that runs over
mongrel using the camping launcher.

Here is an example of error :

Tue Jul 04 09:22:59 CEST 2006: ERROR: wrong number of arguments (3 for
0)

You might admit that it’s hard to guess where that’s happening :slight_smile:

–
Cheers,
zimbatm

13

On Mon, 2006-07-03 at 11:00 +0200, Jonas P. wrote:

I don’t like how errors are intercepted in the new version. Is it
possible to show the whole callstack or at least the line number of
the showed line ?

Hey Jonas, I believe they’ve always been stuffed if they’re typical
errors which don’t really seem important (like client closed the
socket). If you can shoot me the error message I can look at how I
might make this optional.

Zed

14

What worked? I don’t have a custom mongrel.conf but I get the same error
(Ubuntu Server 6.06).

“Aaron K.” [email protected] wrote in
message
news:[email protected]…
On 6/30/06, Zed S. [email protected]
wrote:
I just installed and checked it, but could you shoot me your
mongrel.conf off list so i can look? Might be something related to some
merging wizardry I was doing.

Works for me!

Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails

15

snacktime wrote:

Using rails 1.1.4 I get this:

catalog1# mongrel_rails start -C config/mongrel.conf
** Loading settings from config/mongrel.conf (they override command
line).
** Starting Mongrel listening at 69.25.136.52:80
** Loading additional MIME types from config/mime.types
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in
register': undefined methodresolve’ for nil:Mongrel::URIClassifier
(NoMethodError)
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in
uri' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:indebug’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in
debug' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:incloaker_’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in
listener' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:incloaker_’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in
initialize' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:inrun’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in
`run’
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235
from /usr/local/bin/mongrel_rails:18

I’ve had the same problem on a clean debian installation.

‘gem install mongrel’ showed some messages make wasn’t installed,
however the installation seemed succesfull. I assumed compiling from
source was just optional then.

However it will then fail with the above messages. So just install the
make tools and reinstall the gem and the errors will go away.