Hey Zed, I''m excited for Mongrel 1.0 final! I do have something i ran into before and still is occurring with the new version. When i run into a 500 based error i seem to get header information as output when using mongrel: Status: 500 Internal Server Error Content-Type: text/html <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> I still get the appropriate page as i should, i just get the header info before the page output. I remember you telling me that Rails is sending back the error and page this way, but is there something that can be done so this is not shown? .: Michael :. On 12/20/06, Zed A. Shaw <zedshaw at zedshaw.com> wrote:> > Hello Minions! > > It''s *finally* here. Mongrel 1.0 RC1 for everyone to test, even the win32 > folks. I managed to get everything to build on windows, including > fastthread, and even cleaned up the "releases source": > http://mongrel.rubyforge.org/releases/ so that it should install > cleaner. Win32 will have to try and report problems, as it seems rubygems > is real finicky on win32. > > UNIX Install with: > > $ gem install mongrel --source=http://mongrel.rubyforge.org/releases > > WIN32 Install with: > > $ gem uninstall mongrel > $ gem uninstall gem_plugin > $ gem uninstall fastthread > $ gem install fastthread --source=http://mongrel.rubyforge.org/releases > $ gem install mongrel --source=http://mongrel.rubyforge.org/releases > $ gem install mongrel_service --source> http://mongrel.rubyforge.org/releases > > If you have problems with fastthread then skip it, it''s optional on > Win32. The win32 process is more involved because there hasn''t been a > stable release of it for a while now. That''s why you have to remove > everything you can and then re-install. > > *** Make sure that gem_plugin is version 0.2.2 or the whole thing > dies. *** > > If you have problems installing any of this then add a / to the end of the > source: > > $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > > Yes, that''s retarded, blame the rubygems folks. > > You can view the ChangeLog for this latest release "in the releases": > http://mongrel.rubyforge.org/releases/ChangeLog directory like > normal. This ChangeLog covers everything done since 0.3.18 but it''s in > svn log format so only read it if you''re really uptight. > > And as usual, report any bugs. I''ll be posting instructions on using the > new mongrel_service when I get them from Luis. > > > IT''S RC1 FOR A REASON > > Before you go off installing this thing in your production servers because > you missed the RC1 identifier, remember that RC means "Release > Candidate". Test it to death, use it, report bugs, but only a fool installs > it in mission critical situations without fully testing it. > > OFFICIAL 1.0 (PARTY!) > > If nobody has any problems with this release then it''ll go out on Friday > as the official 1.0 release. > > -- > Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu > http://www.zedshaw.com/ > http://www.awprofessional.com/title/0321483502 -- The Mongrel Book > http://mongrel.rubyforge.org/ > http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help. > _______________________________________________ > 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/20061219/6b35a26a/attachment.html
Hello Minions! It''s *finally* here. Mongrel 1.0 RC1 for everyone to test, even the win32 folks. I managed to get everything to build on windows, including fastthread, and even cleaned up the "releases source":http://mongrel.rubyforge.org/releases/ so that it should install cleaner. Win32 will have to try and report problems, as it seems rubygems is real finicky on win32. UNIX Install with: $ gem install mongrel --source=http://mongrel.rubyforge.org/releases WIN32 Install with: $ gem uninstall mongrel $ gem uninstall gem_plugin $ gem uninstall fastthread $ gem install fastthread --source=http://mongrel.rubyforge.org/releases $ gem install mongrel --source=http://mongrel.rubyforge.org/releases $ gem install mongrel_service --source=http://mongrel.rubyforge.org/releases If you have problems with fastthread then skip it, it''s optional on Win32. The win32 process is more involved because there hasn''t been a stable release of it for a while now. That''s why you have to remove everything you can and then re-install. *** Make sure that gem_plugin is version 0.2.2 or the whole thing dies. *** If you have problems installing any of this then add a / to the end of the source: $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Yes, that''s retarded, blame the rubygems folks. You can view the ChangeLog for this latest release "in the releases":http://mongrel.rubyforge.org/releases/ChangeLog directory like normal. This ChangeLog covers everything done since 0.3.18 but it''s in svn log format so only read it if you''re really uptight. And as usual, report any bugs. I''ll be posting instructions on using the new mongrel_service when I get them from Luis. IT''S RC1 FOR A REASON Before you go off installing this thing in your production servers because you missed the RC1 identifier, remember that RC means "Release Candidate". Test it to death, use it, report bugs, but only a fool installs it in mission critical situations without fully testing it. OFFICIAL 1.0 (PARTY!) If nobody has any problems with this release then it''ll go out on Friday as the official 1.0 release. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/ http://www.awprofessional.com/title/0321483502 -- The Mongrel Book http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.
On Tue, 19 Dec 2006 23:44:03 -0500 "Michael D''Auria" <michael.dauria at gmail.com> wrote:> Hey Zed, > > I''m excited for Mongrel 1.0 final! I do have something i ran into before > and still is occurring with the new version. When i run into a 500 based > error i seem to get header information as output when using mongrel:<snip>> > I still get the appropriate page as i should, i just get the header info > before the page output. I remember you telling me that Rails is sending > back the error and page this way, but is there something that can be done so > this is not shown?Yeah, there''s not much I can do about it right now without changing how rails works and generates its error reports. I tried to crack it again when DHH complained but it just would take way too much rewriting to fix the rewriting. :-) The plan is to tackle that problem and a host of others in later versions. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/ http://www.awprofessional.com/title/0321483502 -- The Mongrel Book http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.
Jonathan del Strother
2006-Dec-20 11:06 UTC
[Mongrel] [ANN] Mongrel 1.0 RC1 Full Win32 Build
On 20 Dec 2006, at 10:02, Zed A. Shaw wrote:> On Tue, 19 Dec 2006 23:44:03 -0500 > "Michael D''Auria" <michael.dauria at gmail.com> wrote: > >> Hey Zed, >> >> I''m excited for Mongrel 1.0 final! I do have something i ran into >> before >> and still is occurring with the new version. When i run into a >> 500 based >> error i seem to get header information as output when using mongrel: > <snip> >> >> I still get the appropriate page as i should, i just get the >> header info >> before the page output. I remember you telling me that Rails is >> sending >> back the error and page this way, but is there something that can >> be done so >> this is not shown? > > Yeah, there''s not much I can do about it right now without changing > how rails works and generates its error reports. I tried to crack > it again when DHH complained but it just would take way too much > rewriting to fix the rewriting. :-) > > The plan is to tackle that problem and a host of others in later > versions.I can''t seem to find any previous discussion on this in the archives - could you give us a quick rundown on what the cause is?
On Wed, 20 Dec 2006 11:06:46 +0000 Jonathan del Strother <maillist at steelskies.com> wrote:> On 20 Dec 2006, at 10:02, Zed A. Shaw wrote: > > > On Tue, 19 Dec 2006 23:44:03 -0500 > > "Michael D''Auria" <michael.dauria at gmail.com> wrote: > > > >> Hey Zed, > >> > >> I''m excited for Mongrel 1.0 final! I do have something i ran into > >> before > >> and still is occurring with the new version. When i run into a > >> 500 based > >> error i seem to get header information as output when using mongrel: > > <snip> > >> > >> I still get the appropriate page as i should, i just get the > >> header info > >> before the page output. I remember you telling me that Rails is > >> sending > >> back the error and page this way, but is there something that can > >> be done so > >> this is not shown? > > > > Yeah, there''s not much I can do about it right now without changing > > how rails works and generates its error reports. I tried to crack > > it again when DHH complained but it just would take way too much > > rewriting to fix the rewriting. :-) > > > > The plan is to tackle that problem and a host of others in later > > versions. > > I can''t seem to find any previous discussion on this in the archives > - could you give us a quick rundown on what the cause is?In order to get headers and the body out Mongrel has to split the IO in two and the case of Rails fake the cgi.rb stuff out with StringIO objects. The problem is that Rails (and other frameworks) like to mix up header and body production so everything is out of order. Since an HTTP response has headers first then the body, I have to collect the headers in one StringIO, the body in a second, and then after Rails is done, send this out later. Everything works fine until Rails has a catastrophic error that causes your "500 page of death". In this case there was already some headers and some body sent out but the error caused Rails to try to "reset" the output and send something totally different, the 500 page. When it does this reset, the headers get screwed up and the body shows some of the headers. Fixing it would require changing how rails does it''s 500 error reporting, or potentially dropping it for an alternative. A simple fix would be to have Rails do a special Mongrel call that tells Mongrel the request failed and Mongrel could produce the 500 page, but then that''d alienate the other methods for deploying rails. Another solution is to rewrite all the carefully tuned Mongrel output processing so that it handles this by buffering everything and writing nothing anywhere until it''s really really final. Since Rails is pushing for 1.2, Mongrel is pushing for 1.0, and having a nasty looking 500 page isn''t the end of the world, I''m just punting until later. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/ http://www.awprofessional.com/title/0321483502 -- The Mongrel Book http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.
On Tue, 2006-12-19 at 22:16 -0800, Zed A. Shaw wrote:> If you have problems with fastthread then skip it, it''s optional on > Win32.But of course, if you all do have problems, please mention them here for my sake so I can address them... -mental -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20061220/538cc2b2/attachment.bin
This morning I updated to ruby 1.8.5-21 (windows oneclick), updated all my gems, and installed mongrel 1.0 (rc1, but 1.0 as per the install instructions) When I start mongrel in RadRails (0.7.2), the console is no longer showing the request that is being made to the mongrel server. With the 0.3.13, when i made a request to http://local:8001/user/dashboard, I would get a message in the log along the lines of (date - time - /user/dashboard - something). Just checking if this is a bug, or working as intended, or if there is something I can set to get this information back? Thanks.