[rrd-developers] rrdcache Update success response..

Steve Shipway s.shipway at auckland.ac.nz
Mon Nov 1 19:51:23 CET 2010

This is not actually a complete success message, a complete success doesnt have the 'errors,' prefix.  The initial '0' is the status code -- 0 for "OK,no more lines follow".

The 'errors, enqueued' message is a 'partial success' message; possibly it thinks you sent two values and only one was correctly enqueued (check for multiple or trailing spaces in the command you sent which could be taken as a badly-formatted value)


Steve Shipway
University of Auckland ITS
UNIX Systems Design Lead
s.shipway at auckland.ac.nz
Ph: +64 9 373 7599 ext 86487

From: rrd-developers-bounces+steve=steveshipway.org at lists.oetiker.ch [rrd-developers-bounces+steve=steveshipway.org at lists.oetiker.ch] on behalf of Shaun Reitan [mailinglists at unix-scripts.com]
Sent: Tuesday, 2 November 2010 7:36 a.m.
To: rrd-developers at lists.oetiker.ch
Subject: [rrd-developers] rrdcache Update success response..

On a successful update you get the following response.

     0 errors, enqueued 1 value(s).

The problem i see with this response is that if you carve up the
response using perl (or any other language) using a whitespace as a
delimiter you will end up with the following...

        status = 0
        message = errors, enqueued 1 value(s).

The problem i see here with this response is that the message indicates
there was errors even though i think what it's really trying to say was
0 errors.  The response should probably really say

0 0 errors, enqueued 1 value(s).
0 no errors, enqueued 1 value(s).

maybe this is a bug?

Shaun Retian
Chief Technical Officer
Network Data Center Host, Inc.

rrd-developers mailing list
rrd-developers at lists.oetiker.ch

More information about the rrd-developers mailing list