is it a bug ?

[help]

Hi,

when using CDEF function Turn Bytes into Bits, i get this strange error. the graph is missing and the source show this error like

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/httpd/cacti/include/rrd_functions.php on line 591

/usr/local/rrdtool-1.0.40/bin/rrdtool graph - \
--imgformat=PNG \
--start="-86400" \
--title="Traffic Analysis for traf_router_3" \
--rigid \
--base=1000 \
--height=120 \
--width=500 \
--alt-autoscale-max \
--vertical-label="Bytes Per Second" \
DEF:a="/home/httpd/cacti/rra/traf_router_3_in.rrd":traf_router_3_:AVERAGE \
DEF:b="/home/httpd/cacti/rra/traf_router_3_out.rrd":traf_router_3_:AVERAGE \
CDEF:cdefc= \
AREA:a#00CF00:"Inbound" \
GPRINT:a:AVERAGE:" Average\:%8.2lf %s" \
\ --> {the missing record}
GPRINT:a:MAX:"Maximum\:%8.2lf %s\n" \
LINE1:b#002A97:"Outbound" \
GPRINT:b:LAST:"Current\:%8.2lf %s" \
GPRINT:b:AVERAGE:"Average\:%8.2lf %s" \
GPRINT:b:MAX:"Maximum\:%8.2lf %s"

some records are missing from mysql database. the same thing happens when i applied the cdef function into another record like MAX and CURRENT or AVERAGE from inbound and outbound.

i'm using cli version of php (there are a lot of warning about include path for the first time, but it's solved by cd into cacti directory.

any suggestion please ??

[Andre]

I got this error message after a table got corrupted because of a full disk. It might be related, my corrupt table was src_data. I fixed it with the commandline tool myisamcheck. Could you post your version of MySQL and PHP please ? I get related errors after upgrading to PHP 4.3.0 and MySQL 3.23.54a .

[Help]

php version is 4.2.1 with configure line

'./configure' '--with-mysql=/usr/local/' '--with-imap=/usr/local/src/imap-4.7/' '--with-apxs=/var/lib/apache/sbin/apxs' '--with-gd=/usr/local' '--with-png-dir=/usr/local' '--with-zlib-dir=/usr/local' '--with-jpeg-dir=/usr' '--with-png' '--enable-cli' '--with-snmp' '--enable-ucd-snmp-hack'

and mysql is 3.22.32

[Help]

problem's solved.
the "wrong thing" is that mysql-3.22 that i used had not support "case" in the query syntax.
with mysql-3.23, it runs well.

thx andre. u give me the idea.