On Tuesday 05 March 2013, user-87556346d4af@xymon.invalid wrote:
(If there's one specific host that's got a pathological value in
there, you can hack xymonclient-${os}.sh manually to keep from
gathering it, without affecting anything that doesn't depend on
that raw data.)
Thanks, it works I seems.
If it's the size of the actual file left on disk
Size of one file on client's disk is not important... But it is
collected in /var/lib/xymon/hostdata... Is this used for xymon
or is it for manual diagnosis later ?
And it all started with a log messages:
xymonclient.log:
2013-03-05 17:47:37 Whoops ! Failed to send message (write error)
2013-03-05 17:47:37 -> Write error while sending message to Xymon daemon at 127.0.0.1:1984
2013-03-05 17:47:37 -> Recipient '127.0.0.1', timeout 15
2013-03-05 17:47:37 -> 1st line: 'client <host>.linux linux'
xymond.log:
2013-03-05 17:47:37 Data flooding from 127.0.0.1 - 1st line client <host>.linux linux
:-)
BTW, ifconfig is obsolete in linux now, what about change it to
"ip -s link" and "ip addr" ?
And /sbin/ifconfig called twice in xymonclient-linux.sh:
echo "[ifconfig]"
/sbin/ifconfig
echo "[ifstat]"
/sbin/ifconfig
--
Regards,
Sergey