I'm not sure we had the same problem. I installed gitlab on very slow pc (I bought it in 2001). i need timeout increased just for the fist running. than I can reduce timeout and everything work fine. I have no idea why it work this way. I'm not ruby developer
On Wednesday, February 13, 2013 at 11:38:22 PM UTC+3, Daniel Blanchard wrote: > > I only get this error on merge request pages, but I consistently get it on > any page that has anything to do with merge requests (i.e., the > project-specific pages or the general list on the front page). Is changing > the timeout the currently accepted workaround for this? Because it seems to > send an empty response *immediately* so it's not like it times out in any > reasonable amount of time if that's what's causing this. > > On Tuesday, December 25, 2012 7:19:49 AM UTC-5, temenb wrote: >> >> I raised timeout in the file unicorn.rb. >> It fixed the problem >> >> timeout 60 >> >> -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/2575b854-bc4a-4e77-9385-bd69a318cbc4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
