Skip to main content
Version: Early Access

Troubleshoot Deploy networking issues

This page describes common networking errors and their solutions.

Server seems to be stuck on startup​

If the Deploy server startup process appears to be stuck, networking may not be configured on the Deploy server. Use the jstack tool to create a thread dump of the Java Virtual Machine (JVM) process that appears to be stuck. You can see lines similar to these in the generated file:

locked <0x00000007eb7cde38> (a java.lang.Object)
at ch.qos.logback.core.util.ContextUtil.getLocalHostName(ContextUtil.java:38)
at ch.qos.logback.core.util.ContextUtil.addHostNameAsProperty(ContextUtil.java:74)
at ch.qos.logback.classic.joran.action.ConfigurationAction.begin(ConfigurationAction.java:57)

The logback library cannot resolve the host name. Ensure that you can ping the host name and configure networking.

Server appears to start, but java.net.UnknownHostException appears in the log file​

If the Deploy server appears to start but the server log file shows java.net.UnknownHostException, networking may not be configured on the Deploy server. Example: In this log, you can see that the Deploy server cannot determine the server URL:

2015-05-04 17:50:49.248 [main] {} INFO com.xebialabs.deployit.Server - Deploy Server has started.
2015-05-04 17:50:49.250 [main] {} ERROR n.j.t.e.s.LoggingEventHandlerStrategy - Could not dispatch event: com.xebialabs.deployit.engine.spi.event.SystemStartedEvent@5d2b3c32 to handler com.xebialabs.deployit.Server@7fc75485[startListener]
java.lang.IllegalStateException: java.net.UnknownHostException: MBP-de-Benoit: MBP-de-Benoit: nodename nor servname provided, or not known
at com.xebialabs.deployit.ServerConfiguration.getDerivedServerUrl(ServerConfiguration.java:593) ~[appserver-core-2015.2.1.jar:na]
at com.xebialabs.deployit.ServerConfiguration.getServerUrl(ServerConfiguration.java:569) ~[appserver-core-2015.2.1.jar:na]
at com.xebialabs.deployit.Server.startListener(Server.java:322) [server-5.0.0.jar:na]

You can manually specify the server.url property in the XL_DEPLOY_SERVER_HOME/conf/deployit.conf file.

A similar error can occur in a different location:

Caused by: java.net.UnknownHostException: packer-freebsd-10.0-amd64: packer-freebsd-10.0-amd64: hostname nor servname provided, or not known
at java.net.InetAddress.getLocal	Host(InetAddress.java:1473) ~[na:1.7.0_71]
at pekko.remote.transport.ne	tty.NettyTransportSettings.<init>(NettyTransport.scala:123) ~[pekko-remote_2.10-2.3.5.jar:na]
at pekko.remote.transport.netty.NettyTransport.<init>(Nett	yTransport.scala:240) ~[pekko-remote_2.10-2.3.5.jar:na]

In this case, the pekko NettyTransport cannot find the default host name because networking is not configured. You can manually specify the host name property in the XL_DEPLOY_SERVER_HOME/conf/server.conf file.

To proceed, configure networking on the server. Ensure that you can ping the host name.

Deploy cannot connect to Windows Server on AWS EC2​

If you are running the Deploy server outside of an Amazon Web Services (AWS) EC2 network and attempt to connect to a Windows Server in the AWS firewall, AWS will block port 445 regardless if it is enabled in your firewall and security group.

To copy files and execute scripts on the Windows Server, install an SSH server (such as WinSSHD) on the server. Alternatively, install the Deploy server in the AWS firewall. This will allow you to use CIFS port 445.