KB-2150 Process Analytics engine issues from mismatched hostname

James Lee — Thu, 10 Sep 2020 21:39:39 GMT

Current Revision posted to Appian Knowledge Base by James Lee on 9/10/2020 9:39:39 PM

Symptoms

The below error is found in the db_PA* logs located in the <APPIAN_HOME>/logs directory:

2019-11-27 03:33:15 [PA00XX1] {paXXX.kdb ,XXXXXX} (Default) ERROR .a.p.ANLYZE.i "This engine is recognized as host [localhost.localdomain] port [XXXX] for local development on a single machine (do not use in production, as this matches all machines), but this did not match appian-topology.xml's host [<HOSTNAME>] port [XXXX]."

The symptoms may also include:

Users are unable to see any rows in process reports.
a!queryProcessAnalytics() returns an empty result.
The ResetAnalytics script fails to run.

Cause

The host name in the appian_topology.xml file does not match the host name in the server hosts file.

Action

Set the hostname in the topology file to match the hostname retrieved by running <APPIAN_HOME>/_admin/_scripts/licinfo.sh (.bat).

Note: The host name is case-sensitive.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: engines, license, infrastructure

KB-2150 Process Analytics issues from mismatched hostname

James Lee — Thu, 10 Sep 2020 21:39:26 GMT

Revision 5 posted to Appian Knowledge Base by James Lee on 9/10/2020 9:39:26 PM

Symptoms

The below error is found in the db_PA* logs located in the <APPIAN_HOME>/logs directory:

2019-11-27 03:33:15 [PA00XX1] {paXXX.kdb ,XXXXXX} (Default) ERROR .a.p.ANLYZE.i "This engine is recognized as host [localhost.localdomain] port [XXXX] for local development on a single machine (do not use in production, as this matches all machines), but this did not match appian-topology.xml's host [<HOSTNAME>] port [XXXX]."

The symptoms may also include:

Users are unable to see any rows in process reports.
a!queryProcessAnalytics() returns an empty result.
The ResetAnalytics script fails to run.

Cause

The host name in the appian_topology.xml file does not match the host name in the server hosts file.

Action

Set the hostname in the topology file to match the hostname retrieved by running <APPIAN_HOME>/_admin/_scripts/licinfo.sh (.bat).

Note: The host name is case-sensitive.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: engines, license, infrastructure

KB-XXXX Process Analytics issues from mismatched hostname

James Lee — Thu, 03 Sep 2020 14:07:47 GMT

Revision 4 posted to Appian Knowledge Base by James Lee on 9/3/2020 2:07:47 PM

Symptoms

The below error is found in the db_PA* logs located in the <APPIAN_HOME>/logs directory:

2019-11-27 03:33:15 [PA00XX1] {paXXX.kdb ,XXXXXX} (Default) ERROR .a.p.ANLYZE.i "This engine is recognized as host [localhost.localdomain] port [XXXX] for local development on a single machine (do not use in production, as this matches all machines), but this did not match appian-topology.xml's host [<HOSTNAME>] port [XXXX]."

The symptoms may also include:

Users are unable to see any rows in process reports.
a!queryProcessAnalytics() returns an empty result.
The ResetAnalytics script fails to run.

Cause

The host name in the appian_topology.xml file does not match the host name in the server hosts file.

Action

Set the hostname in the topology file to match the hostname retrieved by running <APPIAN_HOME>/_admin/_scripts/licinfo.sh (.bat).

Note: The host name is case-sensitive.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: engines, license, infrastructure

KB-XXXX Process Analytics issues from mismatched hostname

Sean Kim — Thu, 20 Aug 2020 07:24:58 GMT

Revision 2 posted to Appian Knowledge Base by Sean Kim on 8/20/2020 7:24:58 AM

Symptoms

Users may be unable to see any rows in process reports. Anything that uses a!queryProcessAnalytics() will return an empty result.

Users may also not be able to run the Reset Analytics script.

The db_PA* logs would show the following error:

2019-11-27 03:33:15 [PA00011] {pa291.kdb ,145351} (Default) ERROR .a.p.ANLYZE.i "This engine is recognized as host [localhost.localdomain] port [5021] for local development on a single machine (do not use in production, as this matches all machines), but this did not match appian-topology.xml's host [<HOSTNAME>] port [5023]."

Cause

The host name in the appian_topology.xml file does not match the host name in the server hosts file. Note that the host name must match in characters and is case-sensitive.

Action

Set the hostname in the topology file to match the hostname retrieved by <APPIAN_HOME>/_admin/_scripts/licinfo.sh (.bat).

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2020

Tags: engines, license, infrastructure

KB-XXXX Process Analytics issues from mismatched hostname

Sean Kim — Wed, 19 Aug 2020 09:06:49 GMT

Revision 1 posted to Appian Knowledge Base by Sean Kim on 8/19/2020 9:06:49 AM

Symptoms

Users may be unable to see any rows in process reports.

Users may also not be able to run the Reset Analytics script.

The db_PA* logs would show the following error:

2019-11-27 03:33:15 [PA00011] {pa291.kdb ,145351} (Default) ERROR .a.p.ANLYZE.i "This engine is recognized as host [localhost.localdomain] port [5021] for local development on a single machine (do not use in production, as this matches all machines), but this did not match appian-topology.xml's host [<HOSTNAME>] port [5023]."

Cause

The host name in the appian_topology.xml file does not match the host name in the server hosts file. Note that the host name must match in characters and is case-sensitive.

Action

Set the hostname in the topology file to match the hostname when retrieved by <APPIAN_HOME>/_admin/_scripts/licinfo.sh (.bat)

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2020

Tags: engines, license, infrastructure