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.
I have decided to use the "cygwin" official popen as a default. The attached source and configure.ac script will implement it by default. You can still use nifty popen using the flag "--enable-nifty-popen". I want you to test without it of course.
Hi Larry. Thanks for the files. I compiled these from home against the version of Cygwin I already have with no problems.
I have tested the poller, and it seems to be stable (so far). I noticed that sh.exe is still called in this version - the "G" version of the poller doesn't seem to do this - is there a reason why ?
I will continue to monitor the "I" version of the poller over the next few hours to see if it locks up or not...
Thanks
Cacti Version 0.8.8b Cacti OS Ubuntu LTS RRDTool Version RRDTool 1.4.7 Poller Information Type SPINE 0.8.8b
The reason that it continues to call sh.exe is that I have dropped nifty popen in favor of the standard "popen" in Cygwin which requires sh.exe. However, I am hoping there is some form of magic that will take place such that we don't see any more hung processes.
Could you also note if you are getting all the cmd.exe's as well? I have a theory, that you will need to confirm.
Larry
True understanding begins only when we realize how little we truly understand...
I can confirm that the cmd.exe processes are running (with around 4 cmd.exe processes when the poller runs). The process sh.exe has only hung twice since I switched to the new version this morning.
Overall, this is MUCH more stable than the one on the CACTI website (compiled with latest version of Cygwin 1.5-24).
Cacti Version 0.8.8b Cacti OS Ubuntu LTS RRDTool Version RRDTool 1.4.7 Poller Information Type SPINE 0.8.8b
When I say "hung", the poller does eventually timeout after 292 seconds (only done this twice in 9 hours, and still looking good). However, the sh.exe process doesn't close properly (I have to kill it) - but the cactid.exe processes seem to close fine.
To give you an idea, I have enclosed a screen shot of the poller stats. From 05:00 this morning, I switched to the "I" poller...
As you can see, I am averaging between 30 and 60 seconds. I'm a bit disappointed, as I was hoping to enjoy the low poller times that everyone else seems to get. Hopefully, from the graph, you can get an indication of how the poller is behaving. The peaks (292 seconds) is where I have to kill process "sh.exe".
The stats previous to 05:00 are from the "G" poller, which as you can see, is extremely stable.
Another thing that is quite annoying is that if I run the poller from the command line, it is on average 6 seconds faster than the scheduled task
Cacti Version 0.8.8b Cacti OS Ubuntu LTS RRDTool Version RRDTool 1.4.7 Poller Information Type SPINE 0.8.8b
My theory is that when the poller times out for some reason, that when I signal things to end, that the timed out shell processes do now receive a term signal as they should.
I would like to get the Cacti logs from you system from around the two abends of the sh.exe process. If you could send them, that would be great.
Larry
True understanding begins only when we realize how little we truly understand...
Unfortunately, I canned the logs around this time (they were quite large). However, the poller has exceeded 292 seconds twice since we spoke last, and I do have the logs for these (although they are MEDIUM, and not DEBUG). Would these help at all ?
I should also point out that process sh.exe has not hung since I switched to the new version you kindly provided. The version on the website for the "I" based poller hangs more often than not - this is what made me choose the "G" poller instead.
Overall, CACTID seems to be quite stable so far.
Cacti Version 0.8.8b Cacti OS Ubuntu LTS RRDTool Version RRDTool 1.4.7 Poller Information Type SPINE 0.8.8b