The python module: http://pastebin.com/m59bece86
I'm collecting data just fine, but gmond restarts will be problematic. Basically, user gmond will end up with varnishlog processes that will never exit until I come through and kill them off by hand after a few gmond restarts. On Sat, May 23, 2009 at 11:43 PM, David Birdsong <[email protected]> wrote: > I have a python module that spawns a separate thread that collects > data off of a pipe. > > Everything runs fine, but I'm finding that metric_cleanup is never > called. When I strace the PID of the worker thread(in Linux so it > get's it's own PID), I see it gets a SIGTERM when I stop gmond instead > of exiting under it's own power. All of the gmond processes exit, but > a subprocess of my worker thread just ends up being reparented to > init instead of being cleaned up by my metric_cleanup logic. > > The worker thread reads from an endless pipe using a select.poll with > a timeout, so the pipe shouldn't block. I need to know to kill the > process on the other end of the pipe which is what metric_cleanup > should be providing. > > I even removed all cleanup code from metric_cleanup() and just put an > open('/tmp/ganglia_kill', 'w'),...but no file is created. What can I > investigate to understand why it's being ignored? > > ganglia-gmond.x86_64 3.1.1-1 > ganglia-gmond-modules-python.x86_64 3.1.1-1 > libganglia-3_1_0.x86_64 3.1.1-1 > Fedora 8 2.6.26.8-57.fc8 > ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
