Ad Widget

Collapse

zabbix_get 3.2.3 unusable due to ZBX-11528

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Pada
    Senior Member
    • Apr 2012
    • 236

    #1

    zabbix_get 3.2.3 unusable due to ZBX-11528

    Since ZBX-11528 has been included in Zabbix 3.2.3, the zabbix_get_jmx script (found at https://www.zabbix.org/wiki/Docs/howto/zabbix_get_jmx) no longer works, which still worked in Zabbix 3.2.2.
    Now I just get the following response with that script:
    Code:
    {"response":"failed","error":"bad protocol header: 7B 22 72 65 71"}
    Where the '7B 22 72 65 71' HEX translates to '{"req' in ASCII.

    I've tried my best to encode the key in binary, but I simply cannot get it to work with zabbix_get app any more, but I did succeed in getting it to work with the standard 'nc' app.

    See my attached zabbix_get_jmx.txt file on how I've encoded the binary <HEADER><DATALEN> fields as documented in https://www.zabbix.com/documentation.../activepassive

    Any ideas on how to make use of zabbix_get now, because I simply cannot manage to pass the \x01 and the datalen binary fields for the '-k' argument...
    Attached Files
    Last edited by Pada; 05-01-2017, 02:43.
  • glebs.ivanovskis
    Senior Member
    • Jul 2015
    • 237

    #2
    Rule #1: don't use undocumented features! :P

    Simply use older version of zabbix_get. Or use another undocumented feature - misc/debug/sender.pl - which sends data with protocol header.

    Comment

    • vishnu.dinoct
      Junior Member
      • May 2017
      • 9

      #3
      Same issue here with that script.

      But this is what the log show. Any thoughts?

      2017-05-07 15:55:05.962 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - sending the following data in response: {"response":"failed","error":"\"bad protocol header: 6A 6D 78 5B 62\""}
      2017-05-07 15:55:05.962 [pool-1-thread-2] DEBUG com.zabbix.gateway.SocketProcessor - finished processing incoming connection
      2017-05-07 15:55:06.067 [pool-1-thread-3] DEBUG com.zabbix.gateway.SocketProcessor - starting to process incoming connection
      2017-05-07 15:55:06.067 [pool-1-thread-3] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading Zabbix protocol header
      2017-05-07 15:55:06.068 [pool-1-thread-3] WARN com.zabbix.gateway.SocketProcessor - error processing request
      com.zabbix.gateway.ZabbixException: bad protocol header: 6A 6D 78 5B 62
      at com.zabbix.gateway.BinaryProtocolSpeaker.getReques t(BinaryProtocolSpeaker.java:59) ~[zabbix-java-gateway-2.2.0.jar:na]
      at com.zabbix.gateway.SocketProcessor.run(SocketProce ssor.java:51) ~[zabbix-java-gateway-2.2.0.jar:na]

      Comment

      • glebs.ivanovskis
        Senior Member
        • Jul 2015
        • 237

        #4
        You may be interested in this feature request and a script attached to it.

        Comment

        • vishnu.dinoct
          Junior Member
          • May 2017
          • 9

          #5
          Originally posted by glebs.ivanovskis
          You may be interested in this feature request and a script attached to it.
          Thank you bro will try that... ( Already few up of this thing

          Comment

          • vishnu.dinoct
            Junior Member
            • May 2017
            • 9

            #6
            "response":"failed","error":"\"java.lang.SecurityE xception: Authentication failed!

            This is what i get when i run the script.
            Any thoughts???

            Thanks..

            Comment

            • vishnu.dinoct
              Junior Member
              • May 2017
              • 9

              #7
              Originally posted by glebs.ivanovskis
              You may be interested in this feature request and a script attached to it.

              "response":"failed","error":"\"java.lang.Secur ityE xception: Authentication failed!

              This is what i get when i run the script.
              Any thoughts???

              Thanks..

              Comment

              Working...