Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-7238

ns_server is still validating ip address in ip file even if erlang already has node name defined (was: 2.0 Build 1941: Couchbase Server does not start after a change in IP, server is looking for the old IP even after the hostname resolves to the new one.)

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.0-beta-2, 2.0
    • Fix Version/s: 2.0
    • Component/s: ns_server
    • Security Level: Public
    • Labels:
      None

      Description

      Couchbase Server does not start after a change in IP, server is looking for the old IP even after the hostname resolves to the new one. Followed the best-practices information to configure the hostname in the couchbase-server file and this issue is reproducible in the 1941 2.0 build.

      Error messages from the log:
      [ns_server:info,2012-11-16T13:16:45.502,ns_1@FQDN:dist_manager<0.2732.0>:dist_manager:read_address_config:55]Reading ip config from "/opt/couchbase/var/lib/couchbase/ip"
      [ns_server:warn,2012-11-16T13:16:45.522,ns_1@FQDN:dist_manager<0.2732.0>:dist_manager:is_good_address:81]Cannot listen on address `OLD IP`: eaddrnotavail

      The logs are available in the link below:
      https://s3.amazonaws.com/customers.couchbase.com/jawfishgames/couch14-build-1914.zip

      update:

      Apparently as part of process of setting up node name folks just left original /opt/couchbase/var/lib/couchbase/ip. And ns_server's bug is due to attempt to validate that address even though it won't be actually used.

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        balak balak created issue -
        balak balak made changes -
        Field Original Value New Value
        Assignee Abhinav Dangeti [ abhinav ]
        ketaki Ketaki Gangal made changes -
        Fix Version/s 2.0 [ 10114 ]
        Affects Version/s 2.0 [ 10114 ]
        abhinav Abhinav Dangeti made changes -
        Assignee Abhinav Dangeti [ abhinav ] Aleksey Kondratenko [ alkondratenko ]
        steve Steve Yen made changes -
        Summary 2.0 Bulid 1941 : Couchbase Server does not start after a change in IP, server is looking for the old IP even after the hostname resolves to the new one. 2.0 Build 1941: Couchbase Server does not start after a change in IP, server is looking for the old IP even after the hostname resolves to the new one.
        Assignee Aleksey Kondratenko [ alkondratenko ] Abhinav Dangeti [ abhinav ]
        Priority Major [ 3 ] Blocker [ 1 ]
        abhinav Abhinav Dangeti made changes -
        Attachment cbcollectinfo_10_1_3_222.zip [ 15859 ]
        abhinav Abhinav Dangeti made changes -
        Assignee Abhinav Dangeti [ abhinav ] Aleksey Kondratenko [ alkondratenko ]
        alkondratenko Aleksey Kondratenko (Inactive) made changes -
        Assignee Aleksey Kondratenko [ alkondratenko ] Abhinav Dangeti [ abhinav ]
        james.mauss James Mauss made changes -
        Description
        Couchbase Server does not start after a change in IP, server is looking for the old IP even after the hostname resolves to the new one. Followed the best-practices information to configure the hostname in the couchbase-server file and this issue is reproducible in the 1941 2.0 build.

        Error messages from the log:
        [ns_server:info,2012-11-16T13:16:45.502,ns_1@FQDN:dist_manager<0.2732.0>:dist_manager:read_address_config:55]Reading ip config from "/opt/couchbase/var/lib/couchbase/ip"
        [ns_server:warn,2012-11-16T13:16:45.522,ns_1@couch14.dev.jawfishgames.com:dist_manager<0.2732.0>:dist_manager:is_good_address:81]Cannot listen on address `OLD IP`: eaddrnotavail

        The logs are available in the link below:
        https://s3.amazonaws.com/customers.couchbase.com/jawfishgames/couch14-build-1914.zip







        Couchbase Server does not start after a change in IP, server is looking for the old IP even after the hostname resolves to the new one. Followed the best-practices information to configure the hostname in the couchbase-server file and this issue is reproducible in the 1941 2.0 build.

        Error messages from the log:
        [ns_server:info,2012-11-16T13:16:45.502,ns_1@FQDN:dist_manager<0.2732.0>:dist_manager:read_address_config:55]Reading ip config from "/opt/couchbase/var/lib/couchbase/ip"
        [ns_server:warn,2012-11-16T13:16:45.522,ns_1@FQDN:dist_manager<0.2732.0>:dist_manager:is_good_address:81]Cannot listen on address `OLD IP`: eaddrnotavail

        The logs are available in the link below:
        https://s3.amazonaws.com/customers.couchbase.com/jawfishgames/couch14-build-1914.zip






        alkondratenko Aleksey Kondratenko (Inactive) made changes -
        Summary 2.0 Build 1941: Couchbase Server does not start after a change in IP, server is looking for the old IP even after the hostname resolves to the new one. ns_server is still validating ip address in ip file even if erlang already has node name defined (was: 2.0 Build 1941: Couchbase Server does not start after a change in IP, server is looking for the old IP even after the hostname resolves to the new one.)
        Description
        Couchbase Server does not start after a change in IP, server is looking for the old IP even after the hostname resolves to the new one. Followed the best-practices information to configure the hostname in the couchbase-server file and this issue is reproducible in the 1941 2.0 build.

        Error messages from the log:
        [ns_server:info,2012-11-16T13:16:45.502,ns_1@FQDN:dist_manager<0.2732.0>:dist_manager:read_address_config:55]Reading ip config from "/opt/couchbase/var/lib/couchbase/ip"
        [ns_server:warn,2012-11-16T13:16:45.522,ns_1@FQDN:dist_manager<0.2732.0>:dist_manager:is_good_address:81]Cannot listen on address `OLD IP`: eaddrnotavail

        The logs are available in the link below:
        https://s3.amazonaws.com/customers.couchbase.com/jawfishgames/couch14-build-1914.zip







        Couchbase Server does not start after a change in IP, server is looking for the old IP even after the hostname resolves to the new one. Followed the best-practices information to configure the hostname in the couchbase-server file and this issue is reproducible in the 1941 2.0 build.

        Error messages from the log:
        [ns_server:info,2012-11-16T13:16:45.502,ns_1@FQDN:dist_manager<0.2732.0>:dist_manager:read_address_config:55]Reading ip config from "/opt/couchbase/var/lib/couchbase/ip"
        [ns_server:warn,2012-11-16T13:16:45.522,ns_1@FQDN:dist_manager<0.2732.0>:dist_manager:is_good_address:81]Cannot listen on address `OLD IP`: eaddrnotavail

        The logs are available in the link below:
        https://s3.amazonaws.com/customers.couchbase.com/jawfishgames/couch14-build-1914.zip

        update:

        Apparently as part of process of setting up node name folks just left original /opt/couchbase/var/lib/couchbase/ip. And ns_server's bug is due to attempt to validate that address even though it won't be actually used.
        alkondratenko Aleksey Kondratenko (Inactive) made changes -
        Assignee Abhinav Dangeti [ abhinav ] Aleksey Kondratenko [ alkondratenko ]
        steve Steve Yen made changes -
        Component/s ns_server [ 10019 ]
        alkondratenko Aleksey Kondratenko (Inactive) made changes -
        Assignee Aleksey Kondratenko [ alkondratenko ] Aliaksey Artamonau [ aliaksey artamonau ]
        Aliaksey Artamonau Aliaksey Artamonau made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Aliaksey Artamonau Aliaksey Artamonau
            Reporter:
            balak balak
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes