SQL Error when selecting Graph for Export.

[exklusve]

Hello!

Last week I upgraded Cacti (all patched up as of today) and Spine to 8.7g.

Today I went into Graph Managment and selected one graph to be allowed to be exported.
The ID for this graph is 480. After hitting save, I get a new page where the graph template and host are set to none.
In the address bar it's show showing it's editing graph id 535. (next avail ID)
/cacti/graphs.php?action=graph_edit&id=535

It looks like it's creating a new graph instead of editing the existing graph.
This is also happening if I open up any graph-template and hit the save button wether or not I change anything.

In my logs here is the error I'm seeing after hitting save:

Code: Select all

04/04/2011 11:08:53 AM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'1064', SQL:"select id,column_name from graph_template_input where graph_template_id=" 
04/04/2011 11:08:53 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"select graph_template_id from graph_local where id=" 

In Technical Support under Utilities all of the DB tables are in 'OK' status.

Any ideas?

Thanks in advance!


System and setup info:

Cacti Version 0.8.7g
NET-SNMP version: 5.4.2.1
RRDTool 1.3.x
PHP Version 5.3.5
uname Linux cacti 2.6.32-gentoo-r7 #1 SMP Thu Apr 22 15:19:25 PDT 2010 i686

[exklusve]

Also found out today that I'm unable to create a new graph template. No errors but whenever I hit the save button, it goes back to a blank template without saving.

Any help is really appreciated.

Thanks!

[exklusve]

Solved.

After 3 fresh installs I figured out it was IE9.

[cigamit]

Thanks for the report. I have found the issue that was hindering IE9, and fixed it in SVN. It was a slight error on our part, we were placing a duplicate form tag. You should see these fixes in the upcoming 0.8.7h release.

[TXJeff]

Wow - I was having the same problem saving most graph-related items. Good catch with the IE9. I only made it through 2 fresh installs before I found this little nugget! Tested in FireFox and it works fine.

[Menger]

In my case the problem was also related to the browser, it was necessary to enable compatibility mode in the browser.

Menger
Blumenau - SC