I''ve migrated a Rails app that I didn''t build to a new server for a customer. Now there are certain pages which are timing out almost exactly at 10 seconds. They do not report an error, they just go to a blank white page. I know they''re timing out and not erring out b/c when I reduce the size of the query by limit and the page loads fine every time. Also this is happening with file uploads. Small files upload fine, larger one''s that require processing go to a white screen at 10 seconds. Rails 1.1.6 Ruby 1.8.4 Running on a Mongrel Cluster. I''m open to any ideas or suggestions. Thanks, in advance for any assistance or guidance you may be able to provide! -- Posted via http://www.ruby-forum.com/.
On Jun 16, 7:57 pm, Rusty Rustybucket <rails-mailing-l...@andreas- s.net> wrote:> I''ve migrated a Rails app that I didn''t build to a new server for a > customer. Now there are certain pages which are timing out almost > exactly at 10 seconds. They do not report an error, they just go to a > blank white page. > > I know they''re timing out and not erring out b/c when I reduce the size > of the query by limit and the page loads fine every time. Also this is > happening with file uploads. Small files upload fine, larger one''s that > require processing go to a white screen at 10 seconds. >This sounds like your load balancer (the thing that proxies requests to your mongrels) giving up. Fred> Rails 1.1.6 Ruby 1.8.4 Running on a Mongrel Cluster. > > I''m open to any ideas or suggestions. Thanks, in advance for any > assistance or guidance you may be able to provide! > -- > Posted viahttp://www.ruby-forum.com/.
Frederick Cheung wrote:> > This sounds like your load balancer (the thing that proxies requests > to your mongrels) giving up. > > FredAny guidance as to what to change to extend it''s attempt time? What file would this be located in? -- Posted via http://www.ruby-forum.com/.
Frederick Cheung wrote:> > This sounds like your load balancer (the thing that proxies requests > to your mongrels) giving up. > > FredSweet Solution! Apache''s timeout was set to... guess what...? 10 seconds changed it to a higher value and all is well in the world now! Thanks Frederick!!! You da man! :D -- Posted via http://www.ruby-forum.com/.