mmonit-3.7.1-linux-x64 throws "500 internal server error" with monit 5.23.0

[Marcus Mülbüsch]

Hello all,

   after upgrade from monit 5.20.0 to 5.23.0 the following test throws 
an error when uploading to mmonit-5.7.1:

> check host somehost with address dns.name.de
>         if failed
>                 port 443 protocol https
>                 and request "/some/URI/log.xml"
>                 with content != 'test="([0-9]|1[0-9]|2[0-4])"\/'
>         then alert

With monit 5.20.0 everything worked fine:

> Jul 28 02:44:23 host monit[9417]: 'somehost' failed protocol test [HTTP] at 
> [dns.name.de]:443/some/URI/log.xml [TCP/IP SSL] -- HTTP error: Regular 
> expression matches

After upgrade to 5.23.0 monit throws:

> Aug  4 12:08:01 host monit[16990]: 'somehost' failed protocol test [HTTP] at 
> [dns.name.de]:443/some/URI/log.xml [TCP/IP TLS] -- HTTP error: Regular 
> expression matches
> Aug  4 12:08:01 host monit[16990]: M/Monit: failed to send message to 
> https://[mmonit]:10445/collector -- HTTP/1.1 500 Internal Server error
> Aug  4 12:08:01 host monit[16990]: M/Monit: event message to 
> https://[mmonit]:10445/collector failed
> Aug  4 12:08:01 host monit[16990]: Adding event to the queue file 
> /var/monit/queue/1501841281_222e240 for later delivery

And mmonit just logs:

> 2017-08-04 12:08:01 NumberFormatException: For input string 
> 18446744073709551615 (src/util/Str.c Str_parseLLong 247) when processing 
> message posted from Monit at host '###.###.###.###' 
> (monitid=7c86ba4557a8fc92f73c3b0e9daea903)

   What happened? mmonit was updated just two days ago; did I forget 
some vital step? However, no other monit client (all of them still at 
5.20.0) shows that behaviour...

Marcus