|
osdir.com mailing list archive |
|
Subject: Problems with SNMP... - msg#00009List: db.rddtool.munin.generalI have the following symlink: lrwxrwxrwx 1 root root 40 Sep 12 20:38 /etc/munin/plugins/snmp_192.168.24.2_cpuload -> /usr/libexec/munin/plugins/snmp__cpuload When I call the program directly, it outputs: cpu.value 36 However, when I do a 'telnet localhost 4949', and then 'list' there is no 'snmp_192.168.24.2_cpuload' showing. If try 'fetch snmp_192.168.24.2_cpuload' I DO get the correct value though. There is also no sign of the SNMP-graph in my munin-graphs, and no reference whatsoever to anything snmp-related in any of the 5 munun-logfiles. How come? How do I get snmp to work correctly? Regards, Evert ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ Thread at a glance:
Previous Message by Date: click to view message preview(no subject)invoice.pdf Description: Adobe PDF document ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/_______________________________________________ munin-users mailing list munin-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/munin-users Next Message by Date: click to view message previewRe: Problems with SNMP...Evert wrote: > /etc/munin/plugins/snmp_192.168.24.2_cpuload -> > /usr/libexec/munin/plugins/snmp__cpuload It would work out better if you could use a hostname. > > When I call the program directly, it outputs: > > cpu.value 36 > > > However, when I do a 'telnet localhost 4949', and then 'list' there is > no 'snmp_192.168.24.2_cpuload' showing. If try 'fetch > snmp_192.168.24.2_cpuload' I DO get the correct value though. Try "nodes" then "list <node>" then "fetch <plugin> <node>" > There is also no sign of the SNMP-graph in my munin-graphs, and no > reference whatsoever to anything snmp-related in any of the 5 > munun-logfiles. You must configure every host you want to monitor: [192.166.24.2] address 127.0.0.1 If your munin server will get to the plugin at localhost. Nicolai ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ Previous Message by Thread: click to view message preview(no subject)invoice.pdf Description: Adobe PDF document ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/_______________________________________________ munin-users mailing list munin-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/munin-users Next Message by Thread: click to view message previewRe: Problems with SNMP...Evert wrote: > /etc/munin/plugins/snmp_192.168.24.2_cpuload -> > /usr/libexec/munin/plugins/snmp__cpuload It would work out better if you could use a hostname. > > When I call the program directly, it outputs: > > cpu.value 36 > > > However, when I do a 'telnet localhost 4949', and then 'list' there is > no 'snmp_192.168.24.2_cpuload' showing. If try 'fetch > snmp_192.168.24.2_cpuload' I DO get the correct value though. Try "nodes" then "list <node>" then "fetch <plugin> <node>" > There is also no sign of the SNMP-graph in my munin-graphs, and no > reference whatsoever to anything snmp-related in any of the 5 > munun-logfiles. You must configure every host you want to monitor: [192.166.24.2] address 127.0.0.1 If your munin server will get to the plugin at localhost. Nicolai ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ Loading Comments...
|
|
