@abriening Could you post the init.d file and the god config to gist? Would be much appreciated. I like the idea of god monitoring god.
On Oct 8, 9:10 am, abriening <[email protected]> wrote: > I was having the same problem. I added an /etc/init.d/ script for god. > It automatically loads /etc/god.d/*.god configs. > > Then I add a config for monitoring god's memory usage. It restarts > itself using the init.d script. > > No cron or monit needed. > > On Aug 10, 10:10 am, lardawge <[email protected]> wrote: > > > > > Good to have you back! Thought you were done with the project and > > glade to hear otherwise. > > > I for one would love to track down the memoryleak. On my server, > > Ubuntu 8.10, it leaks like crazy. It starts at 17m and balloons to > > 160m in less than three days. Pretty big problem. I have resorted to > > restarting via cron every so often vs installing monit to manage it. > > Do you have any ideas as to where theleakis? I would be happy to > > spend some time looking at it. > > > Thanks, > > Larry > > > On Aug 9, 1:32 pm, Tom Werner <[email protected]> wrote: > > > > Hello all, > > > > I've been unable to work on God lately, and I understand that some of > > > you have some frustrations, so I'd like to more clearly specify how > > > issues and patches should be submitted. > > > > It will be much easier for me (and the community as a whole) to track > > > issues if they are placed in the official God issue tracker > > > athttp://github.com/mojombo/god/issues. So from now on, please catalog > > > any problems you have over there. > > > > If you have a patch that you'd like applied to mainline, please also > > > create an issue on GitHub with a pointer to your repo and the branch > > > that the change is on. Having patches tracked there will make sure > > > they don't fall through the cracks, and that discussion can more > > > easily be made around them. It also allows everyone to see what > > > patches are pending. > > > > As far as the memoryleakgoes, I spent a day a few weeks ago trying > > > to further track it down, and committed some changes that looked > > > promising, but it still starts leaking after an hour or so. The > > > strange thing is that on Engine Yard's Gentoo installation of Ruby, > > > God shows no leaks at all, which leads me to believe that there is > > > some compile option that prevents theleakor they've applied some non- > > > standard patches that mitigate the leaky behavior. Since I'll be > > > needing to use God on Debian very soon, I'm very keen to solve the > > > leaking problem once and for all. If you have any insight into the > > > leaks, please do respond on this thread and let me know what you've > > > discovered. > > > > Thanks to everyone that has provided help on this mailing list and has > > > contributed in a positive way! I hope to be able to spend more time on > > > God and address some of the problems that have been reported. > > > > Cheers, > > > > Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "god.rb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/god-rb?hl=en -~----------~----~----~----~------~----~------~--~---
