KB-1641 Tasks no longer available and InvalidShardIdAssignment errors displayed

Jordan Horwat — Fri, 15 Feb 2019 14:58:26 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 2/15/2019 2:58:26 PM

Symptoms

When upgrading from Appian version 17.4 or earlier to Appian 18.1 or later, the following error may be seen in the application server logs concerning an Invalid Shard Id Assignment:

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

End users may also see that all or certain sets of user tasks are no longer visible in the Appian environment.

This may also occur in a new installation of Appian 18.1 or above.

Cause

The application server and engines are unable to communicate correctly. This is frequently caused by a misconfiguration in the appian-topology.xml or a mismatch with the hostname configured on the server.

The hostname or IP address for each engine must match what is listed in the appian-topology.xml file configurations. This is particularly important for the execution and analytics engines, as they match their local information with the entries in the appian-topology.xml file on startup in order to determine which shard (engine id) they are (execution and analytics engines come in pairs in Appian and usually have 3 or more pairs running in an environment). If the shard values do not match, then the engine will fail to identify itself properly and result in the output above.

Action

First, ensure that the hostname of the server running the Appian engines on matches the hostname value present in the appian-topology.xml file. If not, then the topology file must match the server hostname. If the server has more than one valid hostname for the machine, then the hostname being used in the appian-toplogy.xml file must be the top, first most entry in the OS hosts file.

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts.
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts.

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Second, in a distributed environment, ensure the hostname matches in every instance of the appian-topology.xml and ensure the hostname is resolved correctly on all nodes. If the issue persists or there are constraints that prevent the hostname being resolved correctly from all nodes, update the appian-topology.xml file to use the server IP instead of the hostname.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: February 2019

Tags: engines, infrastructure, service manager, network

KB-1641 Tasks no longer available and InvalidShardIdAssignment errors displayed

Jordan Horwat — Fri, 15 Feb 2019 14:58:06 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 2/15/2019 2:58:06 PM

Symptoms

When upgrading from Appian version 17.4 or earlier to Appian 18.1 or later, the following error may be seen in the application server logs concerning an Invalid Shard Id Assignment:

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

End users may also see that all or certain sets of user tasks are no longer visible in the Appian environment.

This may also occur in a new installation of Appian 18.1 or above.

Cause

Action

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: February 2019

Tags: engines, infrastructure, service manager, network

KB-1641 Tasks no longer available and InvalidShardIdAssignment errors displayed

Jordan Horwat — Fri, 15 Feb 2019 14:56:20 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 2/15/2019 2:56:20 PM

Symptoms

When upgrading from Appian version 17.4 or earlier to Appian 18.1 or later, the following error may be seen in the application server logs concerning an Invalid Shard Id Assignment:

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

End users may also see that all or certain sets of user tasks are no longer visible in the Appian environment.

This may also occur in a new installation of Appian 18.1 or above.

Cause

Action

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Second, in a distributed environment, ensure the hostname matches in every instance of the appian-topology.xml and ensure the hostname is resolved correctly on all nodes.

If the issue persists or there are constraints that prevent the hostname being resolved correctly from all nodes, update the appian-topology.xml file to use the server IP instead of the hostname.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: February 2019

Tags: engines, infrastructure, service manager, network

KB-1641 Tasks no longer available and InvalidShardIdAssignment errors displayed

Jordan Horwat — Fri, 15 Feb 2019 14:53:35 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 2/15/2019 2:53:35 PM

Symptoms

When upgrading from Appian version 17.4 or earlier to Appian 18.1 or later, the following error may be seen in the application server logs concerning an Invalid Shard Id Assignment:

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

End users may also see that all or certain sets of user tasks are no longer visible in the Appian environment.

This may also occur in a new installation of Appian 18.1 or above.

Cause

Action

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: August 2018

Tags: engines, infrastructure, service manager, network

KB-1641 Tasks no longer available and InvalidShardIdAssignment errors displayed

Parmida Borhani — Thu, 09 Aug 2018 01:27:39 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 8/9/2018 1:27:39 AM

Symptoms

When upgrading from Appian version 17.4 or earlier to Appian 18.1 or later, the following error may be seen in the application server logs concerning an Invalid Shard Id Assignment:

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

End users may also see that all or certain sets of user tasks are no longer visible in the Appian environment.

This may also occur in a new installation of Appian 18.1 or above.

Cause

Action

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: August 2018

Tags: engines, infrastructure, service manager, network

KB-1641 Tasks no longer available and InvalidShardIdAssignment errors displayed

Parmida Borhani — Wed, 08 Aug 2018 21:25:36 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 8/8/2018 9:25:36 PM

Symptoms

When upgrading from Appian version 17.4 or earlier to Appian 18.1 or later, the following error may be seen in the application server logs concerning an Invalid Shard Id Assignment:

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

End users may also see that all or certain sets of user tasks are no longer visible in the Appian environment.

This may also occur in a new installation of Appian 18.1 or above.

Cause

Action

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: August 2018

Tags: known issues, engines, infrastructure, service manager, network, open issues

KB-1641 Tasks no longer available and InvalidShardIdAssignment errors displayed

Parmida Borhani — Wed, 08 Aug 2018 21:24:45 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 8/8/2018 9:24:45 PM

Symptoms

When upgrading from Appian version 17.4 or earlier to Appian 18.1 or later, the following error may be seen in the application server logs concerning an Invalid Shard Id Assignment:

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

End users may also see that all or certain sets of user tasks are no longer visible in the Appian environment.

This may also occur in a new installation of Appian 18.1 or above.

Cause

Action

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: August 2018

Tags: known issues, engines, infrastructure, service manager, network

DRAFT KB-XXXX Tasks no longer available and InvalidShardIdAssignment errors displayed

Parmida Borhani — Wed, 08 Aug 2018 21:23:11 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 8/8/2018 9:23:11 PM

Symptoms

When upgrading from Appian version 17.4 or earlier to Appian 18.1 or later, the following error may be seen in the application server logs concerning an Invalid Shard Id Assignment:

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

End users may also see that all or certain sets of user tasks are no longer visible in the Appian environment.

This may also occur in a new installation of Appian 18.1 or above.

Cause

Action

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: Aug 2018

Tags: known issues, engines, infrastructure, service manager, network

DRAFT KB-XXXX Tasks no longer available and InvalidShardIdAssignment errors displayed

chase.putnam — Wed, 08 Aug 2018 19:29:20 GMT

Revision 3 posted to Appian Knowledge Base by chase.putnam on 8/8/2018 7:29:20 PM

Symptoms

In upgrading from an Appian version 17.4 or below to an Appian version 18.1 or above, the following error may be seen in your application server logs concerning an Invalid Shard Id Assignment per the following:

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

End users may also see that all or certain sets of user tasks are no longer visible in the Appian environment.

This may also occur in a new installation of Appian 18.1 or above.

Cause

Action

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Affected Versions

Appian 18.1 or later

Last Reviewed: 08-Aug-2018

Tags: known issues, engines, Architecture, infrastructure, service manager, network

DRAFT KB-XXXX Tasks no longer available and InvalidShardIdAssignment errors displayed

chase.putnam — Tue, 07 Aug 2018 19:45:17 GMT

Revision 2 posted to Appian Knowledge Base by chase.putnam on 8/7/2018 7:45:17 PM

Symptoms

In a new installation or an upgrade from an Appian version 17.4 or below to Appian 18.1 or above, you may encounter an error in your application server logs concerning an Invalid Shard Id Assignment like the following:

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

You may also see that all or certain sets of user tasks are no longer present in your Appian environment.

Cause

Action

First, ensure that the hostname of the server you are running the engines on matches the hostname value present in the appian-topology.xml file. If not, then you can correct this so that the topology file matches the server hostname. If your server has more than one valid hostname for the machine, then you must ensure that the hostname being used in the appian-toplogy.xml file is the very top, first most entry in your OS hosts file.

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Affected Versions

Appian 18.1 and 18.2

Last Reviewed

08-Aug-2018

Tags: known issues, engines, Architecture, infrastructure, service manager, network

DRAFT KB-XXXX Tasks no longer available and InvalidShardIdAssignment errors displayed

chase.putnam — Tue, 07 Aug 2018 01:17:06 GMT

Revision 1 posted to Appian Knowledge Base by chase.putnam on 8/7/2018 1:17:06 AM

Symptoms

HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) YYYY-MM-DD HH:MM:SS.mmm [Appian MultithreadedMapper - 1] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-analytics1:Socket[addr=server01.dev.appian.com/12.13.14.15,port=5020,localport=51307],in,out,RW,LittleEndian (read), offset=29]
HH:MM:SS.mmm INFO [stdout] (Appian MultithreadedMapper - 1) com.appiancorp.kougar.driver.exceptions.Signal: InvalidShardIdAssignment

You may also see that all or certain sets of user tasks are no longer present in your Appian environment.

Cause

Actions

For Windows, the hosts file is typically located at: C:\Windows\System32\drivers\etc\hosts
For Linux, the hosts file location varies by Linux distro but can typically be found at: /etc/hosts

This will allow the Appian execution and analytics engines to communicate properly, detect their valid shard id, and propagate data between each other successfully.

Tags: known issues, engines, Architecture, infrastructure, service manager, network