Ad Widget

Collapse

ActiveMQ JMX monitoring fails with invalid username/pass

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • muelli
    Member
    • Jun 2021
    • 68

    #1

    ActiveMQ JMX monitoring fails with invalid username/pass

    Hello forum,

    I have trouble monitoring an ActiveMQ 5.15.12 DB.
    JMX is activated and the generic JMX template is collecting data, so this part is working.
    However the Zabbix 6.0.7 template "Apache ActiveMQ via JMX" does not work, in the server log I can see errors like this:

    1463827:20230201:090433.123 discovery rule "myserver:jmx.discovery[beans,"org.apache.activemq:type=Broker,brokerName= *"]" became not supported: Invalid username or password

    I checked the user/pass/port data for the Host Macros, they are correct and match with the user/pass/port I have in my generic JMX template.
    Any ideas? What could I check?
    Thanks!
  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4807

    #2
    I'm using https://docs.cyclopsgroup.org/jmxterm to verify such jmx connections (from host, where java gw runs). Kind of eliminate possibility that Zabbix is to blame. If it succeeds, then also Zabbix is happy.. If not, then you should look on the other side, why it does not allow connections...

    Comment

    • muelli
      Member
      • Jun 2021
      • 68

      #3
      Tried this, I can log in from my Zabbix Server and use the activeMQ domain and I can get a list of the beans. So JMX is working...

      Zabbix is failing at
      1463827:20230201:090433.123 discovery rule "myserver:jmx.discovery[beans,"org.apache.activemq:type=Broker,brokerName= *"]" became not supported: Invalid username or password
      ​but using this tool I can get all the brokerNames by hand:

      org.apache.activemq:brokerName=myserver,connector= clientConnectors,connectorName=openwire,type=Broke r
      org.apache.activemq:brokerName=myserver,connector= clientConnectors,connectorName=ssl,type=Broker
      org.apache.activemq:brokerName=myserver,connector= clientConnectors,connectorName=stomp,type=Broker
      org.apache.activemq:brokerName=myserver,destinatio nName=ActiveMQ.DLQ,destinationType=Queue,type=Brok er
      org.apache.activemq:brokerName=myserver,destinatio nName=ExchangeRates,destinationType=Topic,type=Bro ker
      org.apache.activemq:brokerName=myserver,destinatio nName=HGS_Spex,destinationType=Queue,type=Broker
      org.apache.activemq:brokerName=myserver,destinatio nName=HGS_TestQueue,destinationType=Queue,type=Bro ker
      org.apache.activemq:brokerName=myserver,destinatio nName=HGS_TestTopic,destinationType=Topic,type=Bro ker
      org.apache.activemq:brokerName=myserver,instanceNa me=KahaDBPersistenceAdapter[/my_dom/apache-activemq-5.15.12/data/kahadb_Index_/my_dom/apache-activemq-5.15.12/data/kahadb],service=PersistenceAdapter,type=Broker
      org.apache.activemq:brokerName=myserver,service=He alth,type=Broker
      org.apache.activemq:brokerName=myserver,service=Lo g4JConfiguration,type=Broker
      org.apache.activemq:brokerName=myserver,type=Broke r​

      Guess something is wrong with the template?
      Last edited by muelli; 02-02-2023, 11:26.

      Comment

      • muelli
        Member
        • Jun 2021
        • 68

        #4
        Problem is solved!
        The documentation for the template ist WRONG:

        quote:
        Set values in host macros {$ACTIVEMQ.USERNAME}, {$ACTIVEMQ.PASSWORD} and {$ACTIVEMQ.PORT}.

        That is wrong and misinformation, in reality the macro for the username is called "{$ACTIVEMQ.USER}".

        Comment

        Working...