0 Replies Latest reply on Apr 1, 2010 10:05 PM by 843798

    JMX remote management behaving oddly, denying snmp for random machines

      So I use cacti to monitor JVM heap details and so fourth. Here is a section of our java process:
      /usr/java/j2sdk/bin/java -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9003 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.snmp.port=9161 -Dcom.sun.management.snmp.acl.file=/home/svradmin/tomcat/snmp.acl
      So the snmp port is set, auth for jmx is disabled, the acl file is defined. The ACL files on both example machines are the same...everything appears to be the same.

      However, on one machine I get (fail):
      [root@www02 ~]# snmpwalk -c public -v2c localhost:9161
      Error in packet.
      Reason: authorizationError (access denied to that object)
      And on another machine I get (pass):
      [root@www03 ~]# snmpwalk -c public -v2c localhost:9161
      SNMPv2-SMI::mib-2 = No Such Object available on this agent at this OID
      Is there another file somewhere that could be causing this general weirdness? This affects about half of our web cluster, and I can't seem to track down where the problem is.