IP address seems to have changed. Unable to listen on .....

Hi,
I hope this link will help you to automatically update the /etc/hosts file,"http://lists.debian.org/debian-devel/1999/12/msg01202.html". Try to create a Crontab for the time that everyday your IP address is renewed.
let me know if you need any further help on this.

Thanks,
Neo

What a great Idea! I hadnt thought of that. Thanks very much!

This will probably not solve your problem,
i've alread setup ip addresses in hosts file, but still get the same message 1-2 times a day
It looks actually not related to dhclient running every 10-12 hours also, cause log times are not consistent.
I suspect a cron job, but didn't dig deeper since its not a vital problem but this probably makes the node unavailable for 1-2 seconds, please update here if you find anything

I changed ns_1@%IP_ADDR% to ns_1@localhost as mentioned but this doesn't change anything.

Still I get this errors:

[19:46:24] - IP address seems to have changed. Unable to listen on 'ns_1@169.254.10.159'.
[19:46:24] - IP address seems to have changed. Unable to listen on 'ns_1@169.254.10.159'.
[19:46:24] - IP address seems to have changed. Unable to listen on 'ns_1@169.254.10.159'.
[19:46:24] - IP address seems to have changed. Unable to listen on 'ns_1@169.254.10.159'.
[19:46:24] - IP address seems to have changed. Unable to listen on 'ns_1@169.254.10.159'.
[19:46:24] - IP address seems to have changed. Unable to listen on 'ns_1@169.254.10.159'.

I guess the real question is will this error cause a node to fail if it decides it cant bind to a given IP address.

Nichess, it looks like your node is loosing network connectivity on one of your network cards, if the 169.x address is anything to go by.

Yes Nichess, it seems the network connectivity on LAN. (169.294.x.x - apipa address)

And regarding the your question geosword, i dont think you will loose connectivity as your connection is hostname specific and they are inturn resolved to whatever ip updated in the /etc/hosts.

Hope this helps. If this doesn't answer your question, please update the thread

I installed the Couchbase on another drive than "C:" in Win7 - that gives back the message only once I start the Couchbase-Service.

Maybe I should disable the APIPA (automatic address configuration) in Windows.

Thanks

Nichess

Do you know what is causing this ?

I disabled APIPA on the Entire Computer now (WIN7) and it solves the problem.

Howto: http://support.microsoft.com/default.aspx?scid=kb;EN-US;244268

As far as I understood the problem, it is because the DHCP-Server of my Rooter wasn't quick enough to provide a IP-Adress - Then my Computer was setting himself a IP Adress through "Automatic Private IP Address" APIPA.

Hi nichess,
Its good to know that you got rid of the issue. But in case, any day in future if you see a 0.0.0.0 ip address please remember that you have disabled APIPA. Just an information i thought will help you.

Because basically APIPA - is a automatically assigned address by your windows to make sure your computer can be identified in the LAN.

Thanks
Neo

Hi isbaran,
I think even though you changed the information in the hosts file, still you have done it after you know the new IP address. So i think before you update it the Logs might be generated.

And just to understand better could you please copy/paste or attach the screenshots of the errors at different times that you are getting will help me in understanding it further.

Thanks,
Neo

Hello,

It's not related to ip info in hosts file, i setup ip addresses in hosts the first time cluster is set up

Here is an example log line:

IP address seems to have changed. Unable to listen on 'ns_1@cb2.domain.net'. menelaus_web_alerts_srv001 ns_1@cb2.domain.net 01:52:20 - Wed Nov 21, 2012

I just checked and previous message is at "22:14:38 - Thu Nov 8, 2012" and the one before at "08:51:22 - Fri Nov 2, 2012"

They don't look related, maybe its somehow an ec2 issue

PLEASE DO NOT USE THIS FORUM FOR ANYTHING ELSE OTHER THAN COUCHBASE

Thanks in advance