ganglia can handle the case where nodes are not perfectly synchronized between each other. i was speaking to the problem where gmond is started and then another process on the same box shifts the time backwards an hour (for example). this shift would cause gmond to go silent for an hour.
On Wed, 2006-12-06 at 10:20 -0800, Phil Dibowitz wrote: > matt massie wrote: > > > > i second ian's idea to check your clocks. if the clock changes > > underneath gmond after it starts, the shift can stop metric collection > > for as long a period as the shift. > > As I mentioned - they're in sync with NTP. Ops1 is the gmetad box, and > ses1-3 are the 'bad' boxes, and ses4 works fine: > > $ for i in ops1 ses1 ses2 ses3 ses4; do ssh $i 'date'; done > Wed Dec 6 10:18:38 PST 2006 > Wed Dec 6 10:18:38 PST 2006 > Wed Dec 6 10:18:38 PST 2006 > Wed Dec 6 10:18:39 PST 2006 > Wed Dec 6 10:18:39 PST 2006 > -- matt massie phone: 415.692.0828 x2843 fax: 415.278.0441 http://archrock.com/
