Ad Widget

Collapse

"error":"Failed response parse. Check debug log for more information." in AWS by HTTP

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • northernpit
    Junior Member
    • Feb 2023
    • 1

    #16
    I had similar error (Cannot find the "data" array in the received JSON object.), and it turn out it was because of I enter AWS region {$AWS.REGION} wrong. I was using eu-central-1c(with "c" in the end), and correcting to eu-central-1solve issue for my instalation.

    Comment

    • Snowflake71
      Junior Member
      • Apr 2023
      • 1

      #17
      Originally posted by fabreg
      hi oscar ,
      here's the log:


      Code:
      [ AWS EC2 ] Sending request: https://ec2.<zone>.amazonaws.com/?Action=DescribeInstances&Version=2016-11-15
      Code:
      [ AWS EC2 ] Received response with status code 200: <?xml version="1.0" encoding="UTF-8"?>
      <DescribeInstancesResponse xmlns="http://ec2.amazonaws.com/doc/2016-11-15/">
      <requestId>a45434a-8442-38v5-6ddc-153ad10d02a3</requestId>
      <reservationSet>
      <item>
      ...
      Then a list of instances is created (I cannot paste there cause it contains sensible data)
      I have many instances (around 80)

      And, the last line is:

      Code:
      4038408:20230208:104406.397 [ AWS EC2 ] ERROR: Failed response parse. Check debug log for more information.
      4038408:20230208:104406.397 zbx_es_execute() output:'{"error":"Failed response parse. Check debug log for more information."}'

      ​This is the same error I get when I try to use the LLD test rules.

      Thank you!

      I have the same issue. Just for testing purposes, I created a single instance in a previously empty zone and there it works nicely, zabbix immediately picked up that one.
      Did you or anybody had some luck with figuring out where the parse may fail exactly?
      In the faulty zone, all instances are tagged, all of them have populated names, etc, but the same result. I checked the returned xml for errors, it's clean and lean, no issues, still I get the parse error.

      Comment

      • fabreg
        Junior Member
        • Feb 2023
        • 3

        #18
        I think you can track directly the bug: https://support.zabbix.com/browse/ZBX-22327

        Comment

        Working...