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.
its actually the exact same script. A long time ago when we were having some trouble we made a copy and poked it a bit, but everything ended up getting reverted once we determined that the script wasnt the issue.
I renamed the stuff in cacti's UI after running an md5 on the scripts. Same result. run by hand it works, run via direct cactid it works, run via normal poller cron method and it fails.
Which to my eyes looks fine. So its something weird in the output thats coming from the script. What I dont understand is why cactid works when I run it manually, and why the script works when I run it manually but for some reason it fails via the poller calling cactid.
Well hardcoding wget (and/or re-importing the entire template set) worked, which is odd because its in the cacti users path and the cacti user could exec it.
Will return your output data in the form of an array that can then be parsed one line at a time. No need to have high load launching both the Perl script and wget binaries.
TheWitness
True understanding begins only when we realize how little we truly understand...
I think it actually has been rewritten accordingly (at least thats what a cursory glance would lead me to believe) however the most useful data we get about apache is a log-scrape script that uses a custom log that reports service times, errors and the like which dumps into a cacti graph.