Mongrel users - Aug 2006 - Mongrel 0.3.13.4 Pre-Release -- QUERY_STRING Fixed

Hello Everyone,

I just posted another pre-release of Mongrel that fixes a bug which
caused Mongrel to claim it was getting parsing errors because the
QUERY_STRINGs were too long.  In actuality it was shift in the parser
that made empty queries (/test?) become negative.  This is fixed up now.

Here''s the full list of changes:

* It has a couple of fixes for win32, but I still have to apply a few
more patches from Jan Svitok.  This will happen tonight.
* The parser is fixed up to allow at least 10k QUERY_STRINGS.
* There is a new debugging feature.  You can now send any Mongrel
process a USR1 signal and it''ll start dumping the full text and
parameters of any request it considers "bad".  More on this below.
* Tests were enhanced to test for the empty query string.
* The mongrel_cluster work from Bradley Taylor is now part of Mongrel
and will be maintained together so it''ll get released at the same time
as mongrel.
* Timeout errors now include the reason mongrel timed out the thread in
the exception description.

That''s all for now.  Please grab this release with:

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

And verify your application still works.


USR1 BAD CLIENT DEBUGGING

As mentioned above, if you''re seeing BAD CLIENT messages or parsing
errors from Mongrel then you can send your mongrel process a USR1 signal
(unix only) and Mongrel will start dumping the full text and parameters
of what it received before aborting the client.

When you hit a parsing error, really make sure the client is correct,
then if you''re positive it''s right, send me the snippet from
your log
(not all of your log) and I''ll look at it.

When you''re done, then simply hit the processes with another USR1 to
toggle it off.

The downside is I''m not sure of the security implications of this
change, but there''s only a performance hit if the client is bad so
it''s
not that bad to leave it on.


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?

On Wed, 2006-08-16 at 16:53 -0700, Zed Shaw wrote:
> Hello Everyone,
> 
> I just posted another pre-release of Mongrel that fixes a bug which
> caused Mongrel to claim it was getting parsing errors because the
> QUERY_STRINGs were too long.  In actuality it was shift in the parser
> that made empty queries (/test?) become negative.  This is fixed up now.
Correction, NOW the win32 gems are up.

I really gotta either get vmware or wine going for cross builds so I can
automate this.


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?

Are you including the mongrel_cluster code in the mongrel gem, or just
releasing them at the same time?


On 8/16/06, Zed Shaw <zedshaw at zedshaw.com>
wrote:
> On Wed, 2006-08-16 at 16:53 -0700, Zed Shaw wrote:
> > Hello Everyone,
> >
> > I just posted another pre-release of Mongrel that fixes a bug which
> > caused Mongrel to claim it was getting parsing errors because the
> > QUERY_STRINGs were too long.  In actuality it was shift in the parser
> > that made empty queries (/test?) become negative.  This is fixed up
now.
>
> Correction, NOW the win32 gems are up.
>
> I really gotta either get vmware or wine going for cross builds so I can
> automate this.
>
>
> --
> 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
>

Hi Joey:

On Aug 17, 2006, at 9:11 AM, Joey Geiger wrote:
> Are you including the mongrel_cluster code in the mongrel gem, or just
> releasing them at the same time?
>
Its still a different gem, but now the source/gem lives in the  
Mongrel project (instead of railsmachine) and will get built with the  
Mongrel build.

Thanks,
Bradley


------
Rails Optimized Hosting ~ VPS and Dedicated Servers
Simplified Deployment  ~ Services and Software
http://railsmachine.com






-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20060817/c469c556/attachment.html

I''m quite often losing mysql connections during requests, when using  
mongrel.  Doesn''t happen with lighty.
This is on OS X 10.4.6, mysql 4.1.16, and a recent rails.  Is there  
any other useful information I can supply?


On 17 Aug 2006, at 00:53, Zed Shaw wrote:
> Hello Everyone,
>
> I just posted another pre-release of Mongrel that fixes a bug which
> caused Mongrel to claim it was getting parsing errors because the
> QUERY_STRINGs were too long.  In actuality it was shift in the parser
> that made empty queries (/test?) become negative.  This is fixed up  
> now.
>
> Here''s the full list of changes:
>
> * It has a couple of fixes for win32, but I still have to apply a few
> more patches from Jan Svitok.  This will happen tonight.
> * The parser is fixed up to allow at least 10k QUERY_STRINGS.
> * There is a new debugging feature.  You can now send any Mongrel
> process a USR1 signal and it''ll start dumping the full text and
> parameters of any request it considers "bad".  More on this
below.
> * Tests were enhanced to test for the empty query string.
> * The mongrel_cluster work from Bradley Taylor is now part of Mongrel
> and will be maintained together so it''ll get released at the same
time
> as mongrel.
> * Timeout errors now include the reason mongrel timed out the  
> thread in
> the exception description.
>
> That''s all for now.  Please grab this release with:
>
>   gem install mongrel --source=http://mongrel.rubyforge.org/releases/
>
> And verify your application still works.
>
>
> USR1 BAD CLIENT DEBUGGING
>
> As mentioned above, if you''re seeing BAD CLIENT messages or
parsing
> errors from Mongrel then you can send your mongrel process a USR1  
> signal
> (unix only) and Mongrel will start dumping the full text and  
> parameters
> of what it received before aborting the client.
>
> When you hit a parsing error, really make sure the client is correct,
> then if you''re positive it''s right, send me the snippet
from your log
> (not all of your log) and I''ll look at it.
>
> When you''re done, then simply hit the processes with another USR1
to
> toggle it off.
>
> The downside is I''m not sure of the security implications of this
> change, but there''s only a performance hit if the client is bad so
> it''s
> not that bad to leave it on.
>
>
> -- 
> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2114 bytes
Desc: not available
Url :
http://rubyforge.org/pipermail/mongrel-users/attachments/20060818/7d40d830/attachment.bin

On Fri, 2006-08-18 at 10:50 +0100, Jonathan del Strother
wrote:
> I''m quite often losing mysql connections during requests, when
using
> mongrel.  Doesn''t happen with lighty.
> This is on OS X 10.4.6, mysql 4.1.16, and a recent rails.  Is there  
> any other useful information I can supply?
Do you mean FastCGI and lighty?  Because "lighty" doesn''t run
rails.

If so, then I''ll need more information than this.  For example:

1) When does this happen?  
2) Where''s your mysql database?
3) Do you have enough ram?
4) Have you done a packet trace to see what might cause it?  These are
very informative, although it sucks to have to resort to this.
5) What''s the exception you get?
6) Are you opening a bunch of files?
7) Do you have lots of cache() statements in your templates?  Those open
lots of files.
8) Are you using the default rails pure ruby driver or the compiled
driver?

If you can get me more info I might be able to figure it out.  Otherwise
most folks seem to have upgraded to the latest driver and not had this
problem.


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?

Jonathan wrote:
> I really gotta either get vmware or wine going for cross builds so I
>
>>can automate this.
>>    
>>
>
>If it''d help I''ve got a VMware Workstation license sitting
unused I''d
>be happy to give you the key for.  I''m not sure if the EULA
>specifically allows or forbids this, but I know someone at the
>director level over there and I''m comfortable with the ethics after
a
>few of the conversations we''ve had.  Frankly for every version from
2
>on I''ve bought a license for a project, used it for a couple of
months
>maximum, and stuck it on the shelf.
>  
>
VMWare Player and VMWare Server are both "free" (as in beer if not 
libre), and there''s always Fabrice Bellard''s wonderful QEMU +
kqemu.

Anymore, the larger licensing issue is the underlying operating system 
you''re building on, not the virtualization platform.

Having fought to build cross build chains for win32 mozilla plugins 
under cygwin, you really just start to yearn for something native after 
a while. Also, the mozilla win32 tinderbox builds are seem to be running 
from virtual machines from what I can tell (I could very well be wrong).

- Ian C. Blenke <ian at blenke.com> http://ian.blenke.com/

On 9/21/06, Jonathan <rise at knavery.net> wrote:
> On Wed, 16 Aug 2006 17:14:34 -0700 Zed Shaw <zedshaw at zedshaw.com>
wrote:
>
> > Correction, NOW the win32 gems are up.
>
> > I really gotta either get vmware or wine going for cross builds so I
> > can automate this.
>
> If it''d help I''ve got a VMware Workstation license
sitting unused I''d
> be happy to give you the key for.  I''m not sure if the EULA
> specifically allows or forbids this, but I know someone at the
> director level over there and I''m comfortable with the ethics
after a
> few of the conversations we''ve had.  Frankly for every version
from 2
> on I''ve bought a license for a project, used it for a couple of
months
> maximum, and stuck it on the shelf.
>
I mailed Zed about doing a build bot automation farm, so each release
on Linux, Windows or whatever other OS we decide to support could be
automatically checked out and build, later sent result to
mongrel-builds list.

I was thinking on BuildBot (http://buildbot.sourceforge.net), a Python
tool, but too complex for starters.

Maybe Cerberus? (http://cerberus.rubyforge.org/) will be a better option?

Anyway, I have a 1 Windows XP and 1 Windows 2000 unused licenses, or
maybe I could build a Windows PE + VC2003 (which will run and reboot
after 24hs running). That could be run inside VMWare Player or
whatever.

Ok, just an idea.
>
> --
> Jonathan Conway                                                rise at
knavery.net
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>

-- 
Luis Lavena
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 Wed, 16 Aug 2006 17:14:34 -0700 Zed Shaw <zedshaw at zedshaw.com>
wrote:
> Correction, NOW the win32 gems are up.
> I really gotta either get vmware or wine going for cross builds so I
> can automate this.
If it''d help I''ve got a VMware Workstation license sitting
unused I''d
be happy to give you the key for.  I''m not sure if the EULA
specifically allows or forbids this, but I know someone at the
director level over there and I''m comfortable with the ethics after a
few of the conversations we''ve had.  Frankly for every version from 2
on I''ve bought a license for a project, used it for a couple of months
maximum, and stuck it on the shelf.


-- 
Jonathan Conway                                                rise at
knavery.net