Client IP address change
list Vernon Everett
Hi all Is there a "trick" to changing the IP address of a monitored Unix client? We had to change the IP address of a client a few days ago, but not the host name. In hosts.cfg, I changed the IP, but since then, the host conn is still red, and lists the old IP address. I tried restarting the Xymon server, and when that didn't help, I restarted the cache daemon - not that I was expecting that to help. (The client isn't in DNS.) The only place it can get the IP (old or new) is from hosts.cfg, and I have removed all references to the old IP from hosts.cfg. All other (client side) tests work fine, except conn, and of course ssh and rpc, which are disabled automatically, believing the host is down. Any tips appreciated. Regards Vernon -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford
list Josh Luthman
The default conn test is to the hostname. If it can't get DNS for it, then it will try the IP. To skip this behavior you can do (in hosts.cfg) 1.1.1.1 foo.bar.com # testip If the hostname doesn't have DNS you'll need to do this and of course correct the IP. Josh Luthman Office: XXX-XXX-XXXX Direct: XXX-XXX-XXXX XXXX Wayne St Suite XXXX Troy, OH XXXXX On Tue, Nov 17, 2015 at 9:01 PM, Vernon Everett <user-b3f8dacb72c8@xymon.invalid>
▸
wrote:
Hi all Is there a "trick" to changing the IP address of a monitored Unix client? We had to change the IP address of a client a few days ago, but not the host name. In hosts.cfg, I changed the IP, but since then, the host conn is still red, and lists the old IP address. I tried restarting the Xymon server, and when that didn't help, I restarted the cache daemon - not that I was expecting that to help. (The client isn't in DNS.) The only place it can get the IP (old or new) is from hosts.cfg, and I have removed all references to the old IP from hosts.cfg. All other (client side) tests work fine, except conn, and of course ssh and rpc, which are disabled automatically, believing the host is down. Any tips appreciated. Regards Vernon -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford
list Vernon Everett
Yep, that worked. So where is it keeping a record of the IP address or cache of the name/IP? As I mentioned, I changed hosts.cfg, and restarted Xymon server. I would have expected that to force a reread of hosts.cfg, and cleared any cache of the old IP address. Thanks for you help. Regards Vernon On 18 November 2015 at 10:04, Josh Luthman <user-4c45a83f15cb@xymon.invalid>
▸
wrote:
The default conn test is to the hostname. If it can't get DNS for it, then it will try the IP. To skip this behavior you can do (in hosts.cfg) 1.1.1.1 foo.bar.com # testip If the hostname doesn't have DNS you'll need to do this and of course correct the IP. Josh Luthman Office: XXX-XXX-XXXX Direct: XXX-XXX-XXXX XXXX Wayne St Suite XXXX Troy, OH XXXXX On Tue, Nov 17, 2015 at 9:01 PM, Vernon Everett <user-b3f8dacb72c8@xymon.invalid> wrote:Hi all Is there a "trick" to changing the IP address of a monitored Unix client? We had to change the IP address of a client a few days ago, but not the host name. In hosts.cfg, I changed the IP, but since then, the host conn is still red, and lists the old IP address. I tried restarting the Xymon server, and when that didn't help, I restarted the cache daemon - not that I was expecting that to help. (The client isn't in DNS.) The only place it can get the IP (old or new) is from hosts.cfg, and I have removed all references to the old IP from hosts.cfg. All other (client side) tests work fine, except conn, and of course ssh and rpc, which are disabled automatically, believing the host is down. Any tips appreciated. Regards Vernon -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford
-- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford
list Adam Goryachev
▸
On 18/11/2015 21:42, Vernon Everett wrote:
Yep, that worked. So where is it keeping a record of the IP address or cache of the name/IP? As I mentioned, I changed hosts.cfg, and restarted Xymon server. I would have expected that to force a reread of hosts.cfg, and cleared any cache of the old IP address. Thanks for you help.
Silly question, but did you check /etc/hosts ? Regards, Adam
▸
On 18 November 2015 at 10:04, Josh Luthman <user-4c45a83f15cb@xymon.invalid> wrote:The default conn test is to the hostname. If it can't get DNS for it, then it will try the IP. To skip this behavior you can do (in hosts.cfg) 1.1.1.1 foo.bar.com # testip If the hostname doesn't have DNS you'll need to do this and of course correct the IP. Josh Luthman Office: XXX-XXX-XXXX Direct: XXX-XXX-XXXX XXXX Wayne St Suite XXXX Troy, OH XXXXX On Tue, Nov 17, 2015 at 9:01 PM, Vernon Everett <user-b3f8dacb72c8@xymon.invalid> wrote:Hi all Is there a "trick" to changing the IP address of a monitored Unix client? We had to change the IP address of a client a few days ago, but not the host name. In hosts.cfg, I changed the IP, but since then, the host conn is still red, and lists the old IP address. I tried restarting the Xymon server, and when that didn't help, I restarted the cache daemon - not that I was expecting that to help. (The client isn't in DNS.) The only place it can get the IP (old or new) is from hosts.cfg, and I have removed all references to the old IP from hosts.cfg. All other (client side) tests work fine, except conn, and of course ssh and rpc, which are disabled automatically, believing the host is down. Any tips appreciated. Regards Vernon -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford
list Vernon Everett
Yep, I did. Agreed. Silly question. :-) On 19 November 2015 at 10:58, Adam Goryachev <
▸
user-92fd6827f6ae@xymon.invalid> wrote:
On 18/11/2015 21:42, Vernon Everett wrote: Yep, that worked. So where is it keeping a record of the IP address or cache of the name/IP? As I mentioned, I changed hosts.cfg, and restarted Xymon server. I would have expected that to force a reread of hosts.cfg, and cleared any cache of the old IP address. Thanks for you help. Silly question, but did you check /etc/hosts ? Regards, Adam On 18 November 2015 at 10:04, Josh Luthman <user-4c45a83f15cb@xymon.invalid> <user-4c45a83f15cb@xymon.invalid> wrote: The default conn test is to the hostname. If it can't get DNS for it, then it will try the IP. To skip this behavior you can do (in hosts.cfg) 1.1.1.1 foo.bar.com # testip If the hostname doesn't have DNS you'll need to do this and of course correct the IP. Josh Luthman Office: XXX-XXX-XXXX Direct: XXX-XXX-XXXX XXXX Wayne St Suite XXXX Troy, OH XXXXX On Tue, Nov 17, 2015 at 9:01 PM, Vernon Everett <user-b3f8dacb72c8@xymon.invalid> <user-b3f8dacb72c8@xymon.invalid> wrote: Hi all Is there a "trick" to changing the IP address of a monitored Unix client? We had to change the IP address of a client a few days ago, but not the host name. In hosts.cfg, I changed the IP, but since then, the host conn is still red, and lists the old IP address. I tried restarting the Xymon server, and when that didn't help, I restarted the cache daemon - not that I was expecting that to help. (The client isn't in DNS.) The only place it can get the IP (old or new) is from hosts.cfg, and I have removed all references to the old IP from hosts.cfg. All other (client side) tests work fine, except conn, and of course ssh and rpc, which are disabled automatically, believing the host is down. Any tips appreciated. Regards Vernon -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford
Xymon mailing user-d459c9d661b6@xymon.invalid
Xymon mailing user-d459c9d661b6@xymon.invalid
▸
-- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford
list Vernon Everett
Found it. It was a new host, which I built over the weekend. I hadn't been given all the info, so I assigned a PIDOOMA IP address from a range I knew were not in use, just to get the ball rolling. It had been added to DNS by an overeager colleague who logged in on the weekend and spotted my email notifying of the new build. When I was given the correct IP address info, it was quick and easy to fix, but the DNS guy wasn't told about the change, because we all thought it wasn't in DNS yet. So it's all good. No mystery. Just a bit of confusion. Thanks for your assistance. Regards Vernon On 19 November 2015 at 14:48, Jeremy Laidman <user-71895fb2e44c@xymon.invalid> wrote:
Vernon I don't believe Xymon keeps the IP address cached. It (xymonnet) asks the system resolver every time. If you don't have testip set (or a similar command-line option), xymonnet will always try to resolve the name, and if it resolves then the IP in hosts.cfg is ignored. Although you said the server isn't in the DNS, it might be in the /etc/hosts file, or NIS or LDAP or any other host resolution database the Xymon server's OS is configured to use (in /etc/nsswitch.conf). Try running "getent hosts <hostname>" and see if it shows the IP address. J
▸
On 19 Nov 2015 13:42, "Vernon Everett" <user-b3f8dacb72c8@xymon.invalid> wrote:Yep, that worked. So where is it keeping a record of the IP address or cache of the name/IP? As I mentioned, I changed hosts.cfg, and restarted Xymon server. I would have expected that to force a reread of hosts.cfg, and cleared any cache of the old IP address. Thanks for you help. Regards Vernon On 18 November 2015 at 10:04, Josh Luthman <user-4c45a83f15cb@xymon.invalid> wrote:The default conn test is to the hostname. If it can't get DNS for it, then it will try the IP. To skip this behavior you can do (in hosts.cfg) 1.1.1.1 foo.bar.com # testip If the hostname doesn't have DNS you'll need to do this and of course correct the IP. Josh Luthman Office: XXX-XXX-XXXX Direct: XXX-XXX-XXXX XXXX Wayne St Suite XXXX Troy, OH XXXXX On Tue, Nov 17, 2015 at 9:01 PM, Vernon Everett < user-b3f8dacb72c8@xymon.invalid> wrote:Hi all Is there a "trick" to changing the IP address of a monitored Unix client? We had to change the IP address of a client a few days ago, but not the host name. In hosts.cfg, I changed the IP, but since then, the host conn is still red, and lists the old IP address. I tried restarting the Xymon server, and when that didn't help, I restarted the cache daemon - not that I was expecting that to help. (The client isn't in DNS.) The only place it can get the IP (old or new) is from hosts.cfg, and I have removed all references to the old IP from hosts.cfg. All other (client side) tests work fine, except conn, and of course ssh and rpc, which are disabled automatically, believing the host is down. Any tips appreciated. Regards Vernon -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford-- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford
-- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford