[Xymon] hobbitd.log and rrd-status.log

[Richard Finegold]

On Wed, Jun 22, 2011 at 21:23, Richard Finegold <goldfndr at gmail.com> wrote:
> On Fri, Jun 17, 2011 at 08:23, Nordquist, Daniel
> <Daniel.Nordquist at orlandohealth.com> wrote:
>> 2011-06-17 11:06:07 RRD error updating
>> /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd from 0.0.0.0:
>> /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd: illegal attempt to
>> update using time 1308323167 when last update time is 1308323167 (minimum
>> one second step)
> [snip]
>> 2011-06-17 11:06:16 RRD error updating
>> /xymon/data/rrd/aserverwehavexoxoDB/disk,ArcData.rrd from 0.0.0.0:
>> /xymon/data/rrd/aserverwehavexoxoDB/disk,ArcData.rrd: illegal attempt to
>> update using time 1308323176 when last update time is 1308323176 (minimum
>> one second step)
>
> Check each column (not just "disk") for these two hosts, make sure
> that you aren't receiving the "disk" data in more than one column, and
> that the table in the "disk" row has unique indexes for each row.
> Also, view source, check if there's a comment in the status that might
> be interepreted as RRD data; try one of these depending on whether you
> have 4.2 or 4.3:
>  bin/bb localhost "hobbitdlog aserverwehavexoxo.disk"
>  bin/xymon localhost "xymondlog aserverwehavexoxo.disk"
>
> grep "=status" and "=data" on your hobbitlaunch.cfg or tasks.cfg, see
> if you're running more RRD collectors that required.
>
> If you're using --extra-tests, see if you're triggering a (redundant) disk rrd.
>
> On the client, temporarily disable the "disk" test, see if the
> status/rrd gets updated elsehow. Check the bottom of the status
> message for the sending host.
>
> Is it just on two hosts, or certain types of host, or all hosts?

On the client, make sure you don't have a display/page recipient more
than once. (e.g. historically two independent BBDISPLAYs but one was
decommissioned and became a CNAME for the other)