Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

FAQs

Info

No available FAQs at this moment

Troubleshooting

The log files for the Google Cloud Search publisher can be found in either:

  • The aspire.log/felix.log files in AspireRootDirectory/log folder where they will be commingled with other Aspire component log entries 

Specific

The

OR

  • The AspireRootDirectory/log/{name of the publisher component}/PAP/PAP.log
When the

Debug flag is off in the Publisher config

UI, all

UI 


Panel
  1. All ERROR records will be written to the logs.
  2. Statistics information about each successfully written to GCS is included too.

When the

The Debug flag is on in the Publisher config UI

Additional additional details about documents that are publisher published are included in the log files.If there too

Too many documents

that

are indexed

which lead

leading to a throughput rate higher than the quota limit assigned to the GCS API

Exponential , exponential backoff retry logic will be employed to attempt to still ingest records.


Troubleshooting


Where to locate the publisher log files

Solution

The log files for the Google Cloud Search publisher can be found in either:

  • The aspire.log/felix.log files in AspireRootDirectory/log folder where they will be commingled with other Aspire component log entries 

OR

  • The AspireRootDirectory/log/{name of the publisher component}/PAP/PAP.log
If socket

Socket timeout exceptions are observed

Solution

The , the read/connection timeout settings should be increased.