Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-20228

active check configuration update from started to fail (SSL_write() timed out)

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • 5.0.17, 5.4.7
    • Agent (G)
    • Client operating system: Windows 10 Pro 21H1 Build 19043.1348
      Client hardware: Lenovo X1 Carbon and Lenovo ThinkBook 13S G2 ITL

      Server: Zabbix Server 5.0.16 on Ubuntu 18.04 LTS
    • Sprint 85 (Feb 2022)
    • 2

      We use the Zabbix agent with over 300 clients secured by TLS with pre-shared key. With approx. 30 new devices we get the following error.

      Zabbix Agent:

      active check configuration update from [monitoring.example.com:10051] started to fail (SSL_write() timed out)
      

      Zabbix Server:

      failed to accept an incoming connection: from 123.123.123.123: TLS handshake set result code to 1: file ../ssl/t1_lib.c line 2589: error:14201076:SSL routines:tls_choose_sigalg:no suitable signature algorithm: TLS write fatal alert "handshake failure"
      

       

      The configuration is identical to devices on which the same configuration works.

      The problem exists with Zabbix Agent 5.0.14 installed via Chocolatey, 5.0.17 manually installed (MSI with OpenSSL) as well as with 5.4.7 manually installed (MSI with OpenSSL).

      We also tested it with Zabbix Server 5.4.7 and Zabbix Agent 5.4.7, with the same result.

      It only works with Zabbix Agent 2 on these clients with identical configuration.

       

      We are happy to provide further information that will help to identify the problem or to give access to one of the devices for debugging purposes, e.g. via TeamViewer.

       

      In the forum someone has the same problem: https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/424646-how-to-solve-problem-active-check-update-from-started-to-fail-ssl_write-timed-out

       

      Zabbix Agent logs with DebugLevel=5 and configuration files attached.

        1. drmemory.txt
          44 kB
          Pah
        2. Screenshot_20211130_105051.png
          19 kB
          Pah
        3. Screenshot_20211130_105107.png
          18 kB
          Pah
        4. Screenshot 2021-11-23 at 09.23.38.png
          526 kB
          Edgar Akhmetshin
        5. Screenshot 2021-11-23 at 09.24.28.png
          503 kB
          Edgar Akhmetshin
        6. zabbix_agentd.conf
          15 kB
          Pah
        7. zabbix_agentd.log
          8 kB
          Pah
        8. zabbix_agentd-10.log
          2.85 MB
          Pah
        9. zabbix_agentd-2.log
          16 kB
          Pah
        10. zabbix_agentd-3.0.32.log
          17 kB
          Pah
        11. zabbix_agentd-3.log
          15 kB
          Pah
        12. zabbix_agentd-4.log
          16 kB
          Pah
        13. zabbix_agentd-5.0.19.log
          19 kB
          Pah
        14. zabbix_agentd-5.0.21rc1.log
          31 kB
          Pah
        15. zabbix_agentd-5.log
          14 kB
          Pah
        16. zabbix_agentd-6.log
          18 kB
          Pah
        17. zabbix_agentd-7.log
          77 kB
          Pah
        18. zabbix_agentd-8.log
          812 kB
          Pah
        19. zabbix_agentd-drmemory.log
          193 kB
          Pah
        20. zabbix_server.conf
          23 kB
          Pah
        21. zabbix-5.0.19.OpenSSL-3.0.1-windows-amd64.tgz
          4.77 MB
          Andris Mednis
        22. ZBX-20228-5.0.diff
          2 kB
          Vladislavs Sokurenko

            vso Vladislavs Sokurenko
            pah Pah
            Team A
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: