Using 2.2 on Ubuntu 7.10, I'm noticing a odd problem with process monitoring.  
Unfortunatly, I didn't look at this close enough before jumping to 2.2 and am 
still pre-production, so I can't say if it is unique to 2.2 or not.

I've set up a series of process objects for processes I'd like to collect basic 
stats on (memory and cpu are sufficent, so this is really just setting up the 
regex).  When I initially add the machine as a device with the processes 
running they are found just fine.  I do get rrd data on the processes.  Sounds 
good, right?  However after some time (possibly after the device is remodeled)  
all the processes "go away".  Manually remodeling the device does not return 
them.  However deleting the device and re-adding it will 'regrow' the 
processes.  During this time the processes have not exited nor restarted.  if I 
do an snmpwalk of hrSWRun and hrSWRunPerf I see the processes.

I tried stopping zenprocess from the UI and starting it from the command line as
 zenprocess run -- configfile /usr/local/zenoss/zenoss/etc/zenprocess.conf \
 --cycle -v 10
hoping to see something useful, learned little.

I'd prefer  not to have to lock the processes in production as I'm templating 
out a dynamic cluster and would like to pick up on new stuff as we spin it up.  
I'd also like to avoid manual intervention as we spin up new boxes.

So, couple of questsions

Is this a known issue?  I searched and couldn't find anything in the forums.

What's the best way to debug something like this?  I'm not 100% sure I 
understand the relationship betwen zenprocess, zenperfsnmp and zenmodler in 
managing the process objects.  Nor is it clear how to up the logging level of 
the daemons shy of running them by hand, 

Assuming I need to lock the process objects, I'd prefer to do it 
programatically..  It looks like that can be done via a rest call (just look at 
what the  drop down is posting to).  Is there a simple way to get the list of 
processes programatically?  I'm not ignoring arguments, so predicting the 
process object name is a bit tricky.




-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=20275#20275

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to