Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
TheWitness wrote:If you dumped your old database and then imported it using mysqldump and mysql < *.sql, you effectively hosed your configuration. That is not how you upgrade.
Please confirm what process you used to "import your devices". If my assumption is correct, you can recover, it's just a bit of a pain with 0.8.7.
TheWitness
We're actually migrating to this new server from our current production one due to number of devices and datasources. So we were just following upgrade instructions as related to db import. Please advise if incorrect.
I just did a fresh replace of my cacti to the 8.7 version and after adding the monitor plugin I had the same problems with "Save Failed" errors.
I fixed it by going into user administration and making sure that the admin user had access to the monitor plugin. this solved my problem with this particular error.
ejensen wrote:I just did a fresh replace of my cacti to the 8.7 version and after adding the monitor plugin I had the same problems with "Save Failed" errors.
I fixed it by going into user administration and making sure that the admin user had access to the monitor plugin. this solved my problem with this particular error.
hope that helps anyone else!
Didn't work for me. Please see attachment. I've included current host info screen shot and admin realm screen shot.
gandalf wrote:Are you able to reproduce, when deactivating "monitor"
Reinhard
We just commented monitor out from global.php and the error no longer exists. Hopefully that is what you're asking?
So monitor 0.81 on 64bit OS is breaking it, correct? In this case, please contact cigamit and/or post to the monitor thread in the Plugins forum
Reinhard
Yep, its not allowing you to update the table. Run this query and see if it fixes it. ALTER TABLE host ADD monitor_text text default '' not null AFTER monitor
TheWitness wrote:If you dumped your old database and then imported it using mysqldump and mysql < *.sql, you effectively hosed your configuration. That is not how you upgrade.
Please confirm what process you used to "import your devices". If my assumption is correct, you can recover, it's just a bit of a pain with 0.8.7.
TheWitness
We're actually migrating to this new server from our current production one due to number of devices and datasources. So we were just following upgrade instructions as related to db import. Please advise if incorrect.
Should I open up a new thread for this? Much thx and appreciation to all you guys! This is an awesome tool, keep up the good work!