KB-1890 Data server does not start with "Could not establish WebSocket connection with "

Parmida Borhani — Fri, 14 Jun 2019 23:44:21 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 6/14/2019 11:44:21 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it as per the documentation.

Affected Versions

This article applies to Appian 18.2 and later.

Last Reviewed: June 2019

Tags: data-server, infrastructure

KB-1890 Data server does not start with "Could not establish WebSocket connection with "

Parmida Borhani — Fri, 14 Jun 2019 23:43:32 GMT

Revision 19 posted to Appian Knowledge Base by Parmida Borhani on 6/14/2019 11:43:32 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it as per the documentation.

Affected Versions

This article applies to Appian 18.2 and later.

Last Reviewed: June 2019

Tags: data-server, infrastructure

INT-1890 Data server does not start with "Could not establish WebSocket connection with "

Parmida Borhani — Wed, 01 May 2019 02:14:45 GMT

Revision 18 posted to Appian Knowledge Base by Parmida Borhani on 5/1/2019 2:14:45 AM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it as per the documentation.

Affected Versions

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

INT-1890 Data server does not start with "Could not establish WebSocket connection with "

Jordan Horwat — Tue, 19 Mar 2019 17:44:36 GMT

Revision 17 posted to Appian Knowledge Base by Jordan Horwat on 3/19/2019 5:44:36 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it as per the documentation.

Affected Versions

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

DRAFT KB-XXXX - Data server does not start with "Could not establish WebSocket connection with "

Ryan Evans — Tue, 19 Mar 2019 15:15:26 GMT

Revision 16 posted to Appian Knowledge Base by Ryan Evans on 3/19/2019 3:15:26 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it as per the documentation.

Affected Versions

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

DRAFT KB-XXXX - Data server does not start with "Could not establish WebSocket connection with "

Ryan Evans — Fri, 15 Mar 2019 17:26:39 GMT

Revision 15 posted to Appian Knowledge Base by Ryan Evans on 3/15/2019 5:26:39 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it as per the documentation.

Affected Versions

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

DRAFT KB-XXXX - Data server does not start with "Could not establish WebSocket connection with "

Ryan Evans — Fri, 15 Mar 2019 09:08:09 GMT

Revision 14 posted to Appian Knowledge Base by Ryan Evans on 3/15/2019 9:08:09 AM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it.

Affected Versions

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

DRAFT KB-XXXX - Data-server does not start with "Could not establish WebSocket connection with "

Jordan Horwat — Thu, 14 Mar 2019 16:48:27 GMT

Revision 13 posted to Appian Knowledge Base by Jordan Horwat on 3/14/2019 4:48:27 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it.

Affected Versions

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

DRAFT KB-XXXX - Data-server does not start with "Could not establish WebSocket connection with "

Jordan Horwat — Thu, 14 Mar 2019 16:48:13 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 3/14/2019 4:48:13 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it.

Affected Versions

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

DRAFT KB-XXXX - Data-server does not start with "Could not establish WebSocket connection with "

Ryan Evans — Thu, 14 Mar 2019 16:40:44 GMT

Revision 11 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 4:40:44 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it.

Affected Versions:

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

DRAFT INT-XXXX - Data-server does not start with "Could not establish WebSocket connection with "

Ryan Evans — Thu, 14 Mar 2019 16:39:42 GMT

Revision 10 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 4:39:42 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window:

{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"Watchdog.java:1063","thread":"main","msg":"Starting Data Server in the background"}
{"level":"INFO","time":"YYYY-MM-DDTHH-mm-ssZ","logger":"watchdog","caller":"JvmStarter.java:41","thread":"main","msg":"Starting JVM process: Config{class=com.appian.data.server.Watchdog, hostAndPort=<HOST_AND_PORT>, args=[-f]}"}
Killed

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it.

Affected Versions:

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

DRAFT INT-XXXX - Data-server does not start with "Could not establish WebSocket connection with "

Ryan Evans — Thu, 14 Mar 2019 16:36:27 GMT

Revision 9 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 4:36:27 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window.

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it.

Affected Versions:

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

DRAFT INT-XXXX - Data-server does not start with "Could not establish WebSocket connection with "

Ryan Evans — Thu, 14 Mar 2019 16:35:43 GMT

Revision 8 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 4:35:43 PM

Symptoms

The Appian data server will fail to start with the message "killed" in the stdout command line window.

When reviewing the watchdog.log file, located in <APPIAN_HOME>/logs/data-server, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data server does not have the required privileges to access the ports and services that the data server uses to start and run.

Action

Ensure that the user intended to start the data server has the necessary privileges to access the ports and services required to start and run it.

Affected Versions:

This article applies to Appian 18.2 and later.

Last Reviewed: March 2019

Tags: data-server, infrastructure

DRAFT INT-XXXX - Data-server does not start with Could not establish WebSocket connection with .

Ryan Evans — Thu, 14 Mar 2019 14:52:02 GMT

Revision 1 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 2:52:02 PM

Symptoms

Appian Data-Server will fail to start with the message "killed" in the stdout command line window.

When reviewing the watchdog.log file, the following message will be seen:

Failed to start HS gateway (port=5401)"}

Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).

...

Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401

...

Failed to start RTS-0 gateway (port=5404)"}

Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).

...

Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

This will be

Cause

Action

Affected Versions:

Last Reviewed: March 2018

DRAFT INT-XXXX - Data-server does not start with Could not establish WebSocket connection with .

Ryan Evans — Thu, 14 Mar 2019 11:03:18 GMT

Revision 7 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 11:03:18 AM

Symptoms

The Appian Data-Server will fail to start with the message "killed" in the stdout command line window.

When reviewing the watchdog.log file, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data-server does not have the required privileges to access the required ports and services that the data-server uses to start and run.

Action

The customer will need to work with his network admins and IT team to determine why those ports and services are blocked for that specific user. The customer will need to unblock those services and ports for the data-server to start.

Workaround

Starting the data-server as root will allow the data-server to start, but is not recommended as this will cause issues for the customer in the future.

Affected Versions:

This applies to all versions of Appian.

Last Reviewed: March 2018

Tags: data-server, infrastructure

DRAFT INT-XXXX - Data-server does not start with Could not establish WebSocket connection with .

Ryan Evans — Thu, 14 Mar 2019 10:58:06 GMT

Revision 6 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 10:58:06 AM

Symptoms

The Appian Data-Server will fail to start with the message "killed" in the stdout command line window.

When reviewing the watchdog.log file, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data-server does not have the required privileges to access the required ports and services that the data-server uses to start and run.

Action

Inform the customer to work with his network admins and IT team to determine why those ports and services are blocked for that specific user. The customer will need to unblock those services and ports for the data-server to start.

Workaround

Starting the data-server as root will allow the data-server to start, but is not recommended as this will cause issues for the customer in the future.

Affected Versions:

This applies to all versions of Appian.

Last Reviewed: March 2018

Tags: data-server, infrastructure

DRAFT INT-XXXX - Data-server does not start with Could not establish WebSocket connection with .

Ryan Evans — Thu, 14 Mar 2019 10:57:44 GMT

Revision 5 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 10:57:44 AM

Symptoms

The Appian Data-Server will fail to start with the message "killed" in the stdout command line window.

When reviewing the watchdog.log file, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data-server does not have the required privileges to access the required ports and services that the data-server uses to start and run.

Action

Inform the customer to work with his network admins and IT team to determine why those ports and services are blocked for that specific user.

The customer will need to unblock those services and ports for the data-server to start.

Workaround

Starting the data-server as root will allow the data-server to start, but is not recommended as this will cause issues for the customer in the future.

Affected Versions:

This applies to all versions of Appian.

Last Reviewed: March 2018

Tags: data-server, infrastructure

DRAFT INT-XXXX - Data-server does not start with Could not establish WebSocket connection with .

Ryan Evans — Thu, 14 Mar 2019 10:56:43 GMT

Revision 4 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 10:56:43 AM

Symptoms

The Appian Data-Server will fail to start with the message "killed" in the stdout command line window.

When reviewing the watchdog.log file, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

Cause

This message is seen when the user attempting to start the data-server does not have the required privileges to access the required ports and services that the data-server uses to start and run.

Action

Inform the customer to work with his network admins and IT team to determine why those ports and services are blocked for that specific user.

Workaround

Starting the data-server as root will allow the data-server to start, but is not recommended as this will cause issues for the customer in the future.

Affected Versions:

This applies to all versions of Appian.

Last Reviewed: March 2018

Tags: data-server, infrastructure

DRAFT INT-XXXX - Data-server does not start with Could not establish WebSocket connection with .

Ryan Evans — Thu, 14 Mar 2019 10:56:16 GMT

Revision 3 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 10:56:16 AM

Symptoms

The Appian Data-Server will fail to start with the message "killed" in the stdout command line window.

When reviewing the watchdog.log file, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

This will be

Cause

This message is seen when the user attempting to start the data-server does not have the required privileges to access the required ports and services that the data-server uses to start and run.

Action

Inform the customer to work with his network admins and IT team to determine why those ports and services are blocked for that specific user.

Workaround

Starting the data-server as root will allow the data-server to start, but is not recommended as this will cause issues for the customer in the future.

Affected Versions:

This applies to all versions of Appian.

Last Reviewed: March 2018

Tags: data-server, infrastructure

DRAFT INT-XXXX - Data-server does not start with Could not establish WebSocket connection with .

Ryan Evans — Thu, 14 Mar 2019 10:52:30 GMT

Revision 2 posted to Appian Knowledge Base by Ryan Evans on 3/14/2019 10:52:30 AM

Symptoms

Appian Data-Server will fail to start with the message "killed" in the stdout command line window.

When reviewing the watchdog.log file, the following message will be seen:

Failed to start HS gateway (port=5401)"}
Could not establish WebSocket connection with localhost:5401. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5401
...
Failed to start RTS-0 gateway (port=5404)"}
Could not establish WebSocket connection with localhost:5404. The target Go process exited abnormally. Check for earlier errors (e.g. Go startup errors).
...
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5404

This will be

Cause

Action

Affected Versions:

Last Reviewed: March 2018