HTTP error: invalid chunk size when checking content

Issue #1004 duplicate
Matt McNeil created an issue

With no changes for many months to the monit config, and I don’t think any meaningful changes to the web content or web server, Monit 5.26 (on Ubuntu 20) a monit check just started failing with these errors:

[UTC Oct  3 04:22:29] error    : 'example-website' failed protocol test [HTTP] at [www.example.org]:443 [TCP/IP TLS] -- HTTP error: invalid chunk size: nt="2021
[UTC Oct  3 04:23:31] error    : 'example-website' failed protocol test [HTTP] at [www.example.org]:443 [TCP/IP TLS] -- HTTP error: invalid chunk size: tent="20
[UTC Oct  3 04:24:32] error    : 'example-website' failed protocol test [HTTP] at [www.example.org]:443 [TCP/IP TLS] -- HTTP error: invalid chunk size: te" cont
[UTC Oct  3 04:25:34] error    : 'example-website' failed protocol test [HTTP] at [www.example.org]:443 [TCP/IP TLS] -- HTTP error: invalid chunk size: te" cont
[UTC Oct  3 04:26:36] error    : 'example-website' failed protocol test [HTTP] at [www.example.org]:443 [TCP/IP TLS] -- HTTP error: invalid chunk size: te" cont
[UTC Oct  3 04:27:37] error    : 'example-website' failed protocol test [HTTP] at [www.example.org]:443 [TCP/IP TLS] -- HTTP error: invalid chunk size: te" cont

Here is the previously working config:

check host example-website with address www.example.org
  # http
  if failed
    port 80
    protocol http

    status = 301
    with timeout 5 seconds
    for 3 times within 5 cycles then alert

  if failed
    port 443
    protocol https
        with timeout 5 seconds

   content = "Example"

    # certbot should auto-renew certificate when expiration date is within 30
    # days of current date. allow a few days
    with certificate valid > 27 days

    for 3 times within 5 cycles then alert

However if I comment out the `content = ` line, then the test immediately begins passing again. The content that is being searched for definitely (“Example”) appears in the HTTP response and is readily matched with curl and grep.

Does anyone have any idea what might be going on? Could it be related to https://bitbucket.org/tildeslash/monit/issues/254/hosts-check-is-too-long ?

Thanks for any help,

Matt

Comments (2)

  1. Log in to comment