cacti exporting all graphs after upgrade?

monachus · Post by **monachus** » Wed Mar 03, 2010 5:22 pm

upgraded to 0.8.7e today and now cacti exports _everything_ no matter whether it's configured to or not. it sent load up to > 50 and created massive gaps in every other graph.

i've been prowling around in the code and the database but am unable to find what criteria the code looks for to determine if a graph should be exported. i see that in graph_templates_graph t_export has a default of 0 but setting something to export changes this to "on." most of the items in this table have an empty string ('') for export and t_export (legacy schema? we've been using cacti for years). i tried setting t_export and export to 0 for all existing rows - it still happily exports thousands of graphs every three minutes.

we only need < 10 graphs actually exported, but they represent our network status on our public support page. if someone in the dev team can give me a hand with this, it would be great.

Post by **rony** » Wed Mar 03, 2010 6:24 pm

Known issue.....

Best solution is to limit the graphs which you wish to export in a separate tree and assign it to the export user.

Post by **TheWitness** » Wed Mar 03, 2010 9:33 pm

monachus wrote:upgraded to 0.8.7e today and now cacti exports _everything_ no matter whether it's configured to or not. it sent load up to > 50 and created massive gaps in every other graph.

i've been prowling around in the code and the database but am unable to find what criteria the code looks for to determine if a graph should be exported. i see that in graph_templates_graph t_export has a default of 0 but setting something to export changes this to "on." most of the items in this table have an empty string ('') for export and t_export (legacy schema? we've been using cacti for years). i tried setting t_export and export to 0 for all existing rows - it still happily exports thousands of graphs every three minutes.

we only need < 10 graphs actually exported, but they represent our network status on our public support page. if someone in the dev team can give me a hand with this, it would be great.

How were you xporting prior to upgrading? Tony's suggestion is correct and has received quite a bit of attention (aka works). However, "classic" has not been actively maintained and may not be working, as you have seen. I need to know what your expectation was and what is happening now.

Thanks,

TheWitness

monachus · Post by **monachus** » Thu Mar 04, 2010 1:49 am

i've always used classic and written to an NFS-mounted directory that is also visible to our webservers. doest it no longer honor the "allow graph export" flag?

Post by **TheWitness** » Thu Mar 04, 2010 7:01 am

Ahh, well, I never QA/tested that. This is likely a "minor" fix if it's broken. Will check likely sometime Friday.

TheWitness

monachus · Post by **monachus** » Thu Mar 04, 2010 9:32 am

great. thank you. let me know if i can help in any way.

Post by **TheWitness** » Thu Mar 04, 2010 7:42 pm

Try this. Let me know.

TheWitness

monachus · Post by **monachus** » Sat Mar 06, 2010 11:49 am

that appears to work. thank you for the quick turnaround!

Post by **TheWitness** » Sat Mar 06, 2010 1:42 pm

The commit had a few more fixes, but the differences are minor and should not impact you version. However, if you are inclined, the branches/0.8.7 of SVN includes the final final on this one.

TheWitness

laffen · Post by **laffen** » Mon Apr 12, 2010 9:14 am

rony wrote:Known issue.....

Best solution is to limit the graphs which you wish to export in a separate tree and assign it to the export user.

Could you give some more details? Just started looking at graph exporting, I can't see where I asssign a designated grap tree to an export user.

Cacti

cacti exporting all graphs after upgrade?

cacti exporting all graphs after upgrade?

Re: cacti exporting all graphs after upgrade?

Who is online