All, I have just seen that the date as reported in the XML stream for one of my clusters went backwards by about 20 days recently.
This of course caused the RRD update to fail because it was attempting to update with an earlier timestamp. A netcat of the cluster port 8649 revealed that the cluster timestamp as well as timestamps for all the hosts was now well in the past. Looking at the code all timestamps would be affected if the headnode got confused about what was now, and now is calculated by calling: now = apr_time_now(); Note that this is a windows cluster not a linux one. Anyone ever seen this sort of thing happen? kind regards, richard ------------------------------------------------------------------------ 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. ------------------------------------------------------------------------
