SNMP - no output

Discussion in 'Install/Configuration' started by Irulusug, Sep 14, 2006.

  1. Irulusug

    Irulusug Member


    Ive got some problems monitoring Lightspeed Enterprise. I followed the intstructions on your wiki, but dont get any output from snmpd.

    My snmpd.conf looks like this:

    pass . /usr/local/php5/bin/php /var/www/xxxx/html/cacti/scripts/litespeed.php

    If I call /usr/local/php5/bin/php /var/www/xxxx/html/cacti/scripts/litespeed.php manually I dont get any output. Cacti says: No Such Instance currently exists at this OID

    I searched the forum and found a hint to check OIDs.

    /usr/local/php5/bin/php /var/www/xxxx/html/cacti/scripts/litespeed.php '-g' . outputs:

    LiteSpeed Web Server

    But snmpwalk -c hhpv2 -v 2c . timeouts: Timeout: No Response from

    Any ideas? Thanks for your help!

    Last edited: Sep 14, 2006
  2. xing

    xing LiteSpeed Staff


    1) First of all. Please use OID: . This OID is registered with LiteSpeed Technologies so you should not have any future conflicts.

    2) Looks like you were testing with our beta release. Please check the /add-ons/ folder of 2.2+ installer for the final release of our snmpd bridge package. Re-import the templates into cacti to update them to the new official OID.

    3) Check to see if any php errors were logged.

    Looks like your OID part is wrong. It should be:
    snmpwalk -c hhpv2 -v 2c  .
    4) If your manual test of "/usr/local/php5/bin/php /var/www/xxxx/html/cacti/scripts/litespeed.php '-g' ." works and outputs the product name, then there is some problem with your snmpd.conf.
    Last edited: Sep 14, 2006
  3. xing

    xing LiteSpeed Staff

    I would recommend to trace the problem going backwards.

    Use a clean slate snmpd.conf as shown in the wiki:

    //working sample snmpd.conf
    rocommunity  public
    pass . /usr/bin/php /litespeed_snmp_scripts/sample.php
    Again, make sure you upgrade all your code/templates to our final non-beta release.

    If the above snmpd.conf works, then we are sure there is something wrong with your original snmpd.conf.

Share This Page