Cycle not updating

[mrscary]

Recently installed a new install of CACTI.. the graphs are graphing.. and i see them in Cycle.. but cycle isnt updating itself.


meaning, its not refreshing automatically. i see "Next update in".. and no numerical time value after that.. i have to manually refresh the page to see the updated graphs.

[netniV]

What version of cycle do you have?

[mrscary]

4.2

[mrscary]

after i got the net-snmp perl module installed, this suddenly started working..

[netniV]

I suspect that is pure coincidence since Cycle doesn't use netsnmp itself.

[mrscary]

it was really strange. all i did was go to active perl, fork the install i downloaded, added a bunch of .. well. "options" , one being the NET-SNMP perl plugin and it started working.

my mounted partitions is another story.

[netniV]

I am getting an issue on Chrome with Cycle due to CSP (Content Security Policy) which may have been preventing you. Not sure if the things you installed may have altered your web server setup for CSP but if so that may explain why it started working now.

[netniV]

Turns out I wasn't using the latest version of cycle myself. In addition though, I did find that the JS include wasn't using the 1.2.x get_md5_include_js() function which helps with cache issues.

[mrscary]

it works in IE and firefox, but not in chrome.
well, not in chrome on this remote machine i have connected to my monitor. I think there may be something wrong that that browser's setup. .same machine, different browser shows white screen when trying to get into cacti.

[netniV]

Check the developer tab for any console errors. Also, I just updated cycle so you may want to get that version.

[mrscary]

got it working in chrome , firefox, Edge Chromium.. all good.

the firefox im having trouble with is a firefox install on this ONE remote PC i am using a my main monitor over my desk. i dont know why it shows a blank page, but that's another topic that I already have open. .thanks!

[Osiris]

It's likely a setTimeout using an eval() over a function call. eval() is blocked by default now in JavaScript.

[netniV]

It's likely a setTimeout using an eval() over a function call. eval() is blocked by default now in JavaScript.

This is what I recently fixed, as I noticed that error.