From piet.hadermann at seagha.com Fri Jun 1 02:36:34 2007 From: piet.hadermann at seagha.com (Piet Hadermann) Date: Fri, 1 Jun 2007 08:36:34 +0200 Subject: [Swiftiply-users] eventmachine problem Message-ID: <67B95D61E544254F98FE975AA08F2FB201A92C38@srv-mail.win.antwerp.seagha.com> Sandro, There's nothing else already running on port 80 by any chance ? Regards, Piet. ________________________________ From: swiftiply-users-bounces at rubyforge.org [mailto:swiftiply-users-bounces at rubyforge.org] On Behalf Of Sandro Duarte Sent: vrijdag 1 juni 2007 1:34 To: swiftiply-users at rubyforge.org Subject: [Swiftiply-users] eventmachine problem Hi... When I start swiftiply : swiftiply -c sw.conf I get a error like this: /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/eventmachine.rb:453:i n `start_tcp_server': no acceptor (RuntimeError) from /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/eventmachine.rb:453:i n `start_server ... -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/swiftiply-users/attachments/20070601/b6504c7a/attachment.html From rick.denatale at gmail.com Fri Jun 1 11:37:16 2007 From: rick.denatale at gmail.com (Rick DeNatale) Date: Fri, 1 Jun 2007 11:37:16 -0400 Subject: [Swiftiply-users] Problems converting from pen+mongrel cluster to swiftiply+swiftiply_mongrel_rails Message-ID: This morning I finally knuckled down to experimenting with using swiftiply to serve my typoblog. I'm stuck right now with this: rick at frodo:/usr/local/lib/typo$ sudo swiftiply_mongrel_rails -h127.0.0.1 -p30000 -n1 --config /usr/local/lib/typo/config/typo_swiftiply.conf ** Loading settings from /usr/local/lib/typo/config/typo_swiftiply.conf (they override command line). ** Starting Mongrel listening at 0.0.0.0:3000 ** Changing group to typoblog. ** Changing user to typoblog. ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload (without restart). It might not work well. ** Mongrel available at 0.0.0.0:3000 ** Use CTRL-C to stop. /usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.7.0/lib/eventmachine.rb:566:in `connect_server': can't convert nil into String (TypeError) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `each' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join' from /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.5.1/bin/mongrel_rails:145:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/command.rb:211:in `run' from /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.5.1/bin/mongrel_rails:252 from /usr/local/bin/mongrel_rails:16:in `load' from /usr/local/bin/mongrel_rails:16 Using Evented Mongrel The immediate problem is the failure. A secondary question is whether or not mongrel is really listening on port 3000. Is this just a spurious/vestigial message from the patched mongrel? Okay here's more info. Here's the mongrel config file: rick at frodo:/usr/local/lib/typo$ cat /usr/local/lib/typo/config/typo_swiftiply.conf --- :docroot: public :host: 0.0.0.0 :prefix: :mime_map: :port: 3000 :timeout: 0 :cwd: /usr/local/lib/typo :daemon: false :log_file: log/mongrel.log :group: typoblog :includes: - mongrel :user: typoblog :pid_file: log/mongrel.pid :config_script: :debug: false :environment: development :config_file: :num_processors: 1024 rick at frodo:/usr/local/lib/typo$ Since I'd previously been using mongrel_cluster, I didn't have an existing mongrel configuration, so I got this one by doing: sudo mongrel_rails start -c/usr/local/lib/typo --user typoblog --group typoblog -G config/typo_swiftiply.conf Here are the gem versions I've got installed: rick at frodo:/usr/local/lib/typo$ gem list --local | egrep '\([0-9]' actionmailer (1.3.3, 1.3.2, 1.3.0, 1.2.5) actionpack (1.13.3, 1.13.2, 1.13.0, 1.12.5) actionwebservice (1.2.3, 1.2.2, 1.2.0, 1.1.6) activerecord (1.15.3, 1.15.2, 1.15.0, 1.14.4) activesupport (1.4.2, 1.4.1, 1.4.0, 1.3.1) aws-s3 (0.3.0) builder (2.1.1) cgi_multipart_eof_fix (2.1) daemons (1.0.5) eventmachine (0.7.0) fastri (0.3.0.1) fastthread (1.0, 0.6.4.1) ferret (0.11.4, 0.11.3) gem_plugin (0.2.2) GraphvizR (0.5.1) hoe (1.2.0) hpricot (0.5) memoize (1.2.2) mime-types (1.15) mongrel (1.0.1) mongrel_cluster (0.2.1) mysql (2.7) ParseTree (1.7.0) permutation (0.1.5, 0.1.4) PriorityQueue (0.1.2) railroad (0.4.0, 0.3.4) rails (1.2.3, 1.2.2, 1.2.0, 1.1.6) rails-app-installer (0.2.0) rake (0.7.3, 0.7.2) rcodetools (0.5.0.0) ruby-debug (0.9.3, 0.9.2) ruby-debug-base (0.9.3, 0.9.2) rubyforge (0.4.1, 0.4.0) RubyInline (3.6.3, 3.6.2) sources (0.0.1) sqlite3-ruby (1.2.1) swiftiply (0.5.1, 0.5.0) tattle (1.0.3) typo (4.1, 4.0.3) tzinfo (0.3.3) unicode (0.1) vim-ruby (2007.05.07, 2007.03.02) VimMate (0.6.2) xml-simple (1.0.11) HELP! Let me know if any more info is needed. -- Rick DeNatale My blog on Ruby http://talklikeaduck.denhaven2.com/ From sandrods at gmail.com Fri Jun 1 12:35:59 2007 From: sandrods at gmail.com (Sandro Duarte) Date: Fri, 1 Jun 2007 13:35:59 -0300 Subject: [Swiftiply-users] eventmachine problem In-Reply-To: <67B95D61E544254F98FE975AA08F2FB201A92C38@srv-mail.win.antwerp.seagha.com> References: <67B95D61E544254F98FE975AA08F2FB201A92C38@srv-mail.win.antwerp.seagha.com> Message-ID: <8133b8010706010935h70ce48bn856185fcdaf5bb63@mail.gmail.com> Nopes... nothing running on the 80. Any other ideai? TIA Sandro On 6/1/07, Piet Hadermann wrote: > > Sandro, > > There's nothing else already running on port 80 by any chance ? > > Regards, > > Piet. > > ------------------------------ > *From:* swiftiply-users-bounces at rubyforge.org [mailto: > swiftiply-users-bounces at rubyforge.org] *On Behalf Of *Sandro Duarte > *Sent:* vrijdag 1 juni 2007 1:34 > *To:* swiftiply-users at rubyforge.org > *Subject:* [Swiftiply-users] eventmachine problem > > Hi... > > When I start swiftiply : > > swiftiply -c sw.conf > > I get a error like this: > > /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/eventmachine.rb:453:in > `start_tcp_server': no acceptor (RuntimeError) > from /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/eventmachine.rb:453:in > `start_server > ... > > -- Sandro Duarte Analista de Sistemas STI/SADES TRE-RS -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/swiftiply-users/attachments/20070601/65689731/attachment.html From sandrods at gmail.com Fri Jun 1 13:26:49 2007 From: sandrods at gmail.com (Sandro Duarte) Date: Fri, 1 Jun 2007 14:26:49 -0300 Subject: [Swiftiply-users] eventmachine problem In-Reply-To: <67B95D61E544254F98FE975AA08F2FB201A92C38@srv-mail.win.antwerp.seagha.com> References: <67B95D61E544254F98FE975AA08F2FB201A92C38@srv-mail.win.antwerp.seagha.com> Message-ID: <8133b8010706011026k3e867f9fi7c740caf9e664fdd@mail.gmail.com> I think I've figured it out. I have to start swiftply BEFORE starting swiftply_mongrel_rails. Then I get no errors... But It seems that the mongrels aren't talkink to swiftply. I point my browser to the machine but gets nothing... just waiting... Sandro On 6/1/07, Piet Hadermann wrote: > > Sandro, > > There's nothing else already running on port 80 by any chance ? > > Regards, > > Piet. > > ------------------------------ > *From:* swiftiply-users-bounces at rubyforge.org [mailto: > swiftiply-users-bounces at rubyforge.org] *On Behalf Of *Sandro Duarte > *Sent:* vrijdag 1 juni 2007 1:34 > *To:* swiftiply-users at rubyforge.org > *Subject:* [Swiftiply-users] eventmachine problem > > Hi... > > When I start swiftiply : > > swiftiply -c sw.conf > > I get a error like this: > > /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/eventmachine.rb:453:in > `start_tcp_server': no acceptor (RuntimeError) > from /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/eventmachine.rb:453:in > `start_server > ... > > -- Sandro Duarte Analista de Sistemas STI/SADES TRE-RS -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/swiftiply-users/attachments/20070601/9ae28f0f/attachment.html From kevwil at gmail.com Fri Jun 1 21:58:39 2007 From: kevwil at gmail.com (Kevin Williams) Date: Fri, 1 Jun 2007 19:58:39 -0600 Subject: [Swiftiply-users] browser hangs with swiftiply proxy Message-ID: <683a886f0706011858q182cd1edyac6be915a08d1f8c@mail.gmail.com> I'm using eventified mongrel and it works fine, so I thought I would try the swiftiply proxy. I can't get it to work, the browser just hangs. Here are my config files: mongrel.conf: --------------------------------------------------- --- :timeout: 0 :cwd: /Users/kevin/dev/subversion/btwebsite :daemon: true :log_file: log/mongrel.log :includes: - mongrel :user: :pid_file: log/mongrel.pid :group: :config_script: config/mongrel_hashed_download.rb :environment: development :config_file: :num_processors: 1024 :debug: false :docroot: public :host: 127.0.0.1 :prefix: :mime_map: :port: "3000" swiftiply.yml: ------------------------------------------------------------ cluster_address: btwebsite cluster_port: 11223 daemonize: true map: - incoming: btwebsite outgoing: 127.0.0.1:13000 default: true The command-line I am using goes like this: swiftiply -c config/swiftiply.yml swiftiply_mongrel_rails -h 127.0.0.1 -p 13000 -n 1 -d -C config/mongrel.conf -- Cheers, Kevin Williams http://www.almostserio.us/ "If you don't think carefully, you might think that programming is just typing statements in a programming language." - Ward Cunningham "Any sufficiently advanced technology is indistinguishable from Magic." - Arthur C. Clarke From sandrods at gmail.com Fri Jun 1 22:52:44 2007 From: sandrods at gmail.com (Sandro Duarte) Date: Fri, 1 Jun 2007 23:52:44 -0300 Subject: [Swiftiply-users] browser hangs with swiftiply proxy In-Reply-To: <683a886f0706011858q182cd1edyac6be915a08d1f8c@mail.gmail.com> References: <683a886f0706011858q182cd1edyac6be915a08d1f8c@mail.gmail.com> Message-ID: <8133b8010706011952k41fbce3fg64d6d5979bd96e52@mail.gmail.com> Having the same problem here... Sandro On 6/1/07, Kevin Williams wrote: > > I'm using eventified mongrel and it works fine, so I thought I would > try the swiftiply proxy. I can't get it to work, the browser just > hangs. Here are my config files: > > mongrel.conf: > --------------------------------------------------- > --- > :timeout: 0 > :cwd: /Users/kevin/dev/subversion/btwebsite > :daemon: true > :log_file: log/mongrel.log > :includes: > - mongrel > :user: > :pid_file: log/mongrel.pid > :group: > :config_script: config/mongrel_hashed_download.rb > :environment: development > :config_file: > :num_processors: 1024 > :debug: false > :docroot: public > :host: 127.0.0.1 > :prefix: > :mime_map: > :port: "3000" > > > > swiftiply.yml: > ------------------------------------------------------------ > cluster_address: btwebsite > cluster_port: 11223 > daemonize: true > map: > - incoming: btwebsite > outgoing: 127.0.0.1:13000 > default: true > > > The command-line I am using goes like this: > > swiftiply -c config/swiftiply.yml > swiftiply_mongrel_rails -h 127.0.0.1 -p 13000 -n 1 -d -C > config/mongrel.conf > > -- > Cheers, > > Kevin Williams > http://www.almostserio.us/ > > "If you don't think carefully, you might think that programming is > just typing statements in a programming language." - Ward Cunningham > "Any sufficiently advanced technology is indistinguishable from > Magic." - Arthur C. Clarke > _______________________________________________ > Swiftiply-users mailing list > Swiftiply-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/swiftiply-users > -- Sandro Duarte Analista de Sistemas STI/SADES TRE-RS -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/swiftiply-users/attachments/20070601/30daa424/attachment.html From abhishek.rhce at hotmail.com Sat Jun 2 08:21:23 2007 From: abhishek.rhce at hotmail.com (abhishek abhishek) Date: Sat, 2 Jun 2007 17:51:23 +0530 Subject: [Swiftiply-users] Error when starting mongrel using swiftiply Message-ID: Hi Today i was just playing swiftiply on my rails application but , i am getting following error when i am starting my mongrel cluster . I am using ruby 1.8.5 and rails 1.2.3 , eventmachine 0.7.2 and swiftiply 1.5.1/usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.5.1/src/swiftcore/swiftiplied_mongrel.rb:129:in `run': Mongrel::StopServer (Mongrel::StopServer) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `call' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `each' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join' from /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.5.1/bin/mongrel_rails:145:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/command.rb:211:in `run' from /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.5.1/bin/mongrel_rails:252 from /usr/local/bin/mongrel_rails:16:in `load' from /usr/local/bin/mongrel_rails:16This is my swiftiply.yml filecluster_address: 192.168.1.34cluster_port: 80daemonize: truemap: - incoming: - www.example.com outgoing: 192.168.1.34:6007 outgoing: 192.168.1.34:6008 outgoing: 192.168.1.34:6009Please tell me what am i doing wrong. Thanks Alot _________________________________________________________________ Want to look great? Get expert opinion on beauty and skin care. http://content.msn.co.in/Lifestyle/AskExpert/Default01.htm -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/swiftiply-users/attachments/20070602/62d88cd7/attachment.html From cs327 at teknolabs.com Sat Jun 2 11:06:48 2007 From: cs327 at teknolabs.com (Cagan) Date: Sat, 2 Jun 2007 18:06:48 +0300 Subject: [Swiftiply-users] eventmachine problem In-Reply-To: <8133b8010706011026k3e867f9fi7c740caf9e664fdd@mail.gmail.com> References: <67B95D61E544254F98FE975AA08F2FB201A92C38@srv-mail.win.antwerp.seagha.com> <8133b8010706011026k3e867f9fi7c740caf9e664fdd@mail.gmail.com> Message-ID: I have the exact same problem, I start swiftply and mongrel, but they are not talking to each other. On Jun 1, 2007, at 8:26 PM, Sandro Duarte wrote: > I think I've figured it out. > > I have to start swiftply BEFORE starting swiftply_mongrel_rails. > Then I get no errors... > > But It seems that the mongrels aren't talkink to swiftply. I point > my browser to the machine but gets nothing... just waiting... > > Sandro > > On 6/1/07, Piet Hadermann wrote: > Sandro, > > There's nothing else already running on port 80 by any chance ? > > Regards, > > Piet. > > From: swiftiply-users-bounces at rubyforge.org [mailto:swiftiply-users- > bounces at rubyforge.org] On Behalf Of Sandro Duarte > Sent: vrijdag 1 juni 2007 1:34 > To: swiftiply-users at rubyforge.org > Subject: [Swiftiply-users] eventmachine problem > > Hi... > > When I start swiftiply : > > swiftiply -c sw.conf > > I get a error like this: > > /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/eventmachine.rb: > 453:in `start_tcp_server': no acceptor (RuntimeError) > from /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/ > eventmachine.rb:453:in `start_server > ... > > > > > -- > Sandro Duarte > Analista de Sistemas > STI/SADES > TRE-RS > _______________________________________________ > Swiftiply-users mailing list > Swiftiply-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/swiftiply-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/swiftiply-users/attachments/20070602/e5d928f2/attachment-0001.html From wyhaines at gmail.com Sat Jun 2 11:16:09 2007 From: wyhaines at gmail.com (Kirk Haines) Date: Sat, 2 Jun 2007 08:16:09 -0700 Subject: [Swiftiply-users] Rails/mongrel_cluster related errors Message-ID: Looks like people are reporting a lot of the same sorts of errors trying to use swiftiply with rails & mongrel_cluster. I will dig into it this weekend and get fixes pushed out. Thanks for the error reports, everyone! Kirk Haines From abhishek.rhce at hotmail.com Mon Jun 4 07:17:23 2007 From: abhishek.rhce at hotmail.com (abhishek abhishek) Date: Mon, 4 Jun 2007 16:47:23 +0530 Subject: [Swiftiply-users] connect_server error in swiftiply mongrel Message-ID: Hi,I am using swiftiply on my testing server but i m not able to run properly when i am starting swiftiply mongrels then i am getting these errors in my mongrel.log file /usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/eventmachine.rb:574:in `connect_server': no implicit conversion from nil to integer (TypeError) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `each' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join' from /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.5.1/bin/mongrel_rails:145:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/command.rb:211:in `run' from /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.5.1/bin/mongrel_rails:252 from /usr/local/bin/mongrel_rails:16:in `load' from /usr/local/bin/mongrel_rails:16Please tell me where i am wrong my swiftiply.conf is as belowcluster_address: 192.168.1.34cluster_port: 80daemonize: truemap: - incoming: - 192.168.1.34 outgoing: 127.0.0.1:6007 default: trueand mongrel.yml file is :timeout: 0:cwd: /home/capped/current:daemon: true:log_file: log/mongrel.log:includes:- mongrel:user: :pid_file: log/mongrel.pid:group: :config_script: config/mongrel_upload_progress.conf:environment: production:config_file::num_processors: 1024:debug: true:docroot: public:host: 127.0.0.1:prefix::mime_map::port: '3000' _________________________________________________________________ Palate Teasers: Straight from Master Chef! http://content.msn.co.in/Lifestyle/Moreonlifestyle/LifestylePT_101106_1530.htm -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/swiftiply-users/attachments/20070604/11273655/attachment.html From cs327 at teknolabs.com Mon Jun 4 08:29:31 2007 From: cs327 at teknolabs.com (Cagan) Date: Mon, 4 Jun 2007 13:29:31 +0100 Subject: [Swiftiply-users] connect_server error in swiftiply mongrel In-Reply-To: References: Message-ID: <196577F7-6B33-4A31-BE90-2148C8135D7F@teknolabs.com> are you running it as root? On Jun 4, 2007, at 12:17 PM, abhishek abhishek wrote: > Hi, > > I am using swiftiply on my testing server but i m not able to run > properly when i am starting swiftiply mongrels then i am getting > these errors in my mongrel.log file > > /usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/ > eventmachine.rb:574:in `connect_server': no implicit conversion > from nil to integer (TypeError) > from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/ > mongrel/configurator.rb:293:in `join' > from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/ > mongrel/configurator.rb:293:in `join' > from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/ > mongrel/configurator.rb:293:in `each' > from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/ > mongrel/configurator.rb:293:in `join' > from /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.5.1/bin/ > mongrel_rails:145:in `run' > from /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/ > mongrel/command.rb:211:in `run' > from /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.5.1/bin/ > mongrel_rails:252 > from /usr/local/bin/mongrel_rails:16:in `load' > from /usr/local/bin/mongrel_rails:16 > > Please tell me where i am wrong > my swiftiply.conf is as below > > cluster_address: 192.168.1.34 > cluster_port: 80 > daemonize: true > map: > - incoming: > - 192.168.1.34 > outgoing: 127.0.0.1:6007 > default: true > > > and mongrel.yml file is > > :timeout: 0 > :cwd: /home/capped/current > :daemon: true > :log_file: log/mongrel.log > :includes: > - mongrel > :user: > :pid_file: log/mongrel.pid > :group: > :config_script: config/mongrel_upload_progress.conf > :environment: production > :config_file: > :num_processors: 1024 > :debug: true > :docroot: public > :host: 127.0.0.1 > :prefix: > :mime_map: > :port: '3000' > > > > Palate Teasers: Straight from Master Chef! Sanjeev Kapoor > _______________________________________________ > Swiftiply-users mailing list > Swiftiply-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/swiftiply-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/swiftiply-users/attachments/20070604/9238113b/attachment.html From anoop at ranganath.com Mon Jun 4 15:08:54 2007 From: anoop at ranganath.com (Anoop Ranganath) Date: Mon, 4 Jun 2007 15:08:54 -0400 Subject: [Swiftiply-users] restarting / shutting down swiftiply_mongrel_rails Message-ID: <2B9E8D14-6B00-4520-B7DC-4F4AA8E9338D@ranganath.com> I've set up Swiftiply on my server with Mongrel, and everything is working like a champ. Now I'm looking to automate the deployments with Capistrano, and I can see how I can start the server, but I can't see a good way to have it restart or shutdown all the instances. Is there any simple way to do this that I am overlooking, or should I script something up that sends kills to each of the PIDs in dogN.pid? Thanks! Anoop From wyhaines at gmail.com Tue Jun 5 09:46:32 2007 From: wyhaines at gmail.com (Kirk Haines) Date: Tue, 5 Jun 2007 06:46:32 -0700 Subject: [Swiftiply-users] eventmachine problem In-Reply-To: References: <67B95D61E544254F98FE975AA08F2FB201A92C38@srv-mail.win.antwerp.seagha.com> <8133b8010706011026k3e867f9fi7c740caf9e664fdd@mail.gmail.com> Message-ID: On 6/2/07, Cagan wrote: > I have the exact same problem, I start swiftply and mongrel, but they are > not talking to each other. Are you using swiftiply_mongrel_rails, too? Try it with just: env SWIFT=1 mongrel_rails Make sure that if you are having Swiftiply run on a port below 1024, you have to start it with root (I'll add an option in the future to have it change it's id after starting so it doesn't need to keep running as root). Also, are you going through another web server/proxy to reach swiftiply, or going straight to it from the browser? Thanks, Kirk Haines From cs327 at teknolabs.com Tue Jun 5 09:51:23 2007 From: cs327 at teknolabs.com (Cagan) Date: Tue, 5 Jun 2007 14:51:23 +0100 Subject: [Swiftiply-users] eventmachine problem In-Reply-To: References: <67B95D61E544254F98FE975AA08F2FB201A92C38@srv-mail.win.antwerp.seagha.com> <8133b8010706011026k3e867f9fi7c740caf9e664fdd@mail.gmail.com> Message-ID: Lately I started using event based mongrel by using the following command: env EVENT=1 mongrel_rails cluster::start This runs behind an apache instance... I would like to take apache out and use swiftiply instead. Should I then simply use: swiftipy_mongrel_rails? or should I use the cluser again? And what are the ? Thanks Cagan On Jun 5, 2007, at 2:46 PM, Kirk Haines wrote: > On 6/2/07, Cagan wrote: >> I have the exact same problem, I start swiftply and mongrel, but >> they are >> not talking to each other. > > Are you using swiftiply_mongrel_rails, too? > > Try it with just: > > env SWIFT=1 mongrel_rails > > Make sure that if you are having Swiftiply run on a port below 1024, > you have to start it with root (I'll add an option in the future to > have it change it's id after starting so it doesn't need to keep > running as root). > > Also, are you going through another web server/proxy to reach > swiftiply, or going straight to it from the browser? > > > Thanks, > > Kirk Haines From wyhaines at gmail.com Tue Jun 5 10:05:24 2007 From: wyhaines at gmail.com (Kirk Haines) Date: Tue, 5 Jun 2007 07:05:24 -0700 Subject: [Swiftiply-users] Fwd: restarting / shutting down swiftiply_mongrel_rails In-Reply-To: References: <2B9E8D14-6B00-4520-B7DC-4F4AA8E9338D@ranganath.com> Message-ID: ---------- Forwarded message ---------- From: Kirk Haines Date: Jun 5, 2007 7:05 AM Subject: Re: [Swiftiply-users] restarting / shutting down swiftiply_mongrel_rails To: Anoop Ranganath On 6/4/07, Anoop Ranganath wrote: > I've set up Swiftiply on my server with Mongrel, and everything is > working like a champ. Now I'm looking to automate the deployments > with Capistrano, and I can see how I can start the server, but I > can't see a good way to have it restart or shutdown all the > instances. Is there any simple way to do this that I am overlooking, > or should I script something up that sends kills to each of the PIDs > in dogN.pid? I'm completely open to suggestions here. What capabilities would you like to see to make everything interoperate with Capistrano better? Kirk Haines From wyhaines at gmail.com Tue Jun 5 10:05:56 2007 From: wyhaines at gmail.com (Kirk Haines) Date: Tue, 5 Jun 2007 07:05:56 -0700 Subject: [Swiftiply-users] Fwd: connect_server error in swiftiply mongrel In-Reply-To: References: Message-ID: ---------- Forwarded message ---------- From: Kirk Haines Date: Jun 5, 2007 7:03 AM Subject: Re: [Swiftiply-users] connect_server error in swiftiply mongrel To: abhishek abhishek On 6/4/07, abhishek abhishek wrote: > I am using swiftiply on my testing server but i m not able to run properly > when i am starting swiftiply mongrels then i am getting these errors in my > mongrel.log file > > /usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.7.2/lib/eventmachine.rb:574:in > `connect_server': no implicit conversion from nil to integer (TypeError) > cluster_address: 192.168.1.34 > cluster_port: 80 > daemonize: true > map: > - incoming: > - 192.168.1.34 > outgoing: 127.0.0.1:6007 > default: true That looks fine. > :host: 127.0.0.1 > :prefix: > :mime_map: > :port: '3000' Looks like you are trying to connect to port 3000 instead of 6007. I am working on clearer error reporting. Kirk Haines From rick.denatale at gmail.com Tue Jun 5 14:06:31 2007 From: rick.denatale at gmail.com (Rick DeNatale) Date: Tue, 5 Jun 2007 14:06:31 -0400 Subject: [Swiftiply-users] Fwd: connect_server error in swiftiply mongrel In-Reply-To: References: Message-ID: On 6/5/07, Kirk Haines wrote: > > On 6/4/07, abhishek abhishek wrote: > > > :port: '3000' > > Looks like you are trying to connect to port 3000 instead of 6007. > > I am working on clearer error reporting. Oops, sorry for the earlier short response, itchy trigger finger. I had the same problem too, I'm still trying to get up and going using swiftiply_mongrel rails. I'd suggest some more documentation as well as clearer error reporting. I thought that the -p / --port option on s_m_r would take preference, apparently not. I was also confused because with it comes up mongrel reports that it's listening on the port, which I thought was spurious since with swiftiply it certainly should be connecting to that port. Some example mongrel/mongrel_cluster configurations showing how the settings should relate to swiftiply and/or swiftiply_mongrel_rails would be helpful. Another option which seems problematical is the pid file location (see below). I'm still having two problems: 1) Periodically (I think for some time after mongrel comes up, but not sure about that), the browser is getting the http response returned with a text mime-type. In other words I see this as the start of whats rendered: OKConnection: close Date: Tue, 05 Jun 2007 16:34:22 GMT Status: 200 OK Cache-Control: no-cache Server: Mongrel 1.0.1 Content-Type: text/html Content-Length: 25402 Note that my setup is Apache to swiftiply via mod proxy. The virtual host configuration, other than the servername and proxy and reverse proxy ports is the same as the virtual host config for my normal config which uses mongrel_cluster. 2) I don't seem to have any pid files generated. My mongrel config has: :pid_file: lib/dog.pid When I start three mongrels with: $ sudo swiftiply_mongrel_rails -n3 -c/usr/local/lib/typo/config/typo_swiftiply.conf Using Evented Mongrel Using Evented Mongrel Using Evented Mongrel If I then do: $ ps aux | grep typo_swiftiply typoblog 857 51.0 4.3 37316 33444 ? R 13:04 0:09 ruby /usr/local/bin/mongrel_rails start -p 4000 -e production -P /home/systemlinks/usr/local/lib/typo/log/dog0.pid -C /usr/local/lib/typo/config/typo_swiftiply.conf typoblog 860 35.0 2.7 25348 21512 ? R 13:04 0:05 ruby /usr/local/bin/mongrel_rails start -p 4000 -e production -P /home/systemlinks/usr/local/lib/typo/log/dog1.pid -C /usr/local/lib/typo/config/typo_swiftiply.conf typoblog 864 27.8 2.2 20872 17088 ? R 13:04 0:02 ruby /usr/local/bin/mongrel_rails start -p 4000 -e production -P /home/systemlinks/usr/local/lib/typo/log/dog2.pid -C /usr/local/lib/typo/config/typo_swiftiply.conf rick 866 0.0 0.1 2884 800 pts/1 R+ 13:04 0:00 grep typo_swiftiply Note that I've got /usr symlinked to a drive other than my root drive, hence the -P options above. It looks like I SHOULD have /usr/local/lib/typo/log/dogn.pid for n in 1..3 but I don't: $ sudo ls log/ development.log mongrel.8001.pid mongrel.log testing.log mongrel.8000.pid mongrel.8002.pid production.log test.log those mongrel.*.pid files are for my normal system which is using mongrel_cluster_ctl So now I try use mongrel_cluster instead of swiftiply_mongrel_rails, but the ports don't seem to be working right $ cat config/swiftiply/mongrel_cluster.yml --- user: typoblog cwd: /usr/local/lib/typo port: "5072" environment: production group: typoblog address: 127.0.0.1 pid_file: log/dog.pid servers: 3 $ env SWIFTIPLY=1 sudo mongrel_cluster_ctl -vc config/swiftiply start Starting all mongrel_clusters... mongrel_rails cluster::start -c mongrel_cluster.yml -v Starting 3 Mongrel servers... mongrel_rails start -d -e production -p 5072 -a 127.0.0.1 -P log/dog.5072.pid -c /usr/local/lib/typo --user typoblog --group typoblog mongrel_rails start -d -e production -p 5073 -a 127.0.0.1 -P log/dog.5073.pid -c /usr/local/lib/typo --user typoblog --group typoblog mongrel_rails start -d -e production -p 5074 -a 127.0.0.1 -P log/dog.5074.pid -c /usr/local/lib/typo --user typoblog --group typoblog $ ps aux | grep "log/dog" typoblog 1325 2.5 4.2 44652 33268 ? Sl 13:54 0:10 ruby /usr/local/bin/mongrel_rails start -d -e production -p 5073 -a 127.0.0.1 -P log/dog.5073.pid -c /usr/local/lib/typo --user typoblog --group typoblog typoblog 1328 2.7 4.2 44644 33268 ? Rl 13:54 0:11 ruby /usr/local/bin/mongrel_rails start -d -e production -p 5074 -a 127.0.0.1 -P log/dog.5074.pid -c /usr/local/lib/typo --user typoblog --group typoblog rick 1437 0.0 0.1 2876 812 pts/1 S+ 14:01 0:00 grep log/dog It looks like mongrel_cluster control is starting the mongrels on different ports (which is what I suspected based on what it does normally), and that the first one is failing silently for some reason. And I'm still not seeing the pid files written to the log directory. The permissions seem to be set up to allow them. -- Rick DeNatale My blog on Ruby http://talklikeaduck.denhaven2.com/ From rick.denatale at gmail.com Tue Jun 5 15:17:03 2007 From: rick.denatale at gmail.com (Rick DeNatale) Date: Tue, 5 Jun 2007 15:17:03 -0400 Subject: [Swiftiply-users] Mongrel cluster and swiftiply (was Re: Fwd: connect_server error in swiftiply mongrel) Message-ID: On 6/5/07, Rick DeNatale wrote: > So now I try use mongrel_cluster instead of swiftiply_mongrel_rails, > but the ports don't seem to be working right > > $ env SWIFTIPLY=1 sudo mongrel_cluster_ctl -vc config/swiftiply start > Starting all mongrel_clusters... > mongrel_rails cluster::start -c mongrel_cluster.yml -v > Starting 3 Mongrel servers... > mongrel_rails start -d -e production -p 5072 -a 127.0.0.1 -P > log/dog.5072.pid -c /usr/local/lib/typo --user typoblog --group > typoblog > mongrel_rails start -d -e production -p 5073 -a 127.0.0.1 -P > log/dog.5073.pid -c /usr/local/lib/typo --user typoblog --group > typoblog > mongrel_rails start -d -e production -p 5074 -a 127.0.0.1 -P > log/dog.5074.pid -c /usr/local/lib/typo --user typoblog --group > typoblog > It looks like mongrel_cluster control is starting the mongrels on > different ports (which is what I suspected based on what it does > normally), and that the first one is failing silently for some reason. Okay, now I realize that the environment variable is SWIFT not SWIFTIPLY $ env SWIFT=1 sudo mongrel_cluster_ctl -vc config/swiftiply start Starting all mongrel_clusters... mongrel_rails cluster::start -c mongrel_cluster.yml -v Using Evented Mongrel Starting 3 Mongrel servers... mongrel_rails start -d -e production -p 5072 -a 127.0.0.1 -P log/dog.5072.pid -c /usr/local/lib/typo --user typoblog --group typoblog mongrel_rails start -d -e production -p 5073 -a 127.0.0.1 -P log/dog.5073.pid -c /usr/local/lib/typo --user typoblog --group typoblog mongrel_rails start -d -e production -p 5074 -a 127.0.0.1 -P log/dog.5074.pid -c /usr/local/lib/typo --user typoblog --group typoblog $ netstat | grep 5072 tcp 0 0 localhost.localdo:58815 localhost.localdom:5072 ESTABLISHED tcp 0 0 localhost.localdom:5072 localhost.localdo:58815 ESTABLISHED So now the mongrel connecting to port 5072 got up, but the other two tried ports 5073 and 5074 and died silently. -- Rick DeNatale My blog on Ruby http://talklikeaduck.denhaven2.com/ IPMS/USA Region 12 Coordinator http://ipmsr12.denhaven2.com/ Visit the Project Mercury Wiki Site http://www.mercuryspacecraft.com/ From rick.denatale at gmail.com Tue Jun 5 16:13:13 2007 From: rick.denatale at gmail.com (Rick DeNatale) Date: Tue, 5 Jun 2007 16:13:13 -0400 Subject: [Swiftiply-users] Mongrel cluster and swiftiply (was Re: Fwd: connect_server error in swiftiply mongrel) In-Reply-To: References: Message-ID: I've been doing this a kind of stream of consciousness, so I thought that I should document where I am now. Still some problems which a keeping me from switching to swiftiply for my public face. Here's my configuration $ cat /etc/swiftiply/testswiftiply.conf cluster_address: 127.0.0.1 cluster_port: 5072 daemonize: true timeout: 2 map: - incoming: - tldtest.local.denhaven2.com outgoing: 127.0.0.1:30000 default: true I start swiftiply with: swiftiply -c/etc/swiftiply/testswiftiply.conf $ cat config/swiftiply/mongrel.yml --- :docroot: public :host: 0.0.0.0 :prefix: :mime_map: :port: 30000 :timeout: 0 :cwd: /usr/local/lib/typo :daemon: true :log_file: log/mongrel.log :group: typoblog :includes: - mongrel :user: typoblog :pid_file: log/dog.pid :config_script: :debug: false :environment: production :config_file: :num_processors: 1024 $sudo swiftiply_mongrel_rails -n3 --config config/swiftiply/mongrel.yml -p 30000 This seems to work except that PROBLEM #1: there's just one dog.pid PROBLEM #2: I'm still seeing http response text in the browser instead of rendered html, at least for a while after startup. I'm concerned that this might show up after startup, so this is my big showstopper. Here's my apache2 virtual host configuration, slightly abridged: ServerName tldtest.local.denhaven2.com ServerAlias tldtest.local.denhaven2.com ErrorLog /var/log/apache2/tlad_test_error.log CustomLog /var/log/apache2/tlad__test_access.log combined ErrorDocument 502 /static/502.html ServerSignature On # This is the important part--it sets up proxying. ProxyRequests Off Order deny,allow Allow from all #serve static files from apache ProxyPass /static ! Alias /static /usr/local/lib/typo/static ProxyPass /images ! Alias /images /usr/local/lib/typo/public/images ProxyPass /stylesheets ! #Alias /stylesheets/theme /usr/local/lib/typo/themes Alias /stylesheets /usr/local/lib/typo/public/stylesheets ProxyPass /javascripts ! Alias /javascripts /usr/local/lib/typo/public/javascripts ProxyPass /files ! Alias /files /usr/local/lib/typo/public/files ProxyPass / http://localhost:5072/ ProxyPassReverse / http://localhost:5072/ ProxyPreserveHost On There are some errors in the apache error log, but the last one is several hours ago and certainly before the last time I got the http response as text instead of rendered html. -- Rick DeNatale My blog on Ruby http://talklikeaduck.denhaven2.com/ From wyhaines at gmail.com Wed Jun 6 00:20:49 2007 From: wyhaines at gmail.com (Kirk Haines) Date: Tue, 5 Jun 2007 21:20:49 -0700 Subject: [Swiftiply-users] Mongrel cluster and swiftiply (was Re: Fwd: connect_server error in swiftiply mongrel) In-Reply-To: References: Message-ID: On 6/5/07, Rick DeNatale wrote: > PROBLEM #2: I'm still seeing http response text in the browser > instead of rendered html, at least for a while after startup. I'm > concerned that this might show up after startup, so this is my big > showstopper. This is a dumb but in the swiftiplied_mongrel. It will happen on the first request that a process handles. I am fixing it tonight. I'll do testing tomorrow and then will get 0.5.2 pushed out. Kirk Haines From jw at innerewut.de Tue Jun 12 07:59:01 2007 From: jw at innerewut.de (Jonathan Weiss) Date: Tue, 12 Jun 2007 13:59:01 +0200 Subject: [Swiftiply-users] Problem running swiftiply / mongrel Message-ID: <466E8A85.3000601@innerewut.de> Cheers, I'm experimenting with swfitiply but having problems getting it to run. I installed swiftiply like this (on OS X 10.4 Intel, Ruby 1.8.5): #gem install swiftiply -y Need to update 29 gems from http://gems.rubyforge.org ............................. complete Building native extensions. This could take a while... Successfully installed swiftiply-0.5.1 Successfully installed eventmachine-0.7.2 Installing ri documentation for swiftiply-0.5.1... Installing ri documentation for eventmachine-0.7.2... Installing RDoc documentation for swiftiply-0.5.1... Installing RDoc documentation for eventmachine-0.7.2... Then I created this config file: # swiftiply -c config/swiftiply.yml -p {"cluster_address"=>"127.0.0.1", "timeout"=>3, "map"=> [{"default"=>true, "outgoing"=>["127.0.0.1:4000"], "keepalive"=>true, "incoming"=>["swiftcore.org", "www.swiftcore.org", "127.0.0.1"]}], "cluster_port"=>8000, "daemonize"=>false} I then started swiftiply: # swiftiply -c config/swiftiply.yml And on another console Mongrel (1.0.1): # env SWIFT=1 mongrel_rails start -p 4000 On this point I get no error messages. When I open the web browser at http://127.0.0.1:8000/ I normaly get redirected, in this case I see this: Moved Temporarily Connection: close Date: Tue, 12 Jun 2007 11:56:31 GMT Set-Cookie: _app_session=94f7be5ce3a61065195fc86e9e0077cd; path=/ Status: 302 Found Location: http://127.0.0.1:8000/news/overview Cache-Control: no-cache Server: Mongrel 1.0.1 Content-Type: text/html; charset=utf-8 Content-Length: 101 You are being redirected. If I manually navigate to http://127.0.0.1/news/overview (the redirect target) the blank page just hangs. But from what I see in the development.log the page got rendered. So it seems like nothing got from Mongrel to Swiftiply. Any hints? -- Jonathan Weiss http://blog.innerewut.de