[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xymon] Client data corruption
- To: xymon (at) xymon.com
- Subject: Re: [xymon] Client data corruption
- From: Colin Coe <colin.coe (at) gmail.com>
- Date: Mon, 8 Nov 2010 20:05:44 +0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=lUcks8lDL8rdJq3OSpjmhg9JEiL54xaZ8AccnIdClOw=; b=AISvdRED+5Uubg2mrFSs0xuC/lGIphReE7QHOD6f6PQ1Bqh7tdST37eqeB+0pkJMJC X2oXTqoHDviarcE1Y3BLowDTfbuJRhII0b7zyCwAhc8QIZ5uuECf2yIf2vKEr0SssMcg fmHjaSC8Owe2wgi3Cvb4OTXoe3lzKKk57wsxs=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Ff/Vk1YjdGMdihsPkCTQ7ZsdQERQtQ2Vqq3enc/x8dLlpX02echVYWjWEk8d+7Lmhj 0924FNav6MVSae13gT12trLHKG6rZVkG/d2+6d4stYaH0XTh4RCjiTedOhIv3E1K4Fw9 QGQBiWIMIslQmVPVhAbQ1C+IbcT+oIprQkv34=
- References: <AANLkTik_ETDf0gvSi17GoOkuaTWt07U8Mo1ARbfbw0NS (at) mail.gmail.com> <ib84u3$8s5$1 (at) voodoo.hswn.dk>
On Mon, Nov 8, 2010 at 2:21 PM, Henrik Størner <henrik (at) hswn.dk> wrote:
> In <AANLkTik_ETDf0gvSi17GoOkuaTWt07U8Mo1ARbfbw0NS (at) mail.gmail.com> Colin Coe <colin.coe (at) gmail.com> writes:
>
>>I'm seeing occasional corruption in the data being sent from clients
>>to Xymon server. For example:
>>---
>>red Mon Nov 8 08:00:08 WST 2010 - Filesystems NOT ok
>>&red 281121212 29% / (112686548% used) has reached the PANIC level (95%)
>>&red 55500 43% /boot (40367% used) has reached the PANIC level (95%)
>
>>Filesystem 1024-blocks Us
>>d A]ailable Capacity Mounted on
>>/dev/mapper/VolGroup00-LogVol00 414880744 112686548 281121212 29% /
>>/dev/cciss/c0d0p1 101086 40367 55500 43% /boot
>>---
>
>>I've also seen this happen with the 'services' data from Windows clients.
>
>>I'm using 'Xymon 4.3.0-0.beta2'.
>
>>Has anyone else seen this?
>
>
> Known bug in beta2. Fixed in the code currently in the Subversion
> archive at Sourceforge.
>
>
> Regards,
> Henrik
>
Then I eagerly await beta3 :)
Thanks
CC
--
RHCE#805007969328369