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

localhost lookups on windows do not work correctly with ipv6

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: clients
    • Security Level: Public
    • Labels:

      Description

      It seems that "localhost" and other names that lookup ipv6 may fail to work from libcouchbase.

      See: http://www.couchbase.com/forums/thread/libcouchbase-windows-hostname-not-working#comment-1006977

      # Subject Project Status CR V
      For Gerrit Dashboard: &For+MB-6378=message:MB-6378

        Activity

        Hide
        trond Trond Norbye added a comment -

        Have you verified that you have a SERVER listening on an IPv6 endpoint?

        Show
        trond Trond Norbye added a comment - Have you verified that you have a SERVER listening on an IPv6 endpoint?
        Hide
        avsej Sergey Avseyev added a comment -

        i'm experiencing issues with resolve localhost on windows 2k8 server, which seems like binding localhost to ipv6 address: https://gist.github.com/3427633

        But the server is listening on ipv4 address https://gist.github.com/3427669

        Do you think it is the libcouchbase issue?

        Show
        avsej Sergey Avseyev added a comment - i'm experiencing issues with resolve localhost on windows 2k8 server, which seems like binding localhost to ipv6 address: https://gist.github.com/3427633 But the server is listening on ipv4 address https://gist.github.com/3427669 Do you think it is the libcouchbase issue?
        Hide
        trond Trond Norbye added a comment -

        From what I understand the erlang layer in the server have problems with the IPv6 stuff so it doesn't bind to an ipv6 address. I guess the workaround for now would be to encourage users to use 127.0.0.1 instead of localhost for now :'(

        Show
        trond Trond Norbye added a comment - From what I understand the erlang layer in the server have problems with the IPv6 stuff so it doesn't bind to an ipv6 address. I guess the workaround for now would be to encourage users to use 127.0.0.1 instead of localhost for now :'(
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        Workaround for now is to use ipv4.

        For example we can have setting in client libraries to only ask for ipv4 addresses when resolving hostname -> address

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - Workaround for now is to use ipv4. For example we can have setting in client libraries to only ask for ipv4 addresses when resolving hostname -> address
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        Thinking about it more.

        Yes server sucks at ipv6 support, but even if resolver gives you ipv6 name for localhost it should not ever prevent client from working. I.e. it needs to try ipv4 after ipv6 fails.

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - Thinking about it more. Yes server sucks at ipv6 support, but even if resolver gives you ipv6 name for localhost it should not ever prevent client from working. I.e. it needs to try ipv4 after ipv6 fails.
        Hide
        trond Trond Norbye added a comment -

        I actually thought we would try all of the addresses for the name, but I'll look into the code..

        Show
        trond Trond Norbye added a comment - I actually thought we would try all of the addresses for the name, but I'll look into the code..
        Hide
        trond Trond Norbye added a comment -

        CCBC-80 defaults to IPv4

        Show
        trond Trond Norbye added a comment - CCBC-80 defaults to IPv4

          People

          • Assignee:
            trond Trond Norbye
            Reporter:
            ingenthr Matt Ingenthron
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes