Uploaded image for project: 'Thrift'
  1. Thrift
  2. THRIFT-2385

Problem with gethostbyname2 during make check

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.9.2
    • Component/s: None
    • Labels:
      None
    • Environment:

      Centos 6.3 running on Vagrant

      Description

      I'm trying to run Mesos on several virtual machines with each a NAT NIC and 3 Hostonly adapter. I followed the following guide : http://mesos.apache.org/gettingstarted/ but when I try to "make check" I have the following error :
      WARNING: Logging before InitGoogleLogging() is written to STDERR
      F0304 00:15:58.755775 1571 process.cpp:1486] Failed to initialize, gethostbyname2: Unknown host

          • Check failure stack trace: ***
            make[5]: *** [check-local] Aborted
            make[5]: Leaving directory `/home/vagrant/mesos/build/3rdparty/libprocess'
            make[4]: *** [check-am] Error 2
            make[4]: Leaving directory `/home/vagrant/mesos/build/3rdparty/libprocess'
            make[3]: *** [check-recursive] Error 1
            make[3]: Leaving directory `/home/vagrant/mesos/build/3rdparty/libprocess'
            make[2]: *** [check-recursive] Error 1
            make[2]: Leaving directory `/home/vagrant/mesos/build/3rdparty'
            make[1]: *** [check] Error 2
            make[1]: Leaving directory `/home/vagrant/mesos/build/3rdparty'
            make: *** [check-recursive] Error 1
            I can run Mesos as a master after that but I get the same error if I try to run it as a slave

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              proussel Pierre Roussel

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment