Snmpd problem was Re: Dell OMSA 5.2 installed into /tmp... not /opt/dell

Richard Chan rspchan at starhub.net.sg
Thu Apr 19 05:09:18 CDT 2007


Reinstalled the same package and OMSA ended up in /opt/dell. Weird.

However now I'm getting an snmpd problem; I've added the smux peer line 
to /etc/snmp/snmpd.conf
but am receiving

error on subcontainer 'ia_addr' insert (-1)
error on subcontainer '' insert (-1)

at 30sec intervals. Any ideas?

Michael E Brown wrote:
> On Wed, Apr 18, 2007 at 08:27:40PM +0800, Richard Chan wrote:
>   
>> My OMSA 5.2 installation on a PE6950/CentOS 5-x86_64 ended up in 
>> /tmp/dellupdatepackage-hapi.....
>>
>> Is this correct behaviour for OMSA 5.2? (downloaded from  Drivers & 
>> Download not any of the yum
>> repositories). I was expecting it to go into /opt./dell as did OMSA 5.0 
>> on my PE2850/CentOS4U4-x86_64.
>>     
>
> You got into a really wierd situation here. How did you install? Looks
> like somehow the wrong RPMs were installed. There are several different
> versions of the "srvadmin-ipmi" RPM, one for each OS, in order to pull
> in the correct dependency on OpenIPMI. There is also a srvadmin-ipmi RPM
> for DUPs, which is a dummy RPM that has no dependencies.
>
> Looks like you have the DUP srvadmin-ipmi RPM installed rather than the
> one for RHEL5, which is what you need.
>
> BTW, if you use the yum repo, this cannot happen. :)
> --
> Michael
>   



More information about the Linux-PowerEdge mailing list