When reindexing a device, Graph Automation creates duplicate graphs every time

[vishnubraj]

Describe the bug
Whenever i run the reindex script cacti automation rule create duplicate graphs... If i disable the rule it doesnt happen. Can you please check this.

[hmorandell]

Hi,
I have a similar issue, but only with certain data query types. It seems not to happen with "SNMP - Interface Statistics", but it happens with a couple of my own created data query types
Maybe an error in my templates? Had not yet the time to check it, but it is somehow good to know that I'm not the only one to have such issues...

btw I'm running version 1.2.1

[cigamit]

We need much more information, the rule screen shot would be a good start.

[vishnubraj]

Please find the rule screen shot

[cigamit]

Well, that rule is so strait forward. No reason it should not be working.

[cigamit]

Can you edit the data sources for each of those graphs and see if there is anything funny with the indexes?

[vishnubraj]

Actually i dont see a data source created for this graph.. At the same time for some other graphs for the same template the data source created.. In Automation rules matching objects it still shows the graph has to be created..

[ian351c]

I am seeing the same thing as @vishnubraj in the built-in rule "Traffic 64 bit Server". I also have seen multiple graphs created for the interfaces on the items listed in the "matching objects" list. The duplicate graphs all refer to the same data sources for each device. (So multiple graphs for "eth0" on "Device A" all refer to the same RRD file when I look at the graphs in debug mode).

I'm not sure if this is definitive, but the devices where I'm seeing multiple graphs are devices that I added new data queries/data sources/graphs to AFTER adding the graphs for the interfaces (using 64 bit counters).

[cigamit]

The duplication of the Data Sources should not happen. That is the expected behavior. However, we need to see what is going on with the creation of the second graph.

[cigamit]

This is resolved now. Code was not re-written to handle the fact that Data Sources are no longer duplicated. It was looking at the Data Source and not the graph, so automation broke.