I can not remember exactly how to keep an instance always running. I think it is in the Passenger config file somewhere. If you google for those terms you should be able to find the config you are looking for. I think there was some discussion on StackOverflow also. The last time I updated from master was about 6 months ago. I tend to work from my own branch (bluequartz.net).
Sorry I couldn't be much help. But at least there is a trend that 32 bit servers tend to have this problem. Mike Jackson On Mar 28, 2011, at 4:34 PM, [email protected] wrote: > On Mar 28, 2011 2:20pm, Michael Jackson <[email protected]> wrote: > > Out of curiosity is your server a 32 or 64 bit server? I *thought* I only > > had the problem with 32 bit servers but I may not have been waiting long > > enough on my 64 bit side. > > I am running CentOS 5.3 x86 > > [Mon Mar 28 16:30:15] [root]@[dev] ~ > # uname -a > Linux mycompany.com 2.6.18-194.17.4.el5 #1 SMP Mon Oct 25 15:51:07 EDT 2010 > i686 athlon i386 GNU/Linux > > > I think I ended up hacking something into the Ruby code to try the > > reconnect first. I also setup my server to always have an instance of > > Gitorious running which slowed down the issues to about once a week. > > > > I have seen this comment about having an instance always running, what does > this mean? > How do I set this up? > I am running Gitorious under Apache 2.2.x via Passenger, my version is a > recent head from the mainline from about 4 weeks ago. > > I just started getting this message a about 2 weeks ago. It doesn't just > happen after a long period of inactivity it happens all day and all night > long ( I have people 10.5 hours ahead of me using the server all day their > time ). > > -- > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
