Archived community.zenoss.org | full text search
Skip navigation
79265 Views 13 Replies Latest reply: Sep 25, 2009 8:16 AM by Ryan Matte RSS
JPSelter Rank: White Belt 13 posts since
Sep 22, 2009
Currently Being Moderated

Sep 22, 2009 11:16 AM

RRD file missing

Hello community!

 

I´m new to Zenoss and to get it running easily I downloaded the VMWare version. I really wonder why a pre-installed VM version still has this error: missing RRD file. What does that mean? How can I solve this? I haven´t altered zenoss in any way (except for adding 2 hosts and 1 user for test purposes). Thanks for any help!

 

kind regards, Peter

  • Ryan Matte ZenossMaster 653 posts since
    Mar 26, 2009
    Currently Being Moderated
    1. Sep 22, 2009 11:56 AM (in response to JPSelter)
    Re: RRD file missing

    RRD files are Round Robin Database files.  They are used to store performance data for graphs.  They store data going back a full year.  If you are receiving an error on a graph which states that an RRD file is missing, it is most likely because you do not have the correct performance template applied to a particular device (it is unable to poll the SNMP OIDs which it is attempting to poll to gather the performance data on the given device).  I would suggest that you read the Zenoss Admin Guide from top to bottom as it explains this as well as many other common issues that you may run across.

     

    Regards,

    Ryan Matte

    Nova Networks

    rmatte@novanetworks.com

  • dbuck Rank: Green Belt 119 posts since
    Jul 22, 2008
    Currently Being Moderated
    2. Sep 22, 2009 12:34 PM (in response to Ryan Matte)
    Re: RRD file missing

    I agree with you Ryan Matte.

     

    I got some experiences with the vmware-appliance of zenoss. In original the appliance is good to use for demo or testing a little bit around with Zenoss...

     

    We use it in production state, so if you want to do the same you schould read the grandiose Community-FAQ here: docs/DOC-2445

    as a good starting point.

    There are many small stones on the way to get it work for a  medium-sized Network. Therefore you need to bring a bit of time to make it work right for you. You have to customize it at some points. For a fast growing big Network you should make a own Installation, if you have enough Linux-experiences.

     

    If you get it working it is the best open source System and Network Monitoring Software i have ever seen.

     

    Regards

     

    dbuck

  • Ryan Matte ZenossMaster 653 posts since
    Mar 26, 2009
    Currently Being Moderated
    4. Sep 23, 2009 9:33 AM (in response to JPSelter)
    Re: RRD file missing
    What type of device is this?  It is possible to have a device configured to only display certain parts of the snmp table.  Generally by default the public community string is configured to only have access to certain OIDs.  You'll want to make sure that you can actually snmpwalk the values that it's complaining about, by doing something like: snmpwalk -v1 -c public host.whatever <OID> where OID is the SNMP OID (without the <>'s).  If you are unable to see any values when doing this then something is misconfigured on the device, or that OID is not valid on that device.
  • Ryan Matte ZenossMaster 653 posts since
    Mar 26, 2009
    Currently Being Moderated
    7. Sep 23, 2009 12:19 PM (in response to JPSelter)
    Re: RRD file missing

    That's because your SNMP on your linux host is not configured properly.  My guess is that you're using default settings.

     

    You need to modify your /etc/snmp/snmpd.conf file.

     

    Near the top you'll see rocommunity and rwcommunity lines, if they aren't there they need to be set:

     

    rocommunity  yourstring

    rwcommunity  yourstring

     

    Replace yourstring with whatever you want (it is very bad security practice to leave it as public).

     

    Near the bottom fo the file you'll want lines such as:

     

    com2sec paranoid  default         public
    group MyROSystem v1        paranoid
    group MyROSystem v2c       paranoid
    group MyROSystem usm       paranoid
    group MyROGroup v1         readonly
    group MyROGroup v2c        readonly
    group MyROGroup usm        readonly
    group MyRWGroup v1         readwrite
    group MyRWGroup v2c        readwrite
    group MyRWGroup usm        readwrite
    view all    included  .1                               80
    view system included  .iso.org.dod.internet.mgmt.mib-2.system
    access MyROSystem ""     any       noauth    exact  system none   none
    access MyROGroup ""      any       noauth    exact  all    none   none
    access MyRWGroup ""      any       noauth    exact  all    all    none

     

    You only have access to part of the snmp tree at the moment, hence why you are seeing those debug messages relating to memAvailReal and such.

  • Ryan Matte ZenossMaster 653 posts since
    Mar 26, 2009
    Currently Being Moderated
    8. Sep 23, 2009 12:24 PM (in response to Ryan Matte)
    Re: RRD file missing

    Here is a working snmpd.conf: http://pastebin.com/f3f460847

     

    Edit it to your liking (modify the trap IPs, your-key needs to be replaced with the snmp community strings of your choice, the location info and contact info need to be modified as well).

  • Ryan Matte ZenossMaster 653 posts since
    Mar 26, 2009
    Currently Being Moderated
    11. Sep 23, 2009 1:39 PM (in response to JPSelter)
    Re: RRD file missing

    No, those should be working as well, tripple check your snmpd.conf to make sure that it looks like the one I pasted.  There's no such thing as "not compatible" when you're talking about the snmp agent on one Linux host versus another.  It's the same service running on the same kernel.  You may need to restart the snmpd service or restart the server.

     

    Also, you'll want to remodel the device in Zenoss.

  • Ryan Matte ZenossMaster 653 posts since
    Mar 26, 2009
    Currently Being Moderated
    13. Sep 25, 2009 8:16 AM (in response to JPSelter)
    Re: RRD file missing
    Oh, you weren't looking at debug messages, you were looking at the first events generated after the server was added to Zenoss.  Yes, that is normal, you'll see a whole slew of events like that each time you add a device.  After adding any device all you care about are the gray events (debug events).  The other stuff doesn't matter (unless it's above info severity, then it could be an issue).

More Like This

  • Retrieving data ...

Legend

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