Log from GENERIC protocol test breaks M/Monit

[twm]

I'm using the generic send/expect test to test a service running on a binary protocol. The test works. However, when the received data doesn't match, the binary data will be provided as "context" (see issue #335) in the log file and in the message to M/Monit. Unfortunately this breaks M/Monit in the following way:

• I'm expecting a binary string ending in 0x01 0x02 0x03.
• I'm receiving a string ending in 0x01 0x01 0x01.
• Monit detects the mismatch and logs failed protocol test [generic] at [localhost]:9066 [TCP/IP] -- GENERIC: received unexpected data [XXX] with XXX being three unreadable characters that hexdump translates to 0x01 0x01 0x01.
• M/Monit immediately shows an error dialogue.
• M/Monit no longer displays the eventlog until the message containing the binary data is manually cleared from the database.

Unfortunately I don't have the exact messages from M/Monit available and I'd rather not try to reproduce this error as this is our production system.

Environment: Ubuntu 16.04 LTS with Monit 5.20.0, Ubuntu 14.04 LTS with M/Monit 3.6.2

[Tildeslash]

Hello,

this problem is fixed in the upcoming M/Monit 3.7.0 release (should be available within 1 week).