Ad Widget

Collapse

Erro "Cannot parse list of active checks"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • emnavarro02
    Junior Member
    • Mar 2021
    • 11

    #1

    Erro "Cannot parse list of active checks"

    Olá,

    Estou tentando fazer o set up do Zabbix na versão 5.2.5 no meu ambiente. Eu instalei o servidor usando a Docker image oficial disponivel aqui.

    Além disso, instalei o Zabbix agent versão 5.2.5 em um Windows Server 2019 e configurei o arquivo zabbix_agentd.conf da seguinte manteira:
    Code:
    LogFile=C:\Program Files\zabbix\zabbix_agentd.log
    
    Server=127.0.0.1
    ListenIP=127.0.0.1
    ServerActive=my-zabbx-server.com
    DebugLevel=5
    Hostname=My-HOSTNAME
    HostMetadata=_WIN_
    Timeout=30
    A partir do servidor onde tenho o Zabbix agent consigo conectar no meu Zabbix server na porta 10051 (telnet) e acessar a URL para administração do servidor.

    No entanto, quando tento inicio o serviço Zabbix Agent no cient, posso ver seguinte error no zabbix_agentd.log do client:

    Code:
    1596:20210317:142551.715 sending [{"request":"active checks","host":"My-HOSTNAME","host_metadata":"_WIN_","ip":"127.0.0.1"}]
    1596:20210317:142551.715 before read
    1596:20210317:142551.741 got [HTTP/1.1 400 BAD_REQUEST
    Content-Length: 0
    Connection: Close
    
    ]
    
    1596:20210317:142551.741 In parse_list_of_checks()
    1596:20210317:142551.742 cannot parse list of active checks: cannot parse as a valid JSON object: invalid object format, expected opening character '{' at: 'HTTP/1.1 400 BAD_REQUEST
    Content-Length: 0
    Connection: Close

    Pelo que em alguns posts antigos aqui no Fórum, esse problema parece estar relacionado com a versão do agente do Zabbix (que deveria ser a mesma versão do Zabbix server). Então, no cliente eu instalei a versão 5.2.5 do agente, mas o erro ocorre com agentes na versão 3.0.0 e 4.0.0.

    Além disso, quando eu removo a linha "ServerActive" do arquivo zabbix_agentd.conf, o problema desaparece, mas o agente não se auto-registra no Zabbix server e, portanto, não consigo monitora-lo.

    Alguém conseguiria me ajudar com essa questão?
  • mfortes
    Senior Member
    • Oct 2019
    • 415

    #2
    Então,
    Se o agent estiver EXATAMENTE como oque você escreveu, então esta incorreto... Visto que o server e o active server devem ser o endereço IP do servidor Zabbix.
    Para o Active server funcionar, o HOSTNAME deve estar IGUAL ao nome cadastrado no hostname dentro do zabbix via web... Se forem diferentes, não vai funcionar


    Michael R. Fortes

    Linkedin: Mike Fortes
    Medium: mromeiro-f

    Comment

    • emnavarro02
      Junior Member
      • Mar 2021
      • 11

      #3
      Oi mfortes , muito obrigado por sua ajuda.

      No Zabbix server há uma regra de Auto Registration que deveria criar os hosts automaticamente. Em todo caso, eu criei esse host manualmente, conforme você sugeriu.

      Eu também alterei a configuração do arquivo zabbix_agentd.conf conforme você sugeriu, mas infelizmente o problema continua:
      Code:
      LogFile=C:\Program Files\zabbix\zabbix_agentd.log
      
      Server=my-zabbx-server.com
      ListenIP=127.0.0.1
      DebugLevel=4
      ServerActive=my-zabbx-server.com
      Hostname=My-HOSTNAME
      HostMetadata=_WIN_
      Timeout=30
      Eu não tenho certeza se a questão dos parâmetros Server e ServerActive serem diferentes é o que está causando o problema, porque tenho diversos hosts com essa configuração em um outro ambiente Zabbix 3.4.

      Durante o troubleshooting eu reinstalei o Zabbix Agent. Aqui está o log completo quando tento iniciar o serviço do Zabbix Agent (Modifiquei apenas os nomes do Zabbix server e do Client).
      Code:
      6056:20210318:073415.851 Starting Zabbix Agent [My-HOSTNAME]. Zabbix 5.2.5 (revision 1afd0ded11).
      6056:20210318:073415.851 **** Enabled features ****
      6056:20210318:073415.852 IPv6 support: YES
      6056:20210318:073415.852 TLS support: YES
      6056:20210318:073415.853 **************************
      6056:20210318:073415.854 using configuration file: C:\Program Files\zabbix\conf\zabbix_agentd.conf
      6056:20210318:073415.855 In init_collector_data()
      6056:20210318:073415.855 logical CPU count 2
      6056:20210318:073415.856 End of init_collector_data()
      6056:20210318:073415.857 In init_perf_collector()
      6056:20210318:073415.859 In init_builtin_counter_indexes()
      6056:20210318:073415.860 In get_all_counter_names()
      6056:20210318:073415.929 End of get_all_counter_names()
      6056:20210318:073416.050 End of init_builtin_counter_indexes():SUCCEED
      6056:20210318:073416.051 In set_object_names()
      6056:20210318:073416.411 In get_all_counter_names()
      6056:20210318:073416.414 End of get_all_counter_names()
      6056:20210318:073416.414 In get_all_counter_names()
      6056:20210318:073416.417 End of get_all_counter_names()
      6056:20210318:073416.496 End of set_object_names():SUCCEED
      6056:20210318:073416.497 End of init_perf_collector():SUCCEED
      6056:20210318:073416.515 OpenSSL library (version OpenSSL 1.1.1g 21 Apr 2020) initialized
      6056:20210318:073416.515 agent #0 started [main process]
      5288:20210318:073416.516 agent #1 started [collector]
      1268:20210318:073416.517 agent #2 started[listener #1]
      6980:20210318:073416.517 agent #3 started[listener #2]
      4428:20210318:073416.518 agent #5 started [active checks #1]
      6092:20210318:073416.518 agent #4 started[listener #3]
      5288:20210318:073416.519 In init_cpu_collector()
      1268:20210318:073416.519 In zbx_tls_init_child()
      6980:20210318:073416.519 In zbx_tls_init_child()
      4428:20210318:073416.521 In zbx_tls_init_child()
      6092:20210318:073416.522 In zbx_tls_init_child()
      5288:20210318:073416.522 In get_counter_name() pdhIndex:238
      1268:20210318:073416.523 End of zbx_tls_init_child()
      6980:20210318:073416.523 End of zbx_tls_init_child()
      4428:20210318:073416.524 End of zbx_tls_init_child()
      6092:20210318:073416.524 End of zbx_tls_init_child()
      5288:20210318:073416.524 End of get_counter_name():SUCCEED
      4428:20210318:073416.525 In init_active_metrics()
      5288:20210318:073416.525 In get_counter_name() pdhIndex:6
      4428:20210318:073416.526 buffer: first allocation for 100 elements
      5288:20210318:073416.526 End of get_counter_name():SUCCEED
      4428:20210318:073416.527 End of init_active_metrics()
      5288:20210318:073416.527 In add_perf_counter() counter:'\Processor(_Total)\% Processor Time' interval:900
      4428:20210318:073416.528 In send_buffer() host:'my-zabbx-server.com' port:10051 entries:0/100
      5288:20210318:073416.528 add_perf_counter(): PerfCounter '\Processor(_Total)\% Processor Time' successfully added
      4428:20210318:073416.529 End of send_buffer():SUCCEED
      5288:20210318:073416.529 End of add_perf_counter(): SUCCEED
      4428:20210318:073416.529 In refresh_active_checks() host:'my-zabbx-server.com' port:10051
      5288:20210318:073416.530 In add_perf_counter() counter:'\Processor(0)\% Processor Time' interval:900
      5288:20210318:073416.531 add_perf_counter(): PerfCounter '\Processor(0)\% Processor Time' successfully added
      5288:20210318:073416.531 End of add_perf_counter(): SUCCEED
      5288:20210318:073416.532 In add_perf_counter() counter:'\Processor(1)\% Processor Time' interval:900
      5288:20210318:073416.532 add_perf_counter(): PerfCounter '\Processor(1)\% Processor Time' successfully added
      5288:20210318:073416.533 End of add_perf_counter(): SUCCEED
      5288:20210318:073416.533 In get_counter_name() pdhIndex:2
      5288:20210318:073416.534 End of get_counter_name():SUCCEED
      5288:20210318:073416.534 In get_counter_name() pdhIndex:44
      5288:20210318:073416.535 End of get_counter_name():SUCCEED
      5288:20210318:073416.535 In add_perf_counter() counter:'\System\Processor Queue Length' interval:900
      5288:20210318:073416.537 add_perf_counter(): PerfCounter '\System\Processor Queue Length' successfully added
      5288:20210318:073416.538 End of add_perf_counter(): SUCCEED
      5288:20210318:073416.538 End of init_cpu_collector():SUCCEED
      5288:20210318:073416.539 In collect_perfstat()
      5288:20210318:073416.540 End of collect_perfstat()
      [B]4428:20210318:073416.585 sending [{"request":"active checks","host":"My-HOSTNAME","host_metadata":"_WIN_","ip":"127.0.0.1" }]
      4428:20210318:073416.585 before read
      4428:20210318:073416.610 Message from my-zabbx-server.com is missing header. Message ignored.[/B]
      [B]4428:20210318:073416.610 active check configuration update from [my-zabbx-server.com:10051] started to fail ()[/B]
      4428:20210318:073416.611 End of refresh_active_checks():FAIL
      4428:20210318:073416.611 In process_active_checks() server:'my-zabbx-server.com' port:10051
      4428:20210318:073416.612 End of process_active_checks()
      4428:20210318:073416.612 In get_min_nextcheck()
      4428:20210318:073416.612 End of get_min_nextcheck():-1
      5288:20210318:073417.541 In collect_perfstat()
      5288:20210318:073417.543 End of collect_perfstat()
      4428:20210318:073417.613 In send_buffer() host:'my-zabbx-server.com' port:10051 entries:0/100
      4428:20210318:073417.614 End of send_buffer():SUCCEED
      5288:20210318:073418.544 In collect_perfstat()
      5288:20210318:073418.546 End of collect_perfstat()
      4428:20210318:073418.615 In send_buffer() host:'my-zabbx-server.com' port:10051 entries:0/100
      Eu encontrei alguns posts aqui no fórum sobre esse erro (ex.: https://www.zabbix.com/forum/zabbix-...essage-ignored) e também esse link na documentação oficial (https://www.zabbix.com/documentation...otocol_dropped), mas confesso que não entendi como implementar os headers no agente. Alguém consegue me dar uma luz?

      Obrigado novamente

      --
      emnavarro02

      Comment

      • Hernandes Martins
        Senior Member
        Zabbix Certified SpecialistZabbix Certified Professional
        • Apr 2011
        • 900

        #4
        Olá meu caro,

        Remove a opção Listenip


        Server=Endereço do Zabbix Server ou Zabbix Proxy
        #ListenIP=127.0.0.1
        __

        Att.
        Hernandes Martins - Zabbix Trainer

        Zabbix Brazil Partner - www.luniobr.com

        Zabbix Brazil Community - www.zabbixbrasil.org

        Blog: hernandesmartins.blogspot.com.br

        Skype: hernandss
        Telegram: @MrHernandes

        Español
        Facebook: facebook.com/groups/zabbixlatam
        Telegram: https://t.me/ZabbixEspañol

        Português
        Facebook: facebook.com/groups/zabbixbrasil/
        Telegram: https://t.me/ZabbixBrasil

        Comment

        • emnavarro02
          Junior Member
          • Mar 2021
          • 11

          #5
          Oi Hernandes Martins ,

          Obrigado por sua sugestão. Eu removi o ListenIP do arquivo, mas o continuou.

          Não tenho muita ideia de como continuar aqui... Não encontro nos logs do servidor nenhuma informação relevante. :-(

          Comment

          • emnavarro02
            Junior Member
            • Mar 2021
            • 11

            #6
            Olá pessoal, apenas para documentação futura, eu consegui resolver o problema.

            Ele estava relacionado com o certificado utilizado para comunicação entre o servidor Zabbix e os clients. No meu caso havia Application Load Balancer (HTTP) entre os clientes e o Zabbix server. Esse application load balancer estava fazendo a SSL/TLS termination, o que atrapalhava a comunicação entre os clientes e o servidor Zabbix.

            Eu modifiquei o Load Balancer para um Network Load Balancer (TCP) de modo que o SSL/TLS temination ocorre agora no Zabbix server. Além disso, eu distribuí o certificado da RootCA que emiitu o certificado do servidor Zabbix para os clients.

            Espero que ajude alguém no futturo. Obrigado a todos pela ajuda.

            Abraços!

            Comment

            Working...