1.2.0 Beta 4 -> 1.2.0 Release - Graphs tab is blank

[Jeeves]

I don't suspect this is common; However, upon upgrading from 1.2.0 B4 to the 1.2.0 release a couple of things were noted;

1) Cacti did not go through an 'install' (or upgrade) procedure upon browsing the web interface.
- Going to /install manually did result in a series of DB alterations. Unlike normal upgrades, no warnings, EULA, etc. was presented.
- A single line had a yellow alert (with no explanation of the cause): "ALTER TABLE `poller_resource_cache` ADD `attributes`"

2) Upon logging in, the graphs tab is blank. There are graphs shown under the Console -> Management -> Graphs.

blank_cacti_graphs.png (16.67 KiB) Viewed 1013 times

Thanks!

[netniV]

This is a known issue with running a beta. Between each beta and the final release, you should run upgrade_database.php --forcever=<previous full release>

We are looking to be able to address this in the future as I believe we should handle incremental upgrades for betas in the same way as we do a full release but that will require some code changes/testing.

[Jeeves]

This is a known issue with running a beta. Between each beta and the final release, you should run upgrade_database.php --forcever=<previous full release>

We are looking to be able to address this in the future as I believe we should handle incremental upgrades for betas in the same way as we do a full release but that will require some code changes/testing.

That's good to know. Thanks for the heads up and quick response!

[classen]

If my database is already at 1.2.0, but I want to force the upgrade script to run what should I enter for <previous full release>?

cd cacti/cli
php upgrade_database.php --forcever=<previous full release>


Thanks

[cjolly3053]

So had this same issue and tried a number of things for <previous full release> and get the error each time -bash: syntax error near unexpected token 'newline'

Any ideas??? I was running the 1.2.0 Beta 1 so had not done any other beta installs.

[Osiris]

Open the browsers debug log, go-to the console and pass to GitHub the console errors. You might want to reload the JavaScript (F5 on Firefox, chrome is magic.)

[Osiris]

Use the previous release number instead of <...>. Like "--forcever=1.1.38"

[cjolly3053]

Ok yeah I was an idiot on that one...lol

Now I'm getting "System log file is not available for writing, please enable write access Log: /var/www/html/cacti/log/cacti.log"

Already did chmod 755 on cacti.log but still an issue???

Any ideas on that?

[netniV]

Ensure you use the user that the website runs as on the sudo command. (sudo -u <user>)