Archived community.zenoss.org | full text search
Skip navigation
1687 Views 4 Replies Latest reply: Aug 30, 2011 7:32 PM by dhopp RSS
mwcotton Rank: Brown Belt 563 posts since
Apr 23, 2008
Currently Being Moderated

Aug 29, 2011 5:10 PM

Possible to have a second zenperfsnmp running locally?

Is it possible to have a second zenperfsnmp daemon running locally? Not on a remote collector but on the zenoss server itself?

if so how? It seems if I create a new monitor/collector and then run the second zenperfsnmp like this:

 

python zenping.py --cycle   --monitor VmCollector0001

 

I then change the collector on a device to  VmCollector0001, and indeed the zenperf data is collected but zenping, zenprocess is not?

 

So, one answer may be I need to run those daemons also pointed at the new collector, but I dont want to do that, just zenperfsnmp.

 

What do I need to do to make this work? I soooo confused

  • dhopp Rank: Green Belt 184 posts since
    Jul 17, 2007

    It is possible to have logical collectors with Core however it is not officially supported (it is officially supported in Service Dynamics).

     

    It looks like you've already created the collector in the GUI so now you need to run all the daemons that will be needed to monitor whatever device you assign to this collector.  This means you need zenping, zenmodeler, zencommand, zenprocess, zenperfsnmp, zenstatus at minimum.  There may be others.

     

    Create the directory $ZENHOME/log/VmCollector0001

     

    There are a couple of different ways to start multiple daemons but this is probably the easiest way.  In $ZENHOME/bin copy each of those daemons into a new file called VmCollector0001_daemon (i.e. VmCollector0001_zenping).  Modify the new file and change CFGFILE to be reference VmCollector0001_daemon.conf.

     

    Then go to $ZENHOME/etc and create this conf file and make it look something like:

     

    monitor VmCollector0001

    logfile /opt/zenoss/log/VmCollector0001

     

    Then in $ZENHOME/etc create a file called daemons.txt and list all of the "VmCollector0001_daemon" that you just created and restart zenoss (you can try to start just one of the daemons if you want). 

     

    If everything starts ok you can then assign a device to this new collector.

     

    I'm working on this setup now and most of this was off the top of my head.  I have toyed around with changing init scripts to start multiple daemons but this seems to be the cleanest way and allows for restarting an individual collector daemon if required.

     

    I suggest you try this in a dev environment first.

     

    --Dennis

  • Shane Scott ZenossMaster 1,373 posts since
    Jul 6, 2009

    mwcotton:

     

    What I would do is add only the daemons you wish to start to the daemons.txt

     

    Best,

    --Hackman238

  • dhopp Rank: Green Belt 184 posts since
    Jul 17, 2007

    mwcotton:

     

    It is my understanding that a collector is self contained.  In other words if you have a VmCollector0001_zenperfsnmp and add just that to daemons.txt and then assign a device to that collector then *only* snmp will be collected for the collector.  If you need ping/status/process then you have to run the other daemons for VmCollector0001

     

    It is not possible to have 1 zenping and 2 zenperfsnmp and have them all share a common device list to my knowledge.  At least not without some code hacking.

     

    --Dennis

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points