[
https://issues.apache.org/jira/browse/OMID-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl resolved OMID-123.
--------------------------------
Resolution: Implemented
This was fixed.
> Allow starting Omid on machines without en or eth interfaces.
> -------------------------------------------------------------
>
> Key: OMID-123
> URL: https://issues.apache.org/jira/browse/OMID-123
> Project: Phoenix Omid
> Issue Type: Sub-task
> Affects Versions: 1.0.1
> Reporter: Lars Hofhansl
> Assignee: Yoni Gottesman
> Priority: Major
> Attachments: OMID-123.txt
>
>
> 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
(v8.3.4#803005)
