Hi Peter: On Thu, Jul 15, 2010 at 11:30 PM, Peter Jenkins <peter.jenk...@csc.fi> wrote:
> The "Unknown command: -1" errors are interesting ... having used socat > and/or telent to talk to the rrdcached socket, I'd say this is something > minor, perhaps a redundant new line sent from gmetad? This could be a > solaris only bug of course. Anyway the actual functionality seems to be > fine. I don't think it's because of new line, because the error message would've been: Unknown command: The "-1" and "0" in your logs seem to correspond to commands that were passed to rrdcached -- the question is, how did that happen? In gmetad, rrd_update() is called, this gets intercepted by rrdcached. It would be interesting to see the parameters that were passed when you get the error messages. Time to put the debugger to use :-) > This isn't pretty, but it's my command line interpretation of cpu_report: > > rrdtool graph foo.png > DEF:'num_nodes'='/opt/rrd/ganglia/Management/host.csc.fi/cpu_user.rrd':'sum':AVERAGE > DEF:'cpu_user'='/opt/rrd/ganglia/Management/host.csc.fi/cpu_user.rrd':'sum':AVERAGE > CDEF:'ccpu_user'=cpu_user,num_nodes,/ > DEF:'cpu_nice'='/opt/rrd/ganglia/Management/host.csc.fi/cpu_nice.rrd':'sum':AVERAGE > CDEF:'ccpu_nice'=cpu_nice,num_nodes,/ > DEF:'cpu_system'='/opt/rrd/ganglia/Management/host.csc.fi/cpu_system.rrd':'sum':AVERAGE > CDEF:'ccpu_system'=cpu_system,num_nodes,/ > DEF:'cpu_idle'='/opt/rrd/ganglia/Management/host.csc.fi/cpu_idle.rrd':'sum':AVERAGE > CDEF:'ccpu_idle'=cpu_idle,num_nodes,/ AREA:'ccpu_user'#3333bb:'User CPU' > STACK:'ccpu_nice'#ffea00:'Nice CPU' STACK:'ccpu_system'#dd0000:'System CPU' > STACK:'ccpu_idle'#e2e2f2:'Idle CPU' > > Withough rrdcached, I get a graph and the output: 481x162 > > With rrdcached: > > ERROR: rrdc_flush (/opt/rrd/ganglia/Management/host.csc.fi/cpu_nice.rrd) > failed with status -1. I just tested this and it works fine under Linux with rrdcached (at least in my setup). BTW, not sure if you know, but in the web interface, on any graphs, you can right click and choose "View Image" which will give you the exact URL used to generate the graph. If you then add &debug=3 to the URL, you will get the rrdtool command that was used to generate it. Pretty handy for debugging purposes. I think at this point you should post your findings of the 2 issues to the RRDtool mailing-list and see if the developers could help you there. Good luck, and please report back if you have any updates on the issue. Cheers, Bernard ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Ganglia-general mailing list Ganglia-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-general
