I'm setting up a number of windows 2008 and 2012 (64bit) servers with bbwin and am not able to include the evenlog msgs on systems with comparatively large eventlog output - I often get "Data flooding from 1.2.3.4 - 1st line client hostname.domain .bbwin win32" from xymond for multiple hosts, always "1st line client". I'm running xymon 4.3.10. If I remove the msgs collection (msgs.dll) from the bbwin client the problem goes away, but we do need to monitor the event logs.
Just to clarify, I assume the "client" in the "1st line client" part relate to client data, ie the MAXMSG_CLIENT parameter in xymonserver.cfg, is that the case?
Anyway, I ramped up the MAXMSG_DATA, CLIENT and STATUS parameters to 30MB (as a test) in xymonserver.cfg:
# ipcs
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status 0x01034be7 16613376 xymon 600 31457280 2 0x02034be7 16646145 xymon 600 31457280 2 0x03034be7 16678914 xymon 600 31457280 2 0x04034be7 16711683 xymon 600 31457280 2 0x05034be7 16744452 xymon 600 262144 1 0x06034be7 16777221 xymon 600 32768 1 0x07034be7 16809990 xymon 600 31457280 2 0x08034be7 16842759 xymon 600 31457280 2 0x09034be7 16875528 xymon 600 131072 1 With tcpdump I captured one client's output, it totals just under 2MB per upload, so it appears the data flooding is somewhat but not exactly related to the MAXMSG parameters - larger values reduce the frequency of the data flooding errors. Can anyone help with this, please? thanks, Phil