ow2-proactive/programming

Stacktrace in task logs when hostname is not resolved

activeeon-bot opened this issue · 1 comments

Original issue created by Youri Bonnaffe on 27, Oct 2014 at 13:07 PM - PALIGHT-88


On a machine where hostname is not properly resolved, the following stack trace appears in the task log. It does not seem to affect task execution.

On the machine, the command hostname returns the hostname but hostname -f returns "hostname: Unknown host".

Fixing the command hostname -f fixes the issue, however it should probably not print this in the task logs. It also seems that setting proactive.useIPaddress=true did not help.

2580000@10.105.135.12;09:19:07] java.net.UnknownHostException: foo.acme.com: foo.acme.com: Name or service not known 
[2580000@10.105.135.12;09:19:07] at java.net.InetAddress.getLocalHost(Unknown Source) 
[2580000@10.105.135.12;09:19:07] at org.objectweb.proactive.core.body.AbstractUniversalBody.(AbstractUniversalBody.java:106) 
[2580000@10.105.135.12;09:19:07] at org.objectweb.proactive.core.body.LocalBodyStore.getContext(LocalBodyStore.java:218) 
[2580000@10.105.135.12;09:19:07] at org.objectweb.proactive.core.body.proxy.AbstractBodyProxy.initUrls(AbstractBodyProxy.java:184) 
[2580000@10.105.135.12;09:19:07] at org.objectweb.proactive.core.body.proxy.AbstractBodyProxy.invokeOnBody(AbstractBodyProxy.java:143) 
[2580000@10.105.135.12;09:19:07] at org.objectweb.proactive.core.body.proxy.AbstractBodyProxy.reify(AbstractBodyProxy.java:125) 
[2580000@10.105.135.12;09:19:07] at pa.stub.org.ow2.proactive.scheduler.task.forked._StubForkerStarterCallback.callback(_StubForkerStarterCallback.java) 
[2580000@10.105.135.12;09:19:07] at org.ow2.proactive.scheduler.task.forked.ForkerStarter.callBack(ForkerStarter.java:95) 
[2580000@10.105.135.12;09:19:07] at org.ow2.proactive.scheduler.task.forked.ForkerStarter.main(ForkerStarter.java:81) 
[2580000@10.105.135.12;09:19:07] Caused by: java.net.UnknownHostException: foo.acme.com: Name or service not known 
[2580000@10.105.135.12;09:19:07] at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) 
[2580000@10.105.135.12;09:19:07] at java.net.InetAddress$1.lookupAllHostAddr(Unknown Source) 
[2580000@10.105.135.12;09:19:07] at java.net.InetAddress.getAddressesFromNameService(Unknown Source) 
[2580000@10.105.135.12;09:19:07] ... 9 more

Original comment posted by Youri Bonnaffe on 10, Nov 2014 at 11:00 AM


Solved by removing dead code.

Nevertheless it is expected that hostname is properly configured on machines.