Fixing warnings reported in data sources

[dma_k]

Dear community,

For some of the datasources I have the following message displayed when I open it for editing from "Management → Data Sources":

cacti_1.png (49.47 KiB) Viewed 1495 times

The text of the warning reads "File RRA '0' has same CF/steps (AVERAGE, 1) as '1' File RRA '1' has same CF/steps (AVERAGE, 1) as '0' File RRA '5' has same CF/steps (MAX, 1) as '6' File RRA '6' has same CF/steps (MAX, 1) as '5'". First of all these are 4 different warnings displayed in one line which is difficult to interpret – why cannot it be split into lines? Second it says "A is same as B" and "B is same as A" just repeating the same information. Third is that "same CF/steps" is not so easy to associate with above table because it does not have such columns (is it "PDP per row"?).

How to solve the issue? Can RRA "0" (RRA:AVERAGE:0.5:1:500) and "5" (RRA:MAX:0.5:1:500) be safely removed from RRD using rrdtune?

P.S. I am using Cacti 1.2.16.

[TheWitness]

I would recommend you create a new data source profile and move to it. I recognize the setup and it's from an upgrade situation where a previous template improperly used both 1 minute and 5 minute RRA definitions. You may have to move all your Data Templates to the new profile, and then recreate your Graphs.

[dma_k]

Thanks for your reply. If what you suggest requires manipulations with Data Templates, then I would say this is not the best option for me, because I have about 20 such data sources with warnings, so it would be quite a lot of clicking. And what about the data? I believe it should be exported with rrddump and then imported again... this is sort of equivalent to the effort to fix RRD directly. Or do I miss something? The existing Data Templates could be fixed directly in the database (I hope). What do you think?

As to the displaying of warnings I've checked that the information from rrdtune is just dumped to HTML. I think it would better be wrapped to <pre> like below:

cacti_3.png (18.75 KiB) Viewed 1485 times

If you agree I can create an improvement ticket in Github.