KB-1694 Engine start up fails with Zookeeper "Address already in use" error

Parmida Borhani — Mon, 06 Jan 2020 01:57:44 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 1/6/2020 1:57:44 AM

Symptoms

Engine start-up fails after running the start.sh|bat script. Although port 2181 is free, the following error is found in the zookeeper.log located in <APPIAN_HOME>/logs/service-manager/zookeeper/:

ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start script located in the <APPIAN_HOME>/services/bin directory, the following error is observed in the command line prompt:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Users may also see the following output after running jps:

[user@server ~]$ jps
<PID> -- process information unavailable

Cause

There are two causes to this issue:

The Zookeeper ports (2181, 2888, and 3888) are either blocked or occupied by an orphan process.
The jps utility is not able to run due to invalid contents in the /tmp/hsperfdata_$APPIAN_USER folder (where $APPIAN_USER is the user running the Appian processes).

Action

Check the port availability with Administrator privileges.
Delete the /tmp/hsperfdata_$APPIAN_USER folder.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: January 2020

Tags: engines, zookeeper, installation, linux, infrastructure

KB-1694 Engine start up fails with Zookeeper "Address already in use" error

Parmida Borhani — Thu, 06 Sep 2018 01:36:50 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 9/6/2018 1:36:50 AM

Symptoms

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start script located in the <APPIAN_HOME>/services/bin directory, the following error is observed in the command line prompt:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error occurs when any of the zookeeper ports (2181, 2888, and 3888) are either blocked or occupied by an orphan process.

Action

Check the port availability with Administrator privileges.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, zookeeper, installation, linux, infrastructure

DRAFT KB-XXXX Engine start up fails with Zookeeper "Address already in use" error

Anirudh Rathi — Wed, 05 Sep 2018 09:31:53 GMT

Revision 10 posted to Appian Knowledge Base by Anirudh Rathi on 9/5/2018 9:31:53 AM

Symptoms

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start script located in the <APPIAN_HOME>/services/bin directory, the following error is observed in the command line prompt:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error occurs when any of the zookeeper ports (2181, 2888, and 3888) are either blocked or occupied by an orphan process.

Action

Check the port availability with Administrator privileges.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, zookeeper, installation, linux, infrastructure

DRAFT KB-XXXX Engine start up fails with Zookeeper "Address already in use" error

Parmida Borhani — Wed, 05 Sep 2018 02:41:29 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 9/5/2018 2:41:29 AM

Symptoms

Engine start-up fails while running Appian. Although port 2181 is free, the following error is found in the zookeeper.log located in <APPIAN_HOME>/logs/service-manager/zookeeper/:

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start script located in the <APPIAN_HOME>/services/bin directory, the following error is observed in the command line prompt:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error occurs when any of the zookeeper ports (2181, 2888, and 3888) are either blocked or occupied by an orphan process.

Action

Check the port availability with Administrator privileges.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, zookeeper, installation, linux, infrastructure

DRAFT KB-XXXX Engine start up fails with Zookeeper "Address already in use" error

Anirudh Rathi — Tue, 04 Sep 2018 09:21:13 GMT

Revision 8 posted to Appian Knowledge Base by Anirudh Rathi on 9/4/2018 9:21:13 AM

Symptoms

Engine start-up fails while running Appian. Although port 2181 is free, the following error is found in zookeeper.log located in <APPIAN_HOME>/logs/service-manager/zookeeper/:

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start script located in <APPIAN_HOME>/services/bin directory, following error is observed in the command line prompt:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error occurs when any of the zookeeper ports (2181, 2888, and 3888) are either blocked or occupied by an orphan process.

Action

Check the port availability with Administrator privileges.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: August 2018

Tags: engines, zookeeper, installation, linux, infrastructure

DRAFT KB-XXXX Engine start up fails with Zookeeper "Address already in use" error

Anirudh Rathi — Tue, 04 Sep 2018 09:19:58 GMT

Revision 7 posted to Appian Knowledge Base by Anirudh Rathi on 9/4/2018 9:19:58 AM

Symptoms

Engine start-up fails while running Appian on RHEL 7.4 and 7.5. Although port 2181 is free, the following error is found in zookeeper.log located in <APPIAN_HOME>/logs/service-manager/zookeeper/:

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start script located in <APPIAN_HOME>/services/bin directory, following error is observed in the command line prompt:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error occurs when any of the zookeeper ports (2181, 2888, and 3888) are either blocked or occupied by an orphan process.

Action

Check the port availability with Administrator privileges.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: August 2018

Tags: engines, zookeeper, installation, linux, infrastructure

DRAFT KB-XXXX Engine start up fails on RHEL 7.5 and RHEL 7.4 with "Address already in use" error

Jordan Horwat — Fri, 31 Aug 2018 15:12:46 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 8/31/2018 3:12:46 PM

Symptoms

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start script located in <APPIAN_HOME>/services/bin directory, following error is observed in the command line prompt:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error occurs when any of the zookeeper ports (2181, 2888, and 3888) are either blocked or occupied by an orphan process.

Action

Check the port availability with Administrator privileges.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: August 2018

Tags: engines, zookeeper, installation, linux, infrastructure

DRAFT KB-XXXX Engine start up fails on RHEL 7.5 and RHEL 7.4 with "Address already in use" error

Anirudh Rathi — Fri, 31 Aug 2018 14:20:57 GMT

Revision 5 posted to Appian Knowledge Base by Anirudh Rathi on 8/31/2018 2:20:57 PM

Symptoms

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start script located in <APPIAN_HOME>/services/bin directory, following error is observed in the command line prompt::

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error occurs when any of the zookeeper ports (2181, 2888 and 3888) are either blocked or occupied by an orphan process.

Action

Check the port availability with admin privileges.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: August 2018

Tags: engines, zookeeper, installation, linux, infrastructure

DRAFT KB-XXXX Engine start up fails on RHEL 7.5 and RHEL 7.4 with "Address already in use" error

Parmida Borhani — Thu, 30 Aug 2018 23:18:38 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 8/30/2018 11:18:38 PM

Symptoms

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start command, engine start-up has the following error in the command line prompt:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error occurs when any of the zookeeper ports (2181, 2888 and 3888) are either blocked or occupied by an orphan process.

Action

If a basic user is able to see zookeeper ports as available, check the port availability with admin privileges.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: August 2018

Tags: engines, zookeeper, installation, linux, infrastructure

DRAFT KB-XXXX Engine start up fails on RHEL 7.5 and RHEL 7.4 with "Address already in use" error

Anirudh Rathi — Thu, 30 Aug 2018 17:56:00 GMT

Revision 3 posted to Appian Knowledge Base by Anirudh Rathi on 8/30/2018 5:56:00 PM

Symptoms

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start command, engine start-up has the following error on command line prompt:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error occurs when any of the zookeeper port (2181, 2888 and 3888) is either blocked or occupied by an orphan process.

Action

If a basic user is able to see zookeeper ports as available, check the port availability with admin privileges.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: August 2018

Tags: engines, linux, infrastructure

DRAFT KB-XXXX Engine start up fails on RHEL 7.5 and RHEL 7.4 with "Address already in use" error

Anirudh Rathi — Mon, 27 Aug 2018 09:39:36 GMT

Revision 2 posted to Appian Knowledge Base by Anirudh Rathi on 8/27/2018 9:39:36 AM

Symptoms

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

After running the start command, engine start-up has the following error on command line prompt:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error is caused on RHEL 7.4 and RHEL 7.5 version.

Action

Check the server version and switch to RHEL 6.X or lower.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: August 2018

Tags: engines, linux, infrastructure

DRAFT KB-XXXX Engine start up fails on RHEL 7.5 and RHEL 7.4

Anirudh Rathi — Fri, 24 Aug 2018 20:59:57 GMT

Revision 1 posted to Appian Knowledge Base by Anirudh Rathi on 8/24/2018 8:59:57 PM

Symptoms

Engine start-up fails while running Appian on RHEL 7.4 and 7.5. Although port 2181 is free, following error is found in zookeeper.log located in <APPIAN_HOME>/logs/service-manager/zookeeper/

2018-08-20 04:46:51,819 [myid:] - ERROR [main:ZooKeeperServerMain@66] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

Engine start-up has following error:

waiting for process QuorumPeerMain
waiting for process QuorumPeerMain
process QuorumPeerMain not running after 10000 seconds
Unable to start service QuorumPeerMain
java.util.concurrent.TimeoutException: Process QuorumPeerMain did not launch within 10000 ms

Cause

This error is caused on RHEL 7.4 and RHEL 7.5 version.

Action

Check the server version and switch to RHEL 6.X or lower.

Affected Versions

This article applies to Appian 17.3 and later

Last Reviewed: August, 2018

Tags: engines, linux, infrastructure