All, I am observing 2 problems occassionally occuring which may or may not be related. The first is that very rarely the time reported back to gmetad from the gmond XML will leap backwards by maybe a month and a half. Checking the time on the server running the gmond reveals that the server time remains correct. Restarting the gmond fixex the problem. My environment is the gmond is running on windows under cygwin. Hosts unicast to a single headnode which is polled by the gmetad. I have not observed the problem on Linux. So it may be windows specific or even cygwin. It has me stumped. Anyone ever seen this? The send thing that sometimes occurs is: RRD_update (/.../FX EXO QANet farm/__SummaryInfo__/cpu_user.rrd): illegal attempt to update using time 1150890115 when last update time is 1150890254 (minimum one second step) The was I see it, the only way this sort of thing can happen when writing summary data is if the LOCALTIME reported for the cluster was maybe jittering around. But I don't know. Can anyone give me suggestions or suggest ways I may get to the bottom of this please? - Richard Barclay Capital Ganglia Engineering and Development, Ganglia 1st line support, 2nd line support, Ganglia Commissioning and Deployment, Ganglia dog's body.
------------------------------------------------------------------------ For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. ------------------------------------------------------------------------
