KB-1787 HTTP 503 Service Unreachable with "Failed opening socket: Connecting to backend failed" error when attempting to access the Appian login page

Jordan Horwat — Wed, 14 Nov 2018 22:37:28 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 11/14/2018 10:37:28 PM

Symptoms

Apache Web Server has been configured to work with Appian, and all components of Appian are running successfully. Apache is running successfully, and it is reachable on the port configured with HTTPS.

However, trying to reach https://<SITE_URL>/suite fails with HTTP 503 Service Unreachable and the following error in mod_jk.log:

Failed opening socket to (::1:8009) (errno=111) 
connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111) 
sending request to tomcat failed (recoverable), because of error during request sending (attempt=2) 
connecting to tomcat failed. 
service failed, worker <NODE_NAME> is in error state 
All tomcat instances are busy or in error state 
All tomcat instances failed, no more workers left

Cause

The value in the field JKWorkerProperty worker.<NODE_NAME>.host does not match the IP address that the application server is running on.

Action

Ensure that the value in the field JKWorkerProperty worker.<NODE_NAME>.host matches the IP of the web server, as mentioned in Configuring Apache Web Server with Appian.

Affected Versions

This article applies to all versions of Appian using Apache as the Web Server.

Last Reviewed: November 2018

Tags: HTTP, apache, web server

DRAFT KB-XXXX HTTP 503 Service Unreachable with "Failed opening socket: Connecting to backend failed" error

Zach Puderbach — Tue, 13 Nov 2018 09:06:41 GMT

Revision 6 posted to Appian Knowledge Base by Zach Puderbach on 11/13/2018 9:06:41 AM

Symptoms

Apache Web Server has been configured to work with Appian. All components of Appian are running successfully. Apache is running successfully and reachable on the port configured with HTTPS.

Trying to reach https://<SITE_URL>/suite fails with HTTP 503 Service Unreachable and the following error in mod_jk.log:

Failed opening socket to (::1:8009) (errno=111) 
connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111) 
sending request to tomcat failed (recoverable), because of error during request sending (attempt=2) 
connecting to tomcat failed. 
service failed, worker <NODE_NAME> is in error state 
All tomcat instances are busy or in error state 
All tomcat instances failed, no more workers left

Cause

The value in the field JKWorkerProperty worker.<NODE_NAME>.host does not match the IP address that the application server is running on.

Action

Ensure that the value in the field JKWorkerProperty worker.<NODE_NAME>.host matches the IP of the web server, as mentioned in Configuring Apache Web Server with Appian.

Affected Versions

This article applies to all versions of Appian using Apache as the Web Server.

Last Reviewed: November 2018

Tags: HTTP, apache, web server

DRAFT KB-XXXX HTTP 503 Service Unreachable with "Failed opening socket: Connecting to backend failed" error

Jordan Horwat — Mon, 12 Nov 2018 17:54:54 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 11/12/2018 5:54:54 PM

Symptoms

Apache Web Server has been configured to work with Appian. All components of Appian are running successfully. Apache is running successfully and reachable on the port configured with HTTPS.

Trying to reach https://<SITE_URL>/suite fails with HTTP 503 Service Unreachable and the following error in mod_jk.log:

Failed opening socket to (::1:8009) (errno=111) 
connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111) 
sending request to tomcat failed (recoverable), because of error during request sending (attempt=2) 
connecting to tomcat failed. 
service failed, worker <NODE_NAME> is in error state 
All tomcat instances are busy or in error state 
All tomcat instances failed, no more workers left

Cause

The value in the field JKWorkerProperty worker.<NODE_NAME>.host does not match the IP address that the application server is running on.

Action

Ensure that the value in the field JKWorkerProperty worker.<NODE_NAME>.host matches the IP of the web server, as mentioned in Configuring Apache Web Server with Appian.

Affected Versions

This article applies to all versions of Appian using Apache as the Web Server.

Last Reviewed: November 2018

Tags: HTTP, apache, web server

DRAFT KB-XXXX HTTP 503 Service Unreachable with "Failed opening socket: Connecting to backend failed" error

Zach Puderbach — Mon, 12 Nov 2018 10:07:56 GMT

Revision 4 posted to Appian Knowledge Base by Zach Puderbach on 11/12/2018 10:07:56 AM

Symptoms

Apache Web Server has been configured to work with Appian. All components of Appian are running successfully. Apache is running successfully and reachable on the port configured with HTTPS.

Trying to reach https://<SITE_URL>/suite fails with HTTP 503 Service Unreachable and the following error in mod_jk.log:

Failed opening socket to (::1:8009) (errno=111) 
connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111) 
sending request to tomcat failed (recoverable), because of error during request sending (attempt=2) 
connecting to tomcat failed. 
service failed, worker <NODE_NAME> is in error state 
All tomcat instances are busy or in error state 
All tomcat instances failed, no more workers left

Cause

The value in the field JKWorkerProperty worker.<NODE_NAME>.host does not match the IP address that the application server is running on.

Action

Ensure that the value in the field JKWorkerProperty worker.<NODE_NAME>.host matches the IP of the web server, as mentioned in Configuring Apache Web Server with Appian.

Affected Versions

This article applies to all versions of Appian using Apache as the Web Server.

Last Reviewed: November 2018

Tags: HTTP, apache, web server

DRAFT KB-XXXX HTTP 503 Service Unreachable with error "Failed opening socket: Connecting to backend failed"

Zach Puderbach — Mon, 12 Nov 2018 09:24:58 GMT

Revision 3 posted to Appian Knowledge Base by Zach Puderbach on 11/12/2018 9:24:58 AM

Symptoms

Apache Web Server has been configured to work with Appian. All components of Appian are running successfully. Apache is running successfully.

Trying to reach https://<SITE_URL>/suite fails with HTTP 503 Service Unreachable and the following error in mod_jk.log:

Failed opening socket to (::1:8009) (errno=111) 
connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111) 
sending request to tomcat failed (recoverable), because of error during request sending (attempt=2) 
connecting to tomcat failed. 
service failed, worker node1 is in error state 
All tomcat instances are busy or in error state 
All tomcat instances failed, no more workers left

Cause

the IP field isn't not configured properly

Action

Ensure that the IP field matches the IP of the web server as mentioned in Configuring Apache Web Server with Appian.

Affected Versions

This article applies to all versions of Appian using Apache as the Web Server.

Last Reviewed: November 2018

Tags: HTTP, apache, web server

DRAFT KB-XXXX HTTP 503 Service Unreachable with error "Failed opening socket: Connecting to backend failed"

Zach Puderbach — Fri, 09 Nov 2018 22:36:04 GMT

Revision 1 posted to Appian Knowledge Base by Zach Puderbach on 11/9/2018 10:36:04 PM

Symptoms

Apache Web Server has been configured to work with Appian. All components of Appian are running successfully.

Cause

the IP field isn't not configured properly

Action

Ensure that the IP field matches the IP of the web server as mentioned in Configuring Apache Web Server with Appian.

Affected Versions

This article applies to all versions of Appian using Apache as the Web Server.

Last Reviewed: November 2018

Tags: HTTP, apache, web server

DRAFT KB-XXXX HTTP 503 Service Unreachable with error "Failed opening socket: Connecting to backend failed"

Zach Puderbach — Fri, 09 Nov 2018 17:49:24 GMT

Revision 2 posted to Appian Knowledge Base by Zach Puderbach on 11/9/2018 5:49:24 PM

Symptoms

Apache Web Server has been configured to work with Appian. All components of Appian are running successfully. Apache is running successfully.

Trying to reach https://<SITE_URL>/suite fails with HTTP 503 Service Unreachable and the following error in mod_jk.log:

Failed opening socket to (::1:8009) (errno=111) 
connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111) 
sending request to tomcat failed (recoverable), because of error during request sending (attempt=2) 
connecting to tomcat failed. 
service failed, worker node1 is in error state 
All tomcat instances are busy or in error state 
All tomcat instances failed, no more workers left

Cause

the IP field isn't not configured properly

Action

Ensure that the IP field matches the IP of the web server as mentioned in Configuring Apache Web Server with Appian.

Affected Versions

This article applies to all versions of Appian using Apache as the Web Server.

Last Reviewed: November 2018

Tags: HTTP, apache, web server