Opened 4 years ago
Closed 7 weeks ago
#755 closed defect (fixed)
munin-node-configure does not support snmp v3
| Reported by: | janl | Owned by: | ligne |
|---|---|---|---|
| Priority: | high | Milestone: | Munin 2.0.0 |
| Component: | node | Version: | 1.4.0 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Munin 1.4.0's Munin::Plugin::SNMP supports SNMP v3 and thus all plugins ported to this also supports SNMP v3. But munin-node-configure does not support this yet.
Change History (6)
comment:1 Changed 4 years ago by janl
comment:2 Changed 3 years ago by janl
- Version changed from 1.4.0-alpha to 1.4.0
comment:3 Changed 3 years ago by janl
- Milestone changed from Munin 1.4.4 to Munin 1.4.5
- Owner changed from nobody to ligne
comment:4 Changed 3 years ago by ligne
this is implemented in trunk (as of r3590). brief testing suggests it mostly works.
it adds new links with a snmp_, not snmpv3_ prefix. this is because some plugins contain their own, obsolete versions of M::P::SNMP::config_session() that can't cope with the latter form:
2010/05/12-13:24:21 Munin::Node::Server (type Net::Server::Fork) starting! pid(19237) Binding to TCP port 4948 on host * Setting gid to "451 451" 2010/05/12-13:24:21 [19237] Error output from snmpv3_localhost_df: 2010/05/12-13:24:21 [19237] # Error: couldn't understand what I'm supposed to monitor. 2010/05/12-13:24:21 [19237] Service 'snmpv3_localhost_df' exited with status 255/0.
--remove-also is also broken (tries to replace snmpv3_* with corresponding snmp_*), though i think that's easily fixed. will experiment later.
the new option flags still need documenting, and possibly greater thought into what they should be called.
comment:5 Changed 3 years ago by ligne
i've (finally) added some documentation in r3891.
comment:6 Changed 7 weeks ago by snide
- Milestone changed from Munin 1.4.7 to Munin 2.0
- Resolution set to fixed
- Status changed from new to closed

Workaround: Discover with version 2? :I We plan to fix this, not by 1.4.0 though.