[clif] Re: Deployment failure?

[Bruno Dillenseger <bruno.dillenseger@xxxxxxxxxxxxxxxxxx>]

> > It seems that your remote server registered in the registry with an 
> > IP address that is not reachable from your console host. Could you 
> > check your network settings (particularly in the etc/clif.props) ? 
> > This may typically occur when your computers belong to several subnets.
>
> Contents of clif.props appears below. I don't see a setting that would 
> correspond to the ip of my remote host. It looks like they are 
> properly set to the console's address. (Unless I misunderstand the 
> purpose of the codeserver setting...)
Yes, but this is not sufficient. When working with several subnets you 
must ensure that RMI will choose IP addresses on a common subnet among 
locally configured network interfaces (see property 
jonathan.connectionfactory.host), otherwise, you may face routing 
problems. The same thing must be done for the plain TCP socket based 
final dadta collection step (see property clif.filestorage.host). Can 
you have a look at the IP configuration of every involved computer 
(ipconfig)?

Note: it seems that you forgot to attach the clif.props
> Is there any way to see what address the Registry believes is correct? 
> Using wireshark, I also watched the registration process, and did not 
> notice anything amiss.
The connection with the registry is correct, but the RMI reference that 
is registered by the CLIF server is probably unreachable from the 
console. The "No route to host" exception at 
org.objectweb.clif.deploy.ServerDeploy.run(ServerDeploy.java:88) is 
rather explicit to me.

Best regards,
-- Bruno.