From daniel at infoex.com Fri Oct 10 06:10:15 2008 From: daniel at infoex.com (Daniel Jabbour) Date: Fri, 10 Oct 2008 06:10:15 -0400 Subject: [Swiftiply-users] All swiftiplied mongrels crashe randomly Message-ID: <75BA1417-F363-4F28-AA72-0CF1A9F43B70@infoex.com> Hi, I am running a swiftiply instance connecting to 20 mongrel processes across two machines (separate from the swiftiply server). Randomly they all crash with the following error: /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:54:in `escape': can't convert nil into String (TypeError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/ configurator.rb:303:in `join' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/ configurator.rb:303:in `join' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/ configurator.rb:303:in `each' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/ configurator.rb:303:in `join' from /usr/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/ mongrel_rails:145:in `run' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/ command.rb:212:in `run' from /usr/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/ mongrel_rails:252 from /usr/bin/mongrel_rails:19:in `load' from /usr/bin/mongrel_rails:19 I noticed a few (~3) google results that might relate, and it seems to be related to a null PATH_INFO variable in mongrel. What is going on? Is the swiftiply mongrel always so unstable? Or is there something I can change about my config? Details below: OS: CentOS 5.2 Arch: x86_64 Swiftiply: 0.6.1.1 Mongrel: 1.1.5 Rails: 2.1.0 Ruby 1.8.6 My swiftiply config looks as follows: cluster_address: HOSTNAME cluster_port: 80 daemonize: true epoll: true epoll_descriptors: 8192 map: - incoming: - HOSTNAME outgoing: 192.168.1.25:30000 default: true redeployable: true I am starting mongrel like such: /usr/bin/ruby /usr/bin/mongrel_rails start -d -a swiftiplyhost -p 30000 -e production -c /var/www/rails -P log/mongrel0.pid -- Daniel Jabbour Executive Vice President of Systems Architecture Office: (646) 778-3789 x707 daniel at infoex.com InfoExchange, Inc. From info at mwmediasolutions.de Tue Oct 14 03:32:14 2008 From: info at mwmediasolutions.de (info mwmediasolutions) Date: Tue, 14 Oct 2008 09:32:14 +0200 Subject: [Swiftiply-users] All swiftiplied mongrels crashe randomly In-Reply-To: <75BA1417-F363-4F28-AA72-0CF1A9F43B70@infoex.com> References: <75BA1417-F363-4F28-AA72-0CF1A9F43B70@infoex.com> Message-ID: <48F44AFE.5070509@mwmediasolutions.de> Hi Daniel, we got the same problems as described in in this group in august. But we could not find a fix for this errors. Did you try to contact Kirk Haynes from http://swiftiply.swiftcore.org ? I tried but got no answers. Sometimes it works over months without a problem. But after restarting the swiftply the error appears again. Would be great to work together to fix this. Greetings, Marc Daniel Jabbour schrieb: > Hi, > > I am running a swiftiply instance connecting to 20 mongrel processes > across two machines (separate from the swiftiply server). Randomly > they all crash with the following error: > > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:54:in > `escape': can't convert nil into String (TypeError) > from > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:303:in > `join' > from > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:303:in > `join' > from > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:303:in > `each' > from > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:303:in > `join' > from > /usr/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/mongrel_rails:145:in > `run' > from > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/command.rb:212:in > `run' > from > /usr/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/mongrel_rails:252 > from /usr/bin/mongrel_rails:19:in `load' > from /usr/bin/mongrel_rails:19 > > I noticed a few (~3) google results that might relate, and it seems to > be related to a null PATH_INFO variable in mongrel. What is going on? > Is the swiftiply mongrel always so unstable? Or is there something I > can change about my config? Details below: > > OS: CentOS 5.2 > Arch: x86_64 > Swiftiply: 0.6.1.1 > Mongrel: 1.1.5 > Rails: 2.1.0 > Ruby 1.8.6 > > My swiftiply config looks as follows: > > cluster_address: HOSTNAME > cluster_port: 80 > daemonize: true > epoll: true > epoll_descriptors: 8192 > map: > - incoming: > - HOSTNAME > outgoing: 192.168.1.25:30000 > default: true > redeployable: true > > I am starting mongrel like such: > /usr/bin/ruby /usr/bin/mongrel_rails start -d -a swiftiplyhost -p > 30000 -e production -c /var/www/rails -P log/mongrel0.pid > > -- > Daniel Jabbour > Executive Vice President of Systems Architecture > Office: (646) 778-3789 x707 > daniel at infoex.com > InfoExchange, Inc. > > _______________________________________________ > Swiftiply-users mailing list > Swiftiply-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/swiftiply-users -- ______________________________________________________________________ Marc Willwacher (Gesch?ftsf?hrung/Development) mwmediasolutions Schillerstra?e 20 - 15517 F?rstenwalde Tel: 03361 757417 - Mobil: 0176 23388854 www.mwmediasolutions.de - willwacher at mwmediasolutions.de From wyhaines at gmail.com Tue Oct 14 08:49:00 2008 From: wyhaines at gmail.com (Kirk Haines) Date: Tue, 14 Oct 2008 06:49:00 -0600 Subject: [Swiftiply-users] All swiftiplied mongrels crashe randomly In-Reply-To: <48F44AFE.5070509@mwmediasolutions.de> References: <75BA1417-F363-4F28-AA72-0CF1A9F43B70@infoex.com> <48F44AFE.5070509@mwmediasolutions.de> Message-ID: On Tue, Oct 14, 2008 at 1:32 AM, info mwmediasolutions < info at mwmediasolutions.de> wrote: > Hi Daniel, > > we got the same problems as described in in this group in august. > But we could not find a fix for this errors. > > It was supposed to be a fixed bug (i.e. it's fixed in my production deployments), but somewhere that commit got lost or missed in the repository. I have fixed the bug itself, and am adding a test case to the tests to make sure it is a covered condition, then the fixes will be pushed up to github. Thanks, Kirk Haines -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at mwmediasolutions.de Tue Oct 14 09:07:13 2008 From: info at mwmediasolutions.de (info mwmediasolutions) Date: Tue, 14 Oct 2008 15:07:13 +0200 Subject: [Swiftiply-users] All swiftiplied mongrels crashe randomly In-Reply-To: References: <75BA1417-F363-4F28-AA72-0CF1A9F43B70@infoex.com> <48F44AFE.5070509@mwmediasolutions.de> Message-ID: <48F49981.9070709@mwmediasolutions.de> Hi Kirk, thank you for your answer. I installed swiftiply by using "|gem install swiftiply|". It would be very nice if you could tell me what to do to install the fixed version and when it will be available? Many thanks, Marc Kirk Haines schrieb: > On Tue, Oct 14, 2008 at 1:32 AM, info mwmediasolutions < > info at mwmediasolutions.de> wrote: > > >> Hi Daniel, >> >> we got the same problems as described in in this group in august. >> But we could not find a fix for this errors. >> >> >> > It was supposed to be a fixed bug (i.e. it's fixed in my production > deployments), but somewhere that commit got lost or missed in the > repository. I have fixed the bug itself, and am adding a test case to the > tests to make sure it is a covered condition, then the fixes will be pushed > up to github. > > > Thanks, > > Kirk Haines > > -- ______________________________________________________________________ Marc Willwacher (Gesch?ftsf?hrung/Development) mwmediasolutions Schillerstra?e 20 - 15517 F?rstenwalde Tel: 03361 757417 - Mobil: 0176 23388854 www.mwmediasolutions.de - willwacher at mwmediasolutions.de From daniel at infoex.com Tue Oct 14 10:53:20 2008 From: daniel at infoex.com (Daniel Jabbour) Date: Tue, 14 Oct 2008 10:53:20 -0400 Subject: [Swiftiply-users] All swiftiplied mongrels crashe randomly In-Reply-To: <48F49981.9070709@mwmediasolutions.de> References: <75BA1417-F363-4F28-AA72-0CF1A9F43B70@infoex.com> <48F44AFE.5070509@mwmediasolutions.de> <48F49981.9070709@mwmediasolutions.de> Message-ID: Marc, 1. gem uninstall swiftiply 2. download from git hub (git clone 3. ruby setup.rb 4. ruby setup.rb test Please note, in recent versions of swiftiply, you muse use swiftiplied_mongrel_rails instead of mongrel_rails. -- Daniel Jabbour Executive Vice President of Systems Architecture Office: (646) 778-3789 x707 daniel at infoex.com InfoExchange, Inc. On Oct 14, 2008, at 9:07 AM, info mwmediasolutions wrote: > Hi Kirk, > > thank you for your answer. > > I installed swiftiply by using "|gem install swiftiply|". > > It would be very nice if you could tell me what to do to install the > fixed version and when it will be available? > > Many thanks, > Marc > > > > Kirk Haines schrieb: >> On Tue, Oct 14, 2008 at 1:32 AM, info mwmediasolutions < >> info at mwmediasolutions.de> wrote: >> >> >>> Hi Daniel, >>> >>> we got the same problems as described in in this group in august. >>> But we could not find a fix for this errors. >>> >>> >>> >> It was supposed to be a fixed bug (i.e. it's fixed in my production >> deployments), but somewhere that commit got lost or missed in the >> repository. I have fixed the bug itself, and am adding a test case >> to the >> tests to make sure it is a covered condition, then the fixes will >> be pushed >> up to github. >> >> >> Thanks, >> >> Kirk Haines >> >> > > -- > ______________________________________________________________________ > Marc Willwacher (Gesch?ftsf?hrung/Development) > mwmediasolutions > Schillerstra?e 20 - 15517 F?rstenwalde > Tel: 03361 757417 - Mobil: 0176 23388854 > www.mwmediasolutions.de - willwacher at mwmediasolutions.de > > _______________________________________________ > Swiftiply-users mailing list > Swiftiply-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/swiftiply-users From info at mwmediasolutions.de Fri Oct 17 04:11:10 2008 From: info at mwmediasolutions.de (info mwmediasolutions) Date: Fri, 17 Oct 2008 10:11:10 +0200 Subject: [Swiftiply-users] All swiftiplied mongrels crashe randomly In-Reply-To: References: <75BA1417-F363-4F28-AA72-0CF1A9F43B70@infoex.com> <48F44AFE.5070509@mwmediasolutions.de> <48F49981.9070709@mwmediasolutions.de> Message-ID: <48F8489E.9040602@mwmediasolutions.de> Hi Daniel , hi Kirk thank you very much for your help. I will try to do this installation. But I got a question on this. What can I do if it throws an error or doesn't work good for me? Is there a simple method to switch back to the gem version to make the server run. So, how can i deinstall? And how can I do an update with coming versions. Will the newer versions override the installation I did with "ruby setup.rb" Many thanks, Marc Daniel Jabbour schrieb: > Marc, > > 1. gem uninstall swiftiply > 2. download from git hub (git clone > 3. ruby setup.rb > 4. ruby setup.rb test > > Please note, in recent versions of swiftiply, you muse use > swiftiplied_mongrel_rails instead of mongrel_rails. > > -- > Daniel Jabbour > Executive Vice President of Systems Architecture > Office: (646) 778-3789 x707 > daniel at infoex.com > InfoExchange, Inc. > > On Oct 14, 2008, at 9:07 AM, info mwmediasolutions wrote: > >> Hi Kirk, >> >> thank you for your answer. >> >> I installed swiftiply by using "|gem install swiftiply|". >> >> It would be very nice if you could tell me what to do to install the >> fixed version and when it will be available? >> >> Many thanks, >> Marc >> >> >> >> Kirk Haines schrieb: >>> On Tue, Oct 14, 2008 at 1:32 AM, info mwmediasolutions < >>> info at mwmediasolutions.de> wrote: >>> >>> >>>> Hi Daniel, >>>> >>>> we got the same problems as described in in this group in august. >>>> But we could not find a fix for this errors. >>>> >>>> >>>> >>> It was supposed to be a fixed bug (i.e. it's fixed in my production >>> deployments), but somewhere that commit got lost or missed in the >>> repository. I have fixed the bug itself, and am adding a test case >>> to the >>> tests to make sure it is a covered condition, then the fixes will be >>> pushed >>> up to github. >>> >>> >>> Thanks, >>> >>> Kirk Haines >>> >>> >> >> -- >> ______________________________________________________________________ >> Marc Willwacher (Gesch?ftsf?hrung/Development) >> mwmediasolutions >> Schillerstra?e 20 - 15517 F?rstenwalde >> Tel: 03361 757417 - Mobil: 0176 23388854 >> www.mwmediasolutions.de - willwacher at mwmediasolutions.de >> >> _______________________________________________ >> Swiftiply-users mailing list >> Swiftiply-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/swiftiply-users > -- ______________________________________________________________________ Marc Willwacher (Gesch?ftsf?hrung/Development) mwmediasolutions Schillerstra?e 20 - 15517 F?rstenwalde Tel: 03361 757417 - Mobil: 0176 23388854 www.mwmediasolutions.de - willwacher at mwmediasolutions.de From info at mwmediasolutions.de Sat Oct 18 09:08:43 2008 From: info at mwmediasolutions.de (info mwmediasolutions) Date: Sat, 18 Oct 2008 15:08:43 +0200 Subject: [Swiftiply-users] Bug in Swiftiply with Firefox2 when sending a form Message-ID: <48F9DFDB.9060202@mwmediasolutions.de> Hi, I got a problem with firefox2 trying to send a form to swiftiply (latest version from 'http://github.com/wyhaines/swiftiply/tree/master') Only with FF2 it starts sending the form but nothing on the server happens and the browsers is waiting. With FF3 and IE7 it works without errors. I checked this by using wireshark - network protocol analyser - 49518 > http [SYN] Seq=0 Win=8192 [TCP CHECKSUM INCORRECT] Len=0 MSS=1460 WS=2 - http > 49518 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1452 WS=7 - 49518 > http [ACK] Seq=1 Ack=1 Win=66792 [TCP CHECKSUM INCORRECT] Len=0 - POST /account/login HTTP/1.1 - http > 49518 [ACK] Seq=1 Ack=674 Win=7296 Len=0 - Continuation or non-HTTP traffic (application/x-www-form-urlencoded) - http > 49518 [ACK] Seq=1 Ack=803 Win=8576 Len=0 Here it stops and I don't know what to do. Seems FF2 or the server is not responding correct If you want to try out by yourself, check here 'http://scholarz.net' You don't need to register, only click on login-button and then wait. Is there something I have to configure, or is it a bug? It would be very nice, if you could help me. Greetings, Marc -- ______________________________________________________________________ Marc Willwacher (Gesch?ftsf?hrung/Development) mwmediasolutions Schillerstra?e 20 - 15517 F?rstenwalde Tel: 03361 757417 - Mobil: 0176 23388854 www.mwmediasolutions.de - willwacher at mwmediasolutions.de From daniel at infoex.com Wed Oct 22 23:20:17 2008 From: daniel at infoex.com (Daniel Jabbour) Date: Wed, 22 Oct 2008 23:20:17 -0400 Subject: [Swiftiply-users] All swiftiplied mongrels crashe randomly In-Reply-To: References: <75BA1417-F363-4F28-AA72-0CF1A9F43B70@infoex.com> <48F44AFE.5070509@mwmediasolutions.de> Message-ID: <2C100A42-0DF6-4CD3-B495-1CC5957D7FBA@infoex.com> Kirk- Curious what's the status of this? Thanks in advance, Daniel -- Daniel Jabbour Executive Vice President of Systems Architecture Office: (646) 778-3789 x707 daniel at infoex.com InfoExchange, Inc. On Oct 14, 2008, at 8:49 AM, Kirk Haines wrote: > > > On Tue, Oct 14, 2008 at 1:32 AM, info mwmediasolutions > wrote: > Hi Daniel, > > we got the same problems as described in in this group in august. > But we could not find a fix for this errors. > > > It was supposed to be a fixed bug (i.e. it's fixed in my production > deployments), but somewhere that commit got lost or missed in the > repository. I have fixed the bug itself, and am adding a test case > to the tests to make sure it is a covered condition, then the fixes > will be pushed up to github. > > > Thanks, > > Kirk Haines > -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel at infoex.com Mon Oct 27 22:31:08 2008 From: daniel at infoex.com (Daniel Jabbour) Date: Mon, 27 Oct 2008 22:31:08 -0400 Subject: [Swiftiply-users] All swiftiplied mongrels crashe randomly In-Reply-To: References: <75BA1417-F363-4F28-AA72-0CF1A9F43B70@infoex.com> <48F44AFE.5070509@mwmediasolutions.de> <2C100A42-0DF6-4CD3-B495-1CC5957D7FBA@infoex.com> Message-ID: Kirk- I have patched swiftiplied_mongrel to resolve some of our issues, which appear to be related to Mongrel getting a null PATH_INFO variable. Mongrel tries to immediately regex this variable and is failing on a nil object. So I modified swiftiplied mongrel to set it to an empty string so this operation doesn't fail. What do you think of this solution? I basically set path_info to a string by calling path_info.to_s in swiftiplied_mongrel.rb. Patch details below. *** /usr/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/src/swiftcore/ swiftiplied_mongrel.rb 2008-10-27 17:01:06.000000000 -0400 --- /usr/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/src/swiftcore/ swiftiplied_mongrel.rb.orig 2008-10-27 14:47:40.000000000 -0400 *************** *** 40,46 **** @request_len = @params[::Mongrel::Const::CONTENT_LENGTH].to_i script_name, path_info, handlers = ::Mongrel ::HttpServer ::Instance.classifier.resolve(@params[::Mongrel::Const::REQUEST_PATH]) if handlers ! @params[::Mongrel::Const::PATH_INFO] = path_info.to_s @params[::Mongrel::Const::SCRIPT_NAME] = script_name @params[::Mongrel::Const::REMOTE_ADDR] = @params[::Mongrel::Const::HTTP_X_FORWARDED_FOR] || ::Socket.unpack_sockaddr_in(get_peername)[1] @notifiers = handlers.select { |h| h.request_notify } --- 40,46 ---- @request_len = @params[::Mongrel::Const::CONTENT_LENGTH].to_i script_name, path_info, handlers = ::Mongrel ::HttpServer ::Instance.classifier.resolve(@params[::Mongrel::Const::REQUEST_PATH]) if handlers ! @params[::Mongrel::Const::PATH_INFO] = path_info @params[::Mongrel::Const::SCRIPT_NAME] = script_name @params[::Mongrel::Const::REMOTE_ADDR] = @params[::Mongrel::Const::HTTP_X_FORWARDED_FOR] || ::Socket.unpack_sockaddr_in(get_peername)[1] @notifiers = handlers.select { |h| h.request_notify } -- Daniel Jabbour Executive Vice President of Systems Architecture Office: (646) 778-3789 x707 daniel at infoex.com InfoExchange, Inc. On Oct 24, 2008, at 12:05 PM, Kirk Haines wrote: > Hey. I am planning on pushing fixes to git hub late tonight that > should resolve these bugs. > > > Kirk Haines