Ad Widget

Collapse

Since 6.4.6 (containers) lots of "zabbix docker failed to fetch info data"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • d0d0
    Member
    • May 2023
    • 41

    #1

    Since 6.4.6 (containers) lots of "zabbix docker failed to fetch info data"

    I recently upgraded to 6.4.6 (all components) but I am seeing a log of "zabbix docker failed to fetch info data" since a few days for several hosts. Is this a known issue with 6.4.6? I didn't have these with 6.4.4. I am using the official docker containers.
  • d0d0
    Member
    • May 2023
    • 41

    #2
    I went back to 6.4.5 for the server container and the problem is gone. Clearly has to do with the 6.4.6 server container

    Comment

    • cyber
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Dec 2006
      • 4807

      #3
      If you think you have found a bug or defect, you can rise a ticket here https://support.zabbix.com/browse/ZBX

      Comment

      • d0d0
        Member
        • May 2023
        • 41

        #4
        I now believe that it has nothing to do with 6.4.6. It seems that the cause was elsewhere, but I do not understand the actual causal relation. On the same host where the Zabbix-server is running I also have a syslog-ng server. I had a missing ";" in the syslog-ng config file after some testing, so syslog-ng was not actually running. I have no idea why that would impact Zabbix that much.

        Comment

        • d0d0
          Member
          • May 2023
          • 41

          #5
          That also was not the problem.. my current theory is that it is a performance problem with the Zabbix server, no ides why that started abruptly at some point in time. I will open another post for the performance issue.

          Comment

          • Baileykemp
            Junior Member
            • Sep 2023
            • 3

            #6
            It's also a good idea to review your Docker configurations, ensure network connectivity, and verify if any changes were made to your setup during the upgrade that might be causing this issue.

            Comment

            Working...