[Xymon] Sudden rash of "logfetch" crashes in libc on RHEL 6 Linux?!?

[Greg Earle]

Starting about 45 minutes ago as I type this, all of a sudden, 5 of
my machines running Xymon 4.3.17 have gotten afflicted with a mysterious
'disease' - "logfetch" is endlessly crashing on all of them.

The core files being created are getting corrupted for some reason,
and they are magically getting deleted as a result, so I can't debug
the problem.

One machine is running 64-bit RHEL 6.5; the rest 64-bit RHEL 6.3.  Client
version is as I mentioned 4.3.17:

xymon-client-4.3.17-1.el6.x86_64

This cycle is getting repeated every 1 minute and 40 seconds - help!

Oct 20 15:42:42 linux1 kernel: logfetch[2334]: segfault at ef ip 000000355a4c835f sp 00007fff0ac56a80 error 6 in libc-2.12.so[355a400000+189000]
Oct 20 15:42:42 linux1 abrt[2335]: //core.2334 fd(-1) is not a regular file with link count 1: Permission denied
Oct 20 15:42:43 linux1 abrt[2335]: Saved core dump of pid 2334 (/usr/bin/logfetch) to /var/spool/abrt/ccpp-2014-10-20-15:42:42-2334 (335872 bytes)
Oct 20 15:42:43 linux1 abrtd: Directory 'ccpp-2014-10-20-15:42:42-2334' creation detected
Oct 20 15:42:43 linux1 abrtd: Package 'xymon-client' isn't signed with proper key
Oct 20 15:42:43 linux1 abrtd: 'post-create' on '/var/spool/abrt/ccpp-2014-10-20-15:42:42-2334' exited with 1
Oct 20 15:42:43 linux1 abrtd: Corrupted or bad directory /var/spool/abrt/ccpp-2014-10-20-15:42:42-2334, deleting

I doubt that "libc" got simultaneously corrupted on all 5 systems so
there must be something wrong in "logfetch".  The segfault ip is always
"000000355a4c835f" on the 4 RHEL 6.3 systems while the stack pointer varies.

	- Greg

P.S. Why am I getting these "isn't signed with proper key" messages as well?