One further note, just in case someone else runs into a similar problem.

Running net-snmp under the agentuser and agentgroup of _snmpd will
work, but many of your MIBs will return null data (most notably, MIB-2
Interfaces) because the agent reads /dev/mem for that data. You'll see
this kind of message in your log files if you compiled with debugging
enabled:

kvm_read(*, 1, 0x2beec61c, 4) = -1: invalid address (1)
auto_nlist failed on ifnet at location 1

And a manual snmpwalk will return something like:

$ snmpwalk -c public -v 1 10.0.0.1 interfaces
IF-MIB::ifNumber.0 = INTEGER: 0

My workaround for this was to change the agentgroup to kmem (or
whatever gid is associated with /dev/mem). It's not ideal since it has
full read access to kernel memory, but it's better than running as
root.

-HKS

On Fri, Jun 27, 2008 at 4:24 PM, (private) HKS <[EMAIL PROTECTED]> wrote:
> Thanks, took this route and things are working just fine now.
> -HKS
>
> On Fri, Jun 27, 2008 at 8:19 AM, Claer <[EMAIL PROTECTED]> wrote:
>> On Fri, Jun 27 2008 at 13:12, Stephan A. Rickauer wrote:
>>> On Wed, 2008-06-25 at 11:17 -0400, (private) HKS wrote:
>>> > In my quest for real SNMP monitoring of OpenBSD, I installed 
>>> > net-snmp-5.4.1p0
>>> > on an OpenBSD 4.3 box via packages. The executable segfaults every time I 
>>> > try
>>> > to run it. This happens with or without command-line options, with my 
>>> > custom
>>> > config file or the default config file. I've tested with two different
>>> > machines, two
>>> > different mirrors, and seen no change.
>>> >
>>> > I've not yet tried building net-snmp from the ports system, but that's
>>> > my next step.
>>> >
>>> > Has anybody else run into this?
>>>
>>> I've seen this, too. But a package made out of the port will work.
>>
>> Repeatable also here. We built net-snmp package from ports.
>>
>> Claer

Reply via email to