OM / snmpd / smux conflict??

Todd Lyons tlyons at ivenue.com
Fri Jun 22 15:31:07 CDT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Jun 22, 2007 at 03:05:56PM -0400, Peter Larsen wrote:

>I seem to have an issue with snmpd and open manage on a RHEL4
>installation. OM is version 5.2.
>I've seen in the read-me that it's a known issue, and they simply
>recommend restarting snmpd, but that's not helping.
>Problem: smux connect fails.
>snmpd.log: [smux_accept] accepted fd 14 from 127.0.0.1:11292
>refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, password ,
>descr Systems Management SNMP MIB Plug-in Manager
>And I get a lot of those, with different PIDs - about every 1 or 2
>seconds.

So is the problem that the smux is not working for you, or that you get
a message every couple seconds about it?

The fix for the message every couple seconds is to create an
/etc/sysconfig/snmpd.options file and put:
OPTIONS="-LS 4 d -p /var/run/snmpd.pid -a"
  (plus whatever other options you need for your smux to work)
then restart snmpd.

The default cli in the init script uses "-Lsd -Lf/dev/null" for logging,
but that causes a problem with current snmpd (this was first noticed on
a CentOS 4.4 to 4.5 update, so if you've recently updated from U4 to U5,
you're probably seeing it too).
- -- 
Regards...		Todd
  We should not be building surveillance technology into standards.
  Law enforcement was not supposed to be easy.  Where it is easy, 
  it's called a police state.             -- Jeff Schiller on NANOG
Linux kernel 2.6.17-6mdv   2 users,  load average: 0.16, 0.13, 0.13
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGfDGLY2VBGxIDMLwRAhQXAJ98l7/Ygf9oRgP9xTx1JX9WMCjvkACdGby9
+OThGNNIRcn0EIBxnwrtpJ4=
=6wIJ
-----END PGP SIGNATURE-----



More information about the Linux-PowerEdge mailing list