Cannot change network interface of the server

activeeon-bot commented 10 years ago

Original issue created by Vladimir Bodnartchouk on 10, Sep 2014 at 18:33 PM - SCHEDULING-2153

Interfaces on my machine:

        lo      MAC n/a 127.0.0.1 0:0:0:0:0:0:0:1
        net0    MAC n/a
        net1    MAC n/a
        net2    MAC n/a
        ppp0    MAC n/a
        eth0    MAC n/a
        eth1    MAC n/a
        eth2    MAC n/a
        ppp1    MAC n/a
        eth3    MAC n/a 192.168.1.62 fe80:0:0:0:8c23:4921:7cb0:bd4d%10
        net3    MAC n/a fe80:0:0:0:0:100:7f:fffe%11
        net4    MAC n/a
        net5    MAC n/a fe80:0:0:0:0:5efe:c0a8:13e%13
        eth4    MAC n/a
        eth5    MAC n/a
        eth6    MAC n/a
        eth7    MAC n/a
        eth8    MAC n/a

When changing the network interface in in config/network/server.ini by setting:

proactive.net.interface=lo

C:\workdir\Releases\ProActiveWorkflowsScheduling-windows-x64-6.0.0-RC1\6.0.0 hjhj -RC1\bin>proactive-server.bat
Exception in thread "main" java.lang.ExceptionInInitializerError
        at org.ow2.proactive.scheduler.util.SchedulerStarter.getLocalAdress(SchedulerStarter.java:417)
        at org.ow2.proactive.scheduler.util.SchedulerStarter.connectToOrStartResourceManager(SchedulerStarter.java:232)
        at org.ow2.proactive.scheduler.util.SchedulerStarter.start(SchedulerStarter.java:151)
        at org.ow2.proactive.scheduler.util.SchedulerStarter.main(SchedulerStarter.java:125)
Caused by: java.lang.IllegalStateException: No suitable IP address found
        at org.objectweb.proactive.core.util.ProActiveInet.getInetAddress(ProActiveInet.java:84)
        at org.objectweb.proactive.core.httpserver.ClassServerServlet.getCodeBase(ClassServerServlet.java:94)
        at org.objectweb.proactive.core.remoteobject.AbstractRemoteObjectFactory.createClassServer(AbstractRemoteObjectFactory.java:71)
        at org.objectweb.proactive.core.remoteobject.AbstractRemoteObjectFactory.<clinit>(AbstractRemoteObjectFactory.java:59)
        ... 4 more

activeeon-bot commented 10 years ago

Original comment posted by Vladimir Bodnartchouk on 10, Sep 2014 at 18:37 PM

It works with scheduling 3.4.3

activeeon-bot commented 10 years ago

Original comment posted by Sergei Dolgov on 11, Sep 2014 at 12:40 PM

This is because the default value of {{proactive.net.nolocal}} is true (used to be present by default in {{config/proactive/ProActiveConfiguration.xml}}, now the default is defined in {{org/objectweb/proactive/core/config/CentralPAPropertyRepository.java}}).

The behavior is the same in 3.4.4 when using {{scheduler-start-gui}}:

sdolgov@britany:~/proactive-artifacts/releases-unpacked/ProActiveScheduling-3.4.4_bin_full $ cat config/proactive/ProActiveConfiguration.xml
<?xml version="1.0" encoding="UTF-8"?>
<ProActiveUserProperties>
    <properties>
        <prop key="proactive.net.nolocal" value="true"/>
        <prop key="proactive.net.interface" value="lo"/>
    </properties>
    <javaProperties>
    </javaProperties>
</ProActiveUserProperties>
sdolgov@britany:~/proactive-artifacts/releases-unpacked/ProActiveScheduling-3.4.4_bin_full $ ./bin/unix/scheduler-start-gui 
Starting the scheduler...
Exception in thread "main" java.lang.ExceptionInInitializerError
    at org.ow2.proactive.scheduler.util.SchedulerStarter.getLocalAdress(SchedulerStarter.java:245)
    at org.ow2.proactive.scheduler.util.SchedulerStarter.main(SchedulerStarter.java:164)
Caused by: java.lang.IllegalStateException: No suitable IP address found
    at org.objectweb.proactive.core.util.ProActiveInet.getInetAddress(ProActiveInet.java:84)
    at org.objectweb.proactive.core.httpserver.ClassServerServlet.getCodeBase(ClassServerServlet.java:97)
    at org.objectweb.proactive.core.remoteobject.AbstractRemoteObjectFactory.createClassServer(AbstractRemoteObjectFactory.java:75)
    at org.objectweb.proactive.core.remoteobject.AbstractRemoteObjectFactory.<clinit>(AbstractRemoteObjectFactory.java:63)
    ... 2 more

Not applicable when using {{bin/start-server.js}} because it overwrites {{ProActiveConfiguration.xml}}.

Setting {{proactive.net.nolocal}} to {{false}} solves the problem. I'd say it is reasonable to expect from user a non-contradicting configuration.

activeeon-bot commented 10 years ago

Original comment posted by Sergei Dolgov on 11, Sep 2014 at 14:51 PM

(link: ~vbodnart), is it OK with you if I close this bug? I can create another issue (improvement) to improve the error messages in case of conflicting configuration options.

activeeon-bot commented 10 years ago

Original comment posted by Vladimir Bodnartchouk on 11, Sep 2014 at 14:53 PM

Yes it's ok Sergei Dolgov

ow2-proactive / scheduling

Cannot change network interface of the server #1918