KB-1548 Cannot run program "jps" error when starting Service Manager

Parmida Borhani — Wed, 23 Mar 2022 02:55:38 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 3/23/2022 2:55:38 AM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, one of the following errors are returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=13, Permission denied

Cause

There are several possible causes for this issue.

If you are using Oracle Java, this error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian System Requirements, JDK is the supported option. To check the JAVA_HOME variable:
- In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
- In Linux, type echo $JAVA_HOME in a terminal to view the Java path.
If you are using OpenJDK, the basic download of OpenJDK does not ship with JPS.
An external program, such an antivirus software, kills the Service Manager script before the Appian services start.

Action

To resolve the issue, follow the Appian Installation Prerequisites documentation to set up the JAVA_HOME and PATH variables to point to the JDK. If using OpenJDK, ensure that the developer edition is being used.
Ensure the Appian user has appropriate permissions to run jps command.
Ensure external programs do not interfere with the Appian startup.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: March 2022

Tags: java, installation, infrastructure, service manager

KB-1548 Cannot run program "jps" error when starting Service Manager

Jordan Horwat — Thu, 14 Feb 2019 17:21:18 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 2/14/2019 5:21:18 PM

Symptoms

Symptom 1

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Symptom 2

Zookeeper service initially starts successfully as per the <APPIAN_HOME>\logs\service-manager\zookeeper\zookeeper.log:

2019-01-22 21:01:44,744 [myid:1] - INFO [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:2181
2019-01-22 21:01:44,747 [myid:1] - INFO [main:QuorumPeer@1158] - tickTime set to 2000

However, Zookeeper then errors out immediately with the following error in the <APPIAN_HOME>\logs\service-manager\zookeeper\zookeeper.log:

2019-01-22 21:02:04,966 [myid:1] - INFO [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:2181
2019-01-22 21:02:04,967 [myid:1] - ERROR [main:QuorumPeerMain@92] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

Cause

There are two possible causes for this issue.

If you are using Oracle Java, this error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian System Requirements, JDK is the supported option. To check the JAVA_HOME variable:
- In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
- In Linux, type echo $JAVA_HOME in a terminal to view the Java path.
If you are using OpenJDK, the basic download of OpenJDK does not ship with JPS.

Action

To resolve the issue, follow the Appian Installation Prerequisites documentation to set up the JAVA_HOME and PATH variables to point to the JDK. If using OpenJDK, ensure that the developer edition is being used.
Ensure the Appian user has appropriate permissions to run jps command.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: February 2019

Tags: java, installation, infrastructure, service manager

KB-1548 Cannot run program "jps" error when starting Service Manager

Jordan Horwat — Thu, 14 Feb 2019 17:20:59 GMT

Revision 11 posted to Appian Knowledge Base by Jordan Horwat on 2/14/2019 5:20:59 PM

Symptoms

Symptom 1

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Symptom 2

Zookeeper service initially starts successfully as per the <APPIAN_HOME>\logs\service-manager\zookeeper\zookeeper.log:

2019-01-22 21:01:44,744 [myid:1] - INFO [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:2181
2019-01-22 21:01:44,747 [myid:1] - INFO [main:QuorumPeer@1158] - tickTime set to 2000

However, Zookeeper then errors out immediately with the following error in the <APPIAN_HOME>\logs\service-manager\zookeeper\zookeeper.log:

2019-01-22 21:02:04,966 [myid:1] - INFO [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:2181
2019-01-22 21:02:04,967 [myid:1] - ERROR [main:QuorumPeerMain@92] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

Cause

There are two possible causes for this issue.

If you are using Oracle Java, this error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian System Requirements, JDK is the supported option. To check the JAVA_HOME variable:
- In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
- In Linux, type echo $JAVA_HOME in a terminal to view the Java path.
If you are using OpenJDK, the basic download of OpenJDK does not ship with JPS.

Action

To resolve the issue, follow the Appian Installation Prerequisites documentation to set up the JAVA_HOME and PATH variables to point to the JDK. If using OpenJDK, ensure that the developer edition is being used.
Ensure the Appian user has appropriate permissions to run "jps" command.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: February 2019

Tags: java, installation, infrastructure, service manager

KB-1548 Cannot run program "jps" error when starting Service Manager

Jordan Horwat — Fri, 08 Feb 2019 16:10:01 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 2/8/2019 4:10:01 PM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Cause

There are two possible causes for this issue.

If you are using Oracle Java, this error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian System Requirements, JDK is the supported option. To check the JAVA_HOME variable:
- In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
- In Linux, type echo $JAVA_HOME in a terminal to view the Java path.
If you are using OpenJDK, the basic download of OpenJDK does not ship with JPS.

Action

To resolve the issue, follow the Appian Installation Prerequisites documentation to set up the JAVA_HOME and PATH variables to point to the JDK. If using OpenJDK, ensure that the developer edition is being used.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: February 2019

Tags: java, installation, infrastructure, service manager

KB-1548 Cannot run program "jps" error when starting Service Manager

Jordan Horwat — Fri, 08 Feb 2019 16:08:53 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 2/8/2019 4:08:53 PM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Cause

There are two possible causes for this issue.

If you are using Oracle Java, this error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian System Requirements, JDK is the supported option. To check the JAVA_HOME variable:
- In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
- In Linux, type echo $JAVA_HOME in a terminal to view the Java path.
If you are using OpenJDK, the basic download of OpenJDK does not ship with JPS.

Action

To resolve the issue, follow the Appian documentation on setting up the JAVA_HOME and PATH variables to point to the JDK. If using OpenJDK, ensure that the developer edition is being used.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: February 2019

Tags: java, infrastructure, service manager

KB-1548 Cannot run program "jps" error when starting Service Manager

Parmida Borhani — Thu, 03 Jan 2019 23:58:32 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 1/3/2019 11:58:32 PM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Cause

There are two possible causes for this issue.

If you are using Oracle Java, this error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian system requirements, JDK is the supported option. To check the JAVA_HOME variable:
- In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
- In Linux, type echo $JAVA_HOME in a terminal to view the Java path.
If you are using OpenJDK, the basic download of OpenJDK does not ship with JPS.

Action

To resolve the issue, follow the Appian documentation on setting up the JAVA_HOME and PATH variables to point to the JDK. If using OpenJDK, ensure that the developer edition is being used.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: January 2019

Tags: java, infrastructure, service manager

KB-1548 Cannot run program "jps" error when starting Service Manager

Parmida Borhani — Mon, 23 Jul 2018 03:22:32 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 7/23/2018 3:22:32 AM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Cause

This error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian system requirements, JDK is the supported option.

To check the JAVA_HOME variable:

In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
In Linux, type echo $JAVA_HOME in a terminal to view the Java path.

Action

To resolve the issue, follow the Appian documentation on setting up the JAVA_HOME and PATH variables to point to the JDK.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: infrastructure, service manager

KB-1548 Cannot run program "jps" error when starting Service Manager

Parmida Borhani — Fri, 13 Apr 2018 00:57:47 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 4/13/2018 12:57:47 AM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Cause

This error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian system requirements, JDK is the supported option.

To check the JAVA_HOME variable:

In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
In Linux, type echo $JAVA_HOME in a terminal to view the Java path.

Action

To resolve the issue, follow the Appian documentation on setting up the JAVA_HOME and PATH variables to point to the JDK.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: service manager

DRAFT KB-XXXX Cannot run program "jps" error when starting Service Manager

Parmida Borhani — Thu, 12 Apr 2018 20:56:25 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 4/12/2018 8:56:25 PM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Cause

This error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian system requirements, JDK is the supported option.

To check the JAVA_HOME variable:

In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
In Linux, type echo $JAVA_HOME in a terminal to view the Java path.

Action

To resolve the issue, follow the Appian documentation on setting up the JAVA_HOME and PATH variables to point to the JDK.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: service manager

DRAFT KB-XXXX Cannot run program "jps" error when starting Service Manager

Khalil Ben Naceur — Thu, 12 Apr 2018 17:51:36 GMT

Revision 4 posted to Appian Knowledge Base by Khalil Ben Naceur on 4/12/2018 5:51:36 PM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Cause

This error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian system requirements, JDK is the supported option.

To check the JAVA_HOME variable:

In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
In Linux, type echo $JAVA_HOME in a terminal to view the Java path.

Action

To resolve the issue, follow the Appian documentation on setting up the JAVA_HOME and PATH variables to point to the JDK.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: service manager

DRAFT KB-XXXX Cannot run program "jps" error when starting Service Manager

Khalil Ben Naceur — Thu, 12 Apr 2018 17:51:18 GMT

Revision 3 posted to Appian Knowledge Base by Khalil Ben Naceur on 4/12/2018 5:51:18 PM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Cause

This error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian system requirements, JDK is the supported option.

To check the JAVA_HOME variable:

In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
In Linux, type echo $JAVA_HOME in a terminal to view the Java path.

Action

To resolve the issue, follow the Appian documentation on setting up the JAVA_HOME and PATH variables to point to the JDK.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: service manager

DRAFT KB-XXXX Cannot run program "jps" error when starting Service Manager

Parmida Borhani — Fri, 06 Apr 2018 00:19:24 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 4/6/2018 12:19:24 AM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Cause

This error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian system requirements, JDK is the supported option.

To check the JAVA_HOME variable:

In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
In Linux, type echo $JAVA_HOME in a terminal to view the Java path.

Action

To resolve the issue, change the JAVA_HOME path to point to the JDK:

In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to point to the correct JDK path.
In Linux, one way would be to run the following commands as the root user:
1. export JAVA_HOME=<PATH_TO_JDK>
2. export PATH=${PATH}:{JAVA_HOME}/bin

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: service manager

DRAFT KB-XXXX Cannot run program "jps" error when starting Service Manager

Khalil Ben Naceur — Thu, 05 Apr 2018 20:56:20 GMT

Revision 1 posted to Appian Knowledge Base by Khalil Ben Naceur on 4/5/2018 8:56:20 PM

Symptoms

When executing a Service Manager script in the <APPIAN_HOME>/services/bin directory, the following error is returned:

Exception thrown while attempting to retrieve process info for java process with main Class name QuorumPeerMain. java.io.IOException: Cannot run program "jps": error=2, No such file or directory
...
Caused by: java.io.IOException: error=2, No such file or directory

Cause

This error is returned when the JAVA_HOME path is set to JRE, rather than JDK. As per the Appian system requirements, JDK is the supported option.

To check the JAVA_HOME variable:

In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to view the JDK path.
In Linux, type echo $JAVA_HOME in a terminal to view the Java path.

Action

To resolve the issue, change the JAVA_HOME path to point to the JDK:

In Windows, right click My Computer and select Properties. On the Advanced tab, select Environment Variables, and edit JAVA_HOME to point to the correct JDK path.
In Linux, one way would be to run the following commands as the root user:
1. export JAVA_HOME=<PATH_TO_JDK>
2. export PATH=${PATH}:{JAVA_HOME}/bin

Affected Versions

This article applies to Appian 17.3 and later

Tags: service manager