Hello Parker, I changed if ($host['TN'] > $host['TMAX'] * 4) to if ($host['TN'] > $host['TMAX'] * 8) for a test.
I was observing the whole process of the status changing of these remote nodes on the web from restarting the gmond until these nodes appearred to be down: For multiplier of 4, these nodes's hearbeats are cycling every 20s for up to 180s, then the head node stopped received hearbeats from these remote nodes. These nodes appeared to be down after 80s (these nodes become 'dead' at the point "Last heartbeat received 80 second ago"). For multiplier of 8, these nodes's hearbeats are cycling every 20s for up to 180s, then the head node stopped received hearbeats from these remote nodes. These nodes appeared to be down after 160s (these nodes become 'dead' at the point "Last heartbeat received 160 second ago"). It seems that these nodes stopped communicate with the head node after 180s. Increasing the multiplier just postpone the time when these nodes become 'dead'. Any idea ? Thanks a lot for your help. Yiye On Sun, 5 Feb 2006, Parker Morse wrote: > On Feb 4, 2006, at 12:40 PM, Parker Morse wrote: > > The PHP front-end shows a host as "down" if the TN value in the XML > > report is more than four times greater than the TMAX value: > > > > if ($host['TN'] > $host['TMAX'] * 4) > > return FALSE; > > $host_up = FALSE; > > > > The trick is figuring out where, in gmond.conf, to change the value > > of TMAX! I'm betting here: > > Thinking about it more, it might be easier to simply change the > multiplier in the PHP file from 4 to 10 or something. It would only > require changing one file (not multiple gmond.confs) and might be > more correct, since the multiplier appears to be a "magic number," > while the XML value presumably carries some meaning. > > pjm > > Parker Morse > [EMAIL PROTECTED] > > >
