You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@omid.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2018/12/26 11:39:00 UTC

[jira] [Created] (OMID-123) Allow starting Omid on machines without en or eth interfaces.

Lars Hofhansl created OMID-123:
----------------------------------

             Summary: Allow starting Omid on machines without en or eth interfaces.
                 Key: OMID-123
                 URL: https://issues.apache.org/jira/browse/OMID-123
             Project: Apache Omid
          Issue Type: Improvement
            Reporter: Lars Hofhansl


Currently there's an assumption that there must be an eth* or a configured en* interface in order to bind to a specific address.

{code}
Exception in thread "main" java.lang.IllegalArgumentException: No network 'en*'/'eth*' interfaces found
at org.apache.omid.NetworkUtils.getDefaultNetworkInterface(NetworkUtils.java:52)
at org.apache.omid.tso.TSOServerConfig.<init>(TSOServerConfig.java:88)
at org.apache.omid.tso.TSOServerConfig.<init>(TSOServerConfig.java:56)
at org.apache.omid.tso.TSOServer.main(TSOServer.java:147)
{code}

The first question is: Why don't we just allow to bind to ::?
Second, we can at least provide a default way to start when no en/eth interface is available.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)