ip-172-30-0-37: ip-172-30-0-37: unknown error

GitHub | tobwiens | 9 months ago
Do you find the tips below useful? Click on the to mark them and say thanks to rafael . Or join the community to write better ones.
  1. 0 ip-172-30-0-37: ip-172-30-0-37: unknown error

    GitHub | 9 months ago | tobwiens ip-172-30-0-37: ip-172-30-0-37: unknown error
  2. 0
    samebug tip
    When kafka creates new consumers, it simply concatenate the name of your VM to generate the consumer id. So, your VM resolves localhost as the name of your VM, not whatever you had set. To solve, add kafka(or the name of VM) plus address to /etc/hosts
  3. 0

    Marathon doesn't run on the latest Vagrant DCOS

    GitHub | 2 years ago | mwasn dcos-01: dcos-01: unknown error
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    java.lang.AssertionError: Could not obtain the localhost address in a new 12c install | 9 months ago lmestre-linux: unknown error
  6. 0

    Uncaught UnknownHostException in host lookup

    GitHub | 1 year ago | karlgoldstein a9c6d0d6a85e: a9c6d0d6a85e: unknown error class=java.util.concurrent.ExecutionException a9c6d0d6a85e: unknown error

  1. nasimk 2 times, last 6 months ago
  2. mortalman7 1 times, last 10 months ago
11 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis


    ip-172-30-0-37: unknown error

  2. Java RT
    1. Method)
    4 frames
  3. org.ow2.proactive
    1. org.ow2.proactive.scheduler.core.DataSpaceServiceStarter.startNamingService(
    2. org.ow2.proactive.scheduler.core.SchedulerFrontend.initActivity(
    2 frames
  4. org.objectweb.proactive
    1 frame
  5. Java RT
    1 frame