In <user-d804fbff0b62@xymon.invalid> =?iso-8859-1?Q?Johan_Sj=F6berg?= <user-74c177c1220d@xymon.invalid> writes:
I think this is somehow related to oversized status messages. We were havin=
g problems with this on 4.3.0 beta, and we also had a lot of oversized stat=
us messages (ports etc). Since we increased the max message size, we have n=
ot seen the problem with the disk test.
I think I've found this bug. It was quite subtle, and there was a greater
chance of triggering it when you had an oversize message, but it could
also happen without any of them.
I'll commit an update for this later tonight, so it will be included in the
next (beta) release, which I expect to ship sometime next week.
Regards,
Henrik