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.
Howie wrote:And neither colour the link? Could you paste the config for one of those links please?
I think you misunderstand - when run from the GUI (Recalculate now) it works and all the links gets painted according to the data in the rrd-files. If i run it via the poller, the links don't get painted.
Howie wrote:And neither colour the link? Could you paste the config for one of those links please?
I think you misunderstand - when run from the GUI (Recalculate now) it works and all the links gets painted according to the data in the rrd-files. If i run it via the poller, the links don't get painted.
/Tommy
But the map does update with the poller? (the date changes)
And nothing shows in the cacti.log when that happens?
And you get grey links?
Howie wrote:But the map does update with the poller? (the date changes)
And nothing shows in the cacti.log when that happens?
And you get grey links?
Yes - the date changes and in the cacti-log I see that it writes "wrote map ....". But the links or nodes does not get colored according to the load.
When run from "Recalculate now" everything shows up just fine.
But I've created the above workaround and I am using this for the moment until I hear from someone with Debian that got the CLI poller working with the speciel gd-lib functions.
I have found the difference....in the log check your returned for the same link.... the same peer which is on load permanently, once with poller and once with button.
It can't work, because the link aren't grey, there are white (0%), and they have wrong value.
It's doesn't impact on gauge value (At least for CPU load, I haven't finish the map for humidity / temperature)
humanlock wrote:I have found the difference....in the log check your returned for the same link.... the same peer which is on load permanently, once with poller and once with button.
It can't work, because the link aren't grey, there are white (0%), and they have wrong value.
It's doesn't impact on gauge value (At least for CPU load, I haven't finish the map for humidity / temperature)
Perhaps, I am mistaken, but I thought we got exactly the same problem.
Please run with DEBUG logging for one poller cycle, and then look for the other ReadData lines. You will see what data is being collected from rrdtool.
In one: 4,5630702333e+05
In the other: 4.6610777732e+05
The first one has a comma, and the second has a point.
I think this is the answer to your problem, and that somehow you have something funny like a default locale of french and a locale for one user of english (or perhaps the other way around).
It was also my locale that tricked it and why it didn't colored the links the right way.
I use en_DK on my servers, but as soon as i prefixed the Poller entry in Crontab with "LC_ALL=en_US LANG=en_US" and generated the locales with "dpkg-reconfigure locales" it all worked from CLI as well.
Howie: Perhaps you should put in a check of which locale the user is using in check.php file? That might save some users a fair amount of time.
Tommy_dk wrote:Ohhh... there was a difference for me as well!
It was also my locale that tricked it and why it didn't colored the links the right way.
I use en_DK on my servers, but as soon as i prefixed the Poller entry in Crontab with "LC_ALL=en_US LANG=en_US" and generated the locales with "dpkg-reconfigure locales" it all worked from CLI as well.
Howie: Perhaps you should put in a check of which locale the user is using in check.php file? That might save some users a fair amount of time.
Thank you for a great product
/Tommy
If one of you would like to try it, I think that 0.97 solves this problem without needing to change locale. That way a check wouldn't be necessary. It has only recently become a problem with (I think) rrdtool 1.3, though.
Could you paste the config for one of those links please?
