Troubleshooting

This task shows you how to:

See Also
Configure storage to index collaborative data
Storage Administration
Troubleshooting
Clearing Application or Widget Storage

Repush is not launched after document modifications

Enable the cache before indexing. Note that dumping the storage database will not trigger an automatic repush from cache.

I can’t search on my collaborative data

Before you begin: A meta corresponding to the collaborative data must be mapped to a "searchable" field or facet in your data model.
Check that the collaborative widget data has been properly indexed.

To do so, you can use a debug processor as explained in Troubleshoot all issues related to the storage service behavior.

Apply actions fail if the search server and the related storage service are not on the same host

Storage can't be used from a remote search server due to SQLite limitations.

It is yet fully compatible with MySQL and Oracle.

Troubleshoot all issues related to the storage service behavior

  1. In the Administration Console, go to Logs.
  2. Set the Default logging level to Debug and check the storage service's logs.
  3. Make sure that the repushFromCache request is issued without problems.

    Important: If you get an error saying invalid source:", it means that the source is empty, that is to say that there is no source category to display. Go to Search Logics > Facets, expand the Source category and set the Root property to Top/source

Troubleshoot indexing issues

  1. In the Administration Console>, go to Index > Data Processing > pipeline name > Document Processors.
  2. Add a Debug Processor to the bottom of your analysis pipeline.
  3. Make sure that values are indexed.
    1. Go to Logs.
    2. From the Processes select box, select analyzer-<BUILD GROUP NAME>.

The Debug Processor will write explicit logs.