Skip to content

Commit

Permalink
[DOCS-7775] Add troubleshooting topic in Search and Insight Engine 2.0 (
Browse files Browse the repository at this point in the history
#1600)

* [DOCS-7775] Add troubleshooting topic in Search and Insight Engine 2.0

* [DOCS-7775] Fix wording and formatting
  • Loading branch information
monikamichalska authored Nov 15, 2024
1 parent 47e0eee commit 00a478f
Showing 1 changed file with 35 additions and 4 deletions.
39 changes: 35 additions & 4 deletions insight-engine/latest/admin/monitor.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This task describes how to perform a full Solr reindex.

The task assumes you are using only one Solr instance for all nodes in the Alfresco Content Services cluster. If not, then you need to repeat the process on each Solr instance used in the cluster.

1. Confirm the location of the Solr core directories for archive and alfresco cores. This can be determined from the solrcore.properties file for both the cores. By default, the solrcore.properties file can be found at `<SOLR_HOME>/solrhome/alfresco/conf` or `<SOLR_HOME>/solrhome/archive/conf`. The Solr core location is defined in the `solrcore.properties` file as:
1. Confirm the location of the Solr core directories for archive and alfresco cores. This can be determined from the `solrcore.properties` file for both the cores. By default, the `solrcore.properties file` can be found at `<SOLR_HOME>/solrhome/alfresco/conf` or `<SOLR_HOME>/solrhome/archive/conf`. The Solr core location is defined in the `solrcore.properties` file as:

For Solr, the default data.dir.root path is:

Expand Down Expand Up @@ -130,7 +130,7 @@ The `SUMMARY` parameter provides the status of the tracking index and reports th
* `Docs/Tx`: indicates summary statistics for the number of documents per transaction. It supports additional information with &detail=true, &hist=true and &value=true.
* `Doc Transformation time (ms)`: indicates summary statistics for document transformation time. It supports additional information with &detail=true, &hist=true and &value=true.

## Troubleshooting
## Troubleshooting - transaction index failure

Use this information to repair a transaction that failed to index.

Expand Down Expand Up @@ -177,6 +177,37 @@ Use the following setting to specify an option core for the report. If it is abs

You can also fix index issues, check the index cache and backup individual indexes by using JMX. The status of the index can be checked using the JMX client on the **JMX MBeans > Alfresco > solrIndexes > `<store>`** tabs. The default view is the Solr core summary. The operations run the same consistency checks that are available by URL.

## Troubleshooting - unsearchable content

If content becomes unsearchable for some documents, it is possible that the necessary transformations failed and the documents are currently indexed with a `transform_failed` status.

> **Note:** For Enterprise installations (assuming the reason for these failed transformations is the temporary unavailability of the Transform Engines (T-Engines)), it is recommended to verify that the T-Engines start running again, and to check that ActiveMQ is still available. In that case, the documents indexed with a `transform_failed` status should be automatically reindexed once the T-Engines start running again and the earlier ActiveMQ messages are consumed, without any further steps being required.

These documents can be identified via the following query:

```http
http://localhost:8080/solr/alfresco/select?indent=on&q=cm:content.transformationStatus:transform_failed&wt=xml
```

You can extract the DB IDs of the nodes for which the content transformation failed from the response:

```xml
<result name="response" numFound="1" start="0">
<doc>
<long name="DBID">877</long>
<str name="id">_DEFAULT_!800000000000036d</str>
</doc>
</result>
```

Once the IDs have been identified, you can perform the following request once for each node, using the `REINDEX` parameter to trigger a reindexing attempt:

```http
http://localhost:8080/solr/admin/cores?action=REINDEX&nodeid=877
```

Alternatively, you can perform a full reindex following the instructions in [Perform a full reindex with Solr](#perform-a-full-reindex-with-solr).

## Solr troubleshooting for SSL configurations

When you have an Alfresco Content Services installation that requires an SSL configuration, you might encounter connection issues.
Expand All @@ -188,9 +219,9 @@ Aug 22, 2011 8:19:21 PM org.apache.tomcat.util.net.jsse.JSSESupport handShake
WARNING: SSL server initiated renegotiation is disabled, closing connection
```

This message indicates that one side of the SSL connections is trying to renegotiate the SSL connection. This form of negotiation was found to be susceptible to man-in-the-middle attacks and it was disabled in the Java JSEE stack until a fix could be applied.
This message indicates that one side of the SSL connections is trying to renegotiate the SSL connection. This form of negotiation was found to be susceptible to man-in-the-middle attacks and it was disabled in the Java JSEE stack until a fix could be applied.

Refer to the following link for more information: [Transport Layer Security (TLS) Renegotiation Issue Readme](https://www.oracle.com/java/technologies/javase/tlsreadme2.html){:target="_blank"}.
Refer to the following link for more information: [Transport Layer Security (TLS) Renegotiation Issue Readme](https://www.oracle.com/java/technologies/javase/tlsreadme2.html){:target="_blank"}.

Refer also to the following links:

Expand Down

0 comments on commit 00a478f

Please sign in to comment.