unusable graph template

[PurpleOfPants]

I'm trying to convert my old 0.6.8 Cacti graphs to 0.8.6 and have only a few strands of hair left. I laboriously created a ping chart (not helped by being unable to edit any field) and finally got it more or less OK for the moment. Since I'm going to use it a bit I converted it to a graph template, and that's where the real trouble starts...

I just can't get a new graph going with this template. First up, I add a new graph and choose this template with 'NONE' for host. On clicking create nothing happens except for this message:

ERROR: invalid rpn expression 'a,0,EQ,NEGINF,UNKN,IF'

Fair enough, I guess it's not going to work until I get a data source in, but I can't do that until I get past this error. I tried creating a host just for this but then ran into the problem of having SNMP go off to look at a non-SNMP host that may or may not exist.

So... I need to get the original graph back from this template so I can just duplicate it as necessary. Is there any way to do this? I might cry if I have to spend another half day recreating it from scratch.

[gandalf]

To get around that rpn error, you may delete the appropriate CDEF from the template (as a workaround).
To get around the snmp error, delete the snmp community string from that device definition and cacti won't ask for it any more.
Reinhard

[PurpleOfPants]

Magic, thanks

Er... except that there are 6 or so CDEFs of varying tediousness (to retype), so I've decided to skip the template stuff and just make copies of a working graph.

[gandalf]

Magic, thanks

Er... except that there are 6 or so CDEFs of varying tediousness (to retype), so I've decided to skip the template stuff and just make copies of a working graph.

Oh, I suppose my statement was not as clear as necessary. I did not ask you to select the CDEF and "clear" it. For sure, you should leave it as is (at the moment). You should only change the Graph Template Item not to use it any more (change the CDEF therein to NONE).
There would be the need to debug this behaviour, but as a workaround, this may help you
Reinhard

[PurpleOfPants]

Duh! I completely misread that, sorry. And it's so obvious now you point it out

Thanks very much for your help.