Ad Widget

Collapse

Info: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1) ?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • geopard@int.pl
    Junior Member
    • Jun 2024
    • 1

    #1

    Info: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1) ?

    (Zabbix) 7.0.0
    system on which the zabbix server is located:: AlmaLinux release 9.4 (Seafoam Ocelot)

    I monitor the server with the following script, e.g.

    "zabbix_export:
    version: '7.0'
    host_groups:
    - uuid: 4925b447f7df4d8cb88f3041e1e86b85
    name: SERVER
    hosts:
    - host: system
    name: system
    groups:
    - name: SERVER
    httptests:
    - name: system
    attempts: '2'
    steps:
    - name: SystemInfoStandalo
    url: 'google.com/Servlet1'
    follow_redirects: 'NO'
    required: OK
    status_codes: '200'
    - name: MainServlet
    url: 'google2.com/Servlet2'
    query_fields:
    - name: 'wbtsage'
    value: core.start
    - name: logintype
    value: xxx
    follow_redirects: 'NO'
    status_codes: '200'
    inventory_mode: DISABLED
    triggers:
    - expression: 'last(/system/web.test.fail[system])>0'
    name: system_google_test
    priority: HIGH
    dependencies:
    - name: 'High ICMP ping loss'
    expression: 'min(/PING_NASZ/icmppingloss,5m)>{$ICMP_LOSS_WARN} and min(/PING_NASZ/icmppingloss,5m)<100'
    - name: 'High ICMP ping response time'
    expression: 'avg(/PING_NASZ/icmppingsec,5m)>{$ICMP_RESPONSE_TIME_WARN}'
    - name: 'Unavailable by ICMP ping'
    expression: 'max(/PING_NASZ/icmpping,#3)=0'
    "

    When you try to query:
    google.com/Servlet1
    Receives status 200
    And when you try to enter:
    google.com/Servlet2
    receives:
    == Info: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
    I do not know why.
    This is one application and Servlet1 works with 2 and 1.
    And Servlet2 only works with 1.
    When I enter through other browsers, everything works fine.

    How to force the above script for zabbix to be able to enter the server via --http1.1??
Working...