KB-1602 News posts missing in Tempo

Parmida Borhani — Thu, 06 Aug 2020 00:19:00 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 8/6/2020 12:19:00 AM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

News posts are stored in the Appian primary data source in the 'tp_feed_entry' table. These posts are indexed for quick retrieval. If these indices become corrupt, indexing must restart, which causes only new entries to be stored and displayed in Tempo. The following sections explain how the posts are indexed based on the Appian version:

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupt.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Confirm the environment is pointing to the correct primary data source.
Once confirmed, connect to the primary data source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the next step.
Recreate the search server indices. Resetting the search server indices can resolve a number of other issues. See KB-1082 for more symptoms regarding issues related to the search server indices, as well as steps on how to perform the reset.

WARNING: These steps should be performed outside of business hours to avoid any potential performance impact.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: August 2020

Tags: search server, news, infrastructure

KB-1602 News posts missing in Tempo

Rebecca Jonas — Mon, 27 Jan 2020 18:05:18 GMT

Revision 32 posted to Appian Knowledge Base by Rebecca Jonas on 1/27/2020 6:05:18 PM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupt.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct primary data source.
Once confirmed, connect to the primary data source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version.

WARNING: These steps should be performed outside of business hours to avoid any potential performance impact.

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Later

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Note: Resetting the search server indices can resolve a number of other issues. See KB-1082 for more symptoms regarding issues related to the search server indices.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: January 2020

Tags: search server, news, infrastructure

KB-1602 News posts missing in Tempo

Rebecca Jonas — Mon, 27 Jan 2020 18:05:01 GMT

Revision 31 posted to Appian Knowledge Base by Rebecca Jonas on 1/27/2020 6:05:01 PM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupt.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct primary data source.
Once confirmed, connect to the primary data source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version.

WARNING: These steps should be performed outside of business hours to avoid any potential performance impact.

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Later

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Note: Resetting the search server indices can resolve a number of other issues. See KB-1082 for more symptoms regarding issues related to the search server indices.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news, infrastructure

KB-1602 News posts missing in Tempo

Jordan Horwat — Wed, 27 Jun 2018 13:53:48 GMT

Revision 30 posted to Appian Knowledge Base by Jordan Horwat on 6/27/2018 1:53:48 PM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupt.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct primary data source.
Once confirmed, connect to the primary data source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Later

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Note: Resetting the search server indices can resolve a number of other issues. See KB-1082 for more symptoms regarding issues related to the search server indices.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news, infrastructure

DRAFT KB-XXXX News posts missing in Tempo

Jordan Horwat — Wed, 27 Jun 2018 09:20:41 GMT

Revision 29 posted to Appian Knowledge Base by Jordan Horwat on 6/27/2018 9:20:41 AM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupt.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct primary data source.
Once confirmed, connect to the primary data source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Later

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Note: Resetting the search server indices can resolve a number of other issues. See KB-1082 for more symptoms regarding issues related to the search server indices.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news, infrastructure

DRAFT KB-XXXX News posts missing in Tempo

Jordan Horwat — Wed, 27 Jun 2018 09:20:01 GMT

Revision 28 posted to Appian Knowledge Base by Jordan Horwat on 6/27/2018 9:20:01 AM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

News posts are stored in the Appian primary data source in the 'tp_feed_entry' table. These posts are indexed for quick retrieval. If these indices become corrupted, indexing must restart, which causes only new entries to be stored and displayed in Tempo. The following sections explain how the posts are indexed based on the Appian version:

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct primary data source.
Once confirmed, connect to the primary data source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Later

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Note: Resetting the search server indices can resolve a number of other issues. See KB-1082 for more symptoms regarding issues related to the search server indices.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news, infrastructure

DRAFT KB-XXXX News posts missing in Tempo

Jordan Horwat — Wed, 27 Jun 2018 09:15:54 GMT

Revision 27 posted to Appian Knowledge Base by Jordan Horwat on 6/27/2018 9:15:54 AM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct primary data source.
Once confirmed, connect to the primary data source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Note: Resetting the search server indices can resolve a number of other issues. See KB-1082 for more symptoms regarding issues related to the search server indices.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news, infrastructure

DRAFT KB-XXXX News posts missing in Tempo

Parmida Borhani — Tue, 26 Jun 2018 23:48:33 GMT

Revision 26 posted to Appian Knowledge Base by Parmida Borhani on 6/26/2018 11:48:33 PM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Note: resetting the search server indices can resolve a number of other issues. See KB-1082 for more symptoms regarding issues related to the search server indices.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news, infrastructure

DRAFT KB-XXXX News posts missing in Tempo

Jordan Horwat — Tue, 26 Jun 2018 09:32:44 GMT

Revision 25 posted to Appian Knowledge Base by Jordan Horwat on 6/26/2018 9:32:44 AM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Note: resetting the search server indices can resolve a number of other issues. See KB-1082 for more symptoms regarding issues related to the search server indices.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News posts missing in Tempo

Jordan Horwat — Tue, 26 Jun 2018 09:32:24 GMT

Revision 24 posted to Appian Knowledge Base by Jordan Horwat on 6/26/2018 9:32:24 AM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Note: resetting the search server indices can resolve a number of other issues. See KB-1082 for more symptoms related to the search server indices.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News posts missing in Tempo

Jordan Horwat — Tue, 26 Jun 2018 09:22:57 GMT

Revision 23 posted to Appian Knowledge Base by Jordan Horwat on 6/26/2018 9:22:57 AM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Later

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News Posts missing in Tempo

Jordan Horwat — Mon, 25 Jun 2018 14:05:09 GMT

Revision 22 posted to Appian Knowledge Base by Jordan Horwat on 6/25/2018 2:05:09 PM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

News posts are stored in the Appian Primary Data Source in the 'tp_feed_entry' table. These posts are indexed for quick retrieval. If these indices become corrupted, indexing must restart, which causes only new entries to be stored and displayed in Tempo. The following sections explain how the posts are indexed based on the Appian version:

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Beyond

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If search server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News Posts missing in Tempo

Jordan Horwat — Fri, 22 Jun 2018 16:26:29 GMT

Revision 21 posted to Appian Knowledge Base by Jordan Horwat on 6/22/2018 4:26:29 PM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

News posts are stored in the Appian Primary Data Source in the 'tp_feed_entry' table. For quick retrieval, these posts are indexed. If these indices become corrupted, indexing must restart, which causes only new entries to be stored and displayed in Tempo. The following sections explain how the posts are indexed based on the Appian version:

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Beyond

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If Search Server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News Posts missing in Tempo

Jordan Horwat — Fri, 22 Jun 2018 16:26:11 GMT

Revision 20 posted to Appian Knowledge Base by Jordan Horwat on 6/22/2018 4:26:11 PM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Beyond

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If Search Server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the news post entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News Posts missing in Tempo

Jordan Horwat — Fri, 22 Jun 2018 16:25:41 GMT

Revision 19 posted to Appian Knowledge Base by Jordan Horwat on 6/22/2018 4:25:41 PM

Symptoms

News posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Beyond

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If Search Server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News Posts missing in Tempo

Jordan Horwat — Fri, 22 Jun 2018 16:23:28 GMT

Revision 18 posted to Appian Knowledge Base by Jordan Horwat on 6/22/2018 4:23:28 PM

Symptoms

news posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These news posts are indexed purely by the Apache Lucene software. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Beyond

These news posts are not purely indexed by Appian Lucene. Starting with Appian 17.2, the search server began to assume the role of indexing. This is why the <APPIAN_HOME>\_admin\search-local directory in 17.2 contains both the index-primary and search-server folders.
Starting with Appian 17.3, these news posts are purely indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If Search Server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old news posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News Posts missing in Tempo

Jordan Horwat — Fri, 22 Jun 2018 16:18:26 GMT

Revision 17 posted to Appian Knowledge Base by Jordan Horwat on 6/22/2018 4:18:26 PM

Symptoms

News Posts before a specific date have disappeared from Tempo.

Cause

News Posts are stored in the Appian Primary Data Source in the 'tp_feed_entry' table. For quick retrieval, these posts are indexed. If these indices become corrupted, indexing must restart, which causes only new entries to be stored and displayed in Tempo. The following sections explain how the posts are indexed based on the Appian version:

Appian 17.1

These News Posts are indexed purely by Apache Lucene. The indices are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Beyond

These News Posts are indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If Search Server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old News Posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News Posts missing in Tempo

Jordan Horwat — Fri, 22 Jun 2018 16:17:54 GMT

Revision 16 posted to Appian Knowledge Base by Jordan Horwat on 6/22/2018 4:17:54 PM

Symptoms

News Posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These News Posts are indexed by Apache Lucene. The index files are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.

Appian 17.2 and Beyond

These News Posts are indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If Search Server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old News Posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News Posts missing in Tempo

Jordan Horwat — Fri, 22 Jun 2018 16:17:34 GMT

Revision 15 posted to Appian Knowledge Base by Jordan Horwat on 6/22/2018 4:17:34 PM

Symptoms

News Posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These News Posts are indexed by Apache Lucene. The index files are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Explain how this can get corrupted.

Appian 17.2 and Beyond

These News Posts are indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If Search Server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old News Posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News Posts missing in Tempo

Jordan Horwat — Fri, 22 Jun 2018 16:16:26 GMT

Revision 14 posted to Appian Knowledge Base by Jordan Horwat on 6/22/2018 4:16:26 PM

Symptoms

News Posts before a specific date have disappeared from Tempo.

Cause

Appian 17.1

These News Posts are indexed by Apache Lucene. The index files are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Explain how this can get corrupted.

Appian 17.2 and Beyond

These News Posts are indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If Search Server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old News Posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local\ directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news

DRAFT KB-XXXX News Posts missing in Tempo

Jordan Horwat — Fri, 22 Jun 2018 16:13:25 GMT

Revision 13 posted to Appian Knowledge Base by Jordan Horwat on 6/22/2018 4:13:25 PM

Symptoms

News Posts before a specific date have disappeared from Tempo.

Cause

News Posts are stored in the Appian Primary Data Source in the 'tp_feed_entry' table. For quick retrieval, these posts are indexed. If these indices become corrupted, indexing must restart, which causes only new entries to be stored and displayed in Tempo. The sections below explain how the posts are indexed based on the Appian version:

Appian 17.1

These News Posts are indexed by Apache Lucene. The index files are stored in the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Explain how this can get corrupted.

Appian 17.2 and Beyond

These News Posts are indexed by the search server. The index files are stored in the <APPIAN_HOME>\_admin\search-local\search-server\data\appian-search-cluster\nodes\0\indices directory.
If Search Server experiences an issue (i.e. crashes due to network issue or runs out of disk space), the indices may become corrupted.
The root cause of the search server crash can be determined by examining the logs located at <APPIAN_HOME>\logs\search-server.

Action

Review the <JBOSS_HOME>\standalone\deployments\*-ds.xml and confirm that the environment is pointing to the correct Primary Data Source.
Once confirmed, connect to the Primary Data Source and run the following query: SELECT * FROM tp_feed_entry ORDER BY id ASC;
Inspect the content returned by the query. If the content contains old News Posts (that are currently missing from Tempo), proceed to the following steps based on the corresponding Appian version (Note: please perform these steps outside of business hours to avoid any potential performance impact):

Appian 17.1

In the <APPIAN_HOME>\_admin\search-local\index-primary directory, open the lastsync.properties file.
Delete the contents of the lastsync.properties file and save it.
Wait a few minutes and check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

If the above procedure does not resolve the issue, proceed with the following steps:

Stop Appian.
Delete the the <APPIAN_HOME>\_admin\search-local\index-primary directory.
Start Appian.
Check that the lastsync.properties file has been repopulated with a new timestamp and that the News Feed entries are now showing up.

Appian 17.2 and Beyond

Stop the application server and search server.
Delete the the <APPIAN_HOME>\_admin\search-local\ directory.
Start the application server and search server.

Affected Versions

This article applies to Appian 17.1 and later.

Last Reviewed: June 2018

Tags: search server, news