21 Oct
2014
21 Oct
'14
1:47 p.m.
This was the trick. There was an external test/script still using the old mail server's name. This external test was under the Xymon's server's ~xymon/client/ext directory and I didn't think to look there with my "it must be a xymonnet test" blinders.
Thanks for the help.
Robert Herron robert.herron at gmail.com
On Wed, Oct 15, 2014 at 5:13 PM, Root, Paul T <Paul.Root at centurylink.com> wrote:
This generally means that the xymon server is still performing a test on this address.
Do you have any ext scripts or maybe cron scripts that still are running to look at this machine.
What I generally do is add the machine back into the hosts.cfg file so it will show up and tell me what test is the issue. Fix that and remove the host again.