Hi all, Ruby 1.8.4 Rails 1.1.2 Mongrel 0.3.12 I''m seeing this output from the Mongrel server: Client closed socket requesting file C:/eclipse/workspace/dslscheduler/public/javascripts/prototype.js: Invalid argument It seems to be harmless, but I''m curious as to what''s causing it. Any ideas? Thanks, Dan
Hi Dan, I added those reports for people who have crappy proxy servers that keep closing the connections. Lighttpd does this quite frequently for no apparent reason. I''m really starting to not like lighttpd. Basically, if the file is being served to the client and the client closes the connection mid-stream then it''s usually harmless. It means someone just hit the stop button on their browser. But if you''re seeing a ton of these then there''s probably something wrong, especially if it''s to the same file. Take a look at your proxy server settings and consider blocking remote clients that do this often. Another thing is that, if you have your fronting web server configured right so it deals with the static files, then you should see these for static files at all. This means that Mongrel is actually serving the file when really a web server like apache or litespeed should be doing it. I''ll be most likely toning down the logging once it seems that the parser is doing good and people think these closed connection warnings are not needed. Let me know if you also see BAD CLIENT dumps with requests that should be legitimate. Also, there''s a pre-release up that dumps more information to help track this stuff down like the IP address of the remote client and the time. You can install it with gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Zed On 4/21/06 12:25 PM, "Berger, Daniel" <Daniel.Berger at qwest.com> wrote:> Hi all, > > Ruby 1.8.4 > Rails 1.1.2 > Mongrel 0.3.12 > > I''m seeing this output from the Mongrel server: > > Client closed socket requesting file > C:/eclipse/workspace/dslscheduler/public/javascripts/prototype.js: > Invalid argument > > It seems to be harmless, but I''m curious as to what''s causing it. Any > ideas? > > Thanks, > > Dan > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users
Thanks for the reply Zed. However, this is just a local server for development. There''s no proxy, no frontend web server for serving static content, and no external client (at least, that I know of). Just me futzing around in IE on localhost to make sure everything looks ok. Running the same Rails app on my Solaris box (again, a local dev copy) does not seem to produce this warning. I thought it was a Windows specific issue of some sort. I''ll try the prerelease and see if I can get any further information. Thanks, Dan Zed Shaw wrote:> Hi Dan, > > I added those reports for people who have crappy proxy servers that keep > closing the connections. Lighttpd does this quite frequently for no > apparent reason. I''m really starting to not like lighttpd. > > Basically, if the file is being served to the client and the client closes > the connection mid-stream then it''s usually harmless. It means someone just > hit the stop button on their browser. > > But if you''re seeing a ton of these then there''s probably something wrong, > especially if it''s to the same file. Take a look at your proxy server > settings and consider blocking remote clients that do this often. > > Another thing is that, if you have your fronting web server configured right > so it deals with the static files, then you should see these for static > files at all. This means that Mongrel is actually serving the file when > really a web server like apache or litespeed should be doing it. > > I''ll be most likely toning down the logging once it seems that the parser is > doing good and people think these closed connection warnings are not needed. > Let me know if you also see BAD CLIENT dumps with requests that should be > legitimate. > > Also, there''s a pre-release up that dumps more information to help track > this stuff down like the IP address of the remote client and the time. You > can install it with gem install mongrel > --source=http://mongrel.rubyforge.org/releases/ > > > Zed > > > On 4/21/06 12:25 PM, "Berger, Daniel" <Daniel.Berger at qwest.com> wrote: > >> Hi all, >> >> Ruby 1.8.4 >> Rails 1.1.2 >> Mongrel 0.3.12 >> >> I''m seeing this output from the Mongrel server: >> >> Client closed socket requesting file >> C:/eclipse/workspace/dslscheduler/public/javascripts/prototype.js: >> Invalid argument >> >> It seems to be harmless, but I''m curious as to what''s causing it. Any >> ideas? >> >> Thanks, >> >> Dan >> >> _______________________________________________ >> 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
On 4/21/06 2:13 PM, "Zed Shaw" <zedshaw at zedshaw.com> wrote:> Another thing is that, if you have your fronting web server configured right > so it deals with the static files, then you should see these for static > files at all. This means that Mongrel is actually serving the file when > really a web server like apache or litespeed should be doing it.Correction: "then you should *NOT* see these for static file at all." Zed
> -----Original Message----- > From: mongrel-users-bounces at rubyforge.org > [mailto:mongrel-users-bounces at rubyforge.org] On Behalf Of Zed Shaw > Sent: Friday, April 21, 2006 12:13 PM > To: mongrel-users at rubyforge.org > Subject: Re: [Mongrel] "Client closed socket" spewage> > Also, there''s a pre-release up that dumps more information to > help track this stuff down like the IP address of the remote > client and the time. You can install it with gem install > mongrel --source=http://mongrel.rubyforge.org/releases/I seem to be having some problems: C:\>gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Attempting local installation of ''mongrel'' Local gem file not found: mongrel*.gem Attempting remote installation of ''mongrel'' Install required dependency daemons? [Yn] Y ERROR: While executing gem ... (Gem::GemNotFoundException) Could not find daemons (>= 0.4.2) in the repository Gem issue? I didn''t think Windows had daemons as a prereq. Regards, Dan
On 4/21/06, Berger, Daniel <Daniel.Berger at qwest.com> wrote:> > -----Original Message----- > > From: mongrel-users-bounces at rubyforge.org > > [mailto:mongrel-users-bounces at rubyforge.org] On Behalf Of Zed Shaw > > Sent: Friday, April 21, 2006 12:13 PM > > To: mongrel-users at rubyforge.org > > Subject: Re: [Mongrel] "Client closed socket" spewage > > > > > Also, there''s a pre-release up that dumps more information to > > help track this stuff down like the IP address of the remote > > client and the time. You can install it with gem install > > mongrel --source=http://mongrel.rubyforge.org/releases/ > > I seem to be having some problems: > > C:\>gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > Attempting local installation of ''mongrel'' > Local gem file not found: mongrel*.gem > Attempting remote installation of ''mongrel'' > Install required dependency daemons? [Yn] Y > ERROR: While executing gem ... (Gem::GemNotFoundException) > Could not find daemons (>= 0.4.2) in the repository > > Gem issue? I didn''t think Windows had daemons as a prereq. >The fun of serving beta gems. You might have better luck running C:\> gem install mongrel then C:\> gem update mongrel --source=http://mongrel.rubyforge.org/releases that way all the dependencies are installed. -- "Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity." ?General George S. Patton
On 4/21/06, Bryan Soto <bryan.a.soto at gmail.com> wrote:> > I seem to be having some problems: > > > > C:\>gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > > Attempting local installation of ''mongrel'' > > Local gem file not found: mongrel*.gem > > Attempting remote installation of ''mongrel'' > > Install required dependency daemons? [Yn] Y > > ERROR: While executing gem ... (Gem::GemNotFoundException) > > Could not find daemons (>= 0.4.2) in the repository > > > > Gem issue? I didn''t think Windows had daemons as a prereq. > > > > The fun of serving beta gems. You might have better luck running > C:\> gem install mongrel > then > C:\> gem update mongrel --source=http://mongrel.rubyforge.org/releases > that way all the dependencies are installed. >And follow that with a C:\> gem cleanup mongrel Hope that helps, Bryan -- "Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity." ?General George S. Patton
Ah, see what happens when you don''t test? Thanks Brian for clueing Dan in. Dan, let me know how this works. Zed On 4/21/06 3:13 PM, "Berger, Daniel" <Daniel.Berger at qwest.com> wrote:>> -----Original Message----- >> From: mongrel-users-bounces at rubyforge.org >> [mailto:mongrel-users-bounces at rubyforge.org] On Behalf Of Zed Shaw >> Sent: Friday, April 21, 2006 12:13 PM >> To: mongrel-users at rubyforge.org >> Subject: Re: [Mongrel] "Client closed socket" spewage > >> >> Also, there''s a pre-release up that dumps more information to >> help track this stuff down like the IP address of the remote >> client and the time. You can install it with gem install >> mongrel --source=http://mongrel.rubyforge.org/releases/ > > I seem to be having some problems: > > C:\>gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > Attempting local installation of ''mongrel'' > Local gem file not found: mongrel*.gem > Attempting remote installation of ''mongrel'' > Install required dependency daemons? [Yn] Y > ERROR: While executing gem ... (Gem::GemNotFoundException) > Could not find daemons (>= 0.4.2) in the repository > > Gem issue? I didn''t think Windows had daemons as a prereq. > > Regards, > > Dan > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users
On 4/21/06, Zed Shaw <zedshaw at zedshaw.com> wrote:> Ah, see what happens when you don''t test? Thanks Brian for clueing Dan in. > Dan, let me know how this works.Zed, beta gems are *nix only, right? Thats why the dependencies are broken... Let me know the release schedule and the todo so we could work better, with test on the win32 side of mongrel. Luis
Yeah, beta gems tend to only release for the posix side of things because, ehem, I''m a lazy bastard. I''ll do up a better release. I''ll get ahold of you soon about cleaning up the win32 side of things so that everything is nice and unified into one simple script. Zed On 4/21/06 7:17 PM, "Luis Lavena" <luislavena at gmail.com> wrote:> On 4/21/06, Zed Shaw <zedshaw at zedshaw.com> wrote: >> Ah, see what happens when you don''t test? Thanks Brian for clueing Dan in. >> Dan, let me know how this works. > > Zed, beta gems are *nix only, right? Thats why the dependencies are broken... > > Let me know the release schedule and the todo so we could work better, > with test on the win32 side of mongrel. > > Luis > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users
Dan, sorry but I totally forgot that you''re on win32. Not a good brain day for me. Let me test this all out tonight and get back to you. I''ll post beta gems that you can get from the win32 side too. Zed On 4/21/06 2:25 PM, "Daniel Berger" <Daniel.Berger at qwest.com> wrote: <snip>> > I''ll try the prerelease and see if I can get any further information. > > Thanks, >