Search Indexing Error

Lots of these errors too but not sure why? 

Search Indexing Error

Error while mapping post (3505)
Parents
  •  same thing we see - and the exception message that displays is almost non-legible 

     highlighting this here - is this expected? 

  • This seems to be different than the original item in this thread. Can you share the export of this exception and a diagnostic export too?

  • Hi  , it was a separate issue. Attached is the exception and our resolution

    Root Cause

    The Solr/search container was running and healthy, and both Solr cores responded, but the Solr indexes were empty.

    The actual failure was file ownership on the persisted Solr bind mount:

    /opt/verint-community/data/solr -> /var/solr

    Nested Solr core/index files were owned by UID/GID 1000:1000, while the Solr process in the search container runs as UID/GID 8983:8983. As a result, Solr could start and pass health checks but could not write index files.

    The logs showed errors like:

    java.nio.file.AccessDeniedException: /var/solr/data/telligent-content/data/index/_0.fdm
    java.nio.file.AccessDeniedException: /var/solr/data/telligent-conversations/data/index/_0.fdm

    Fix Applied

    sudo chown -R 8983:8983 /opt/verint-community/data/solr
    cd /opt/verint-community
    sudo docker compose restart search job

    Our installer was then updated to repair Solr ownership idempotently so future installs, reruns, or copied demo instances do not recreate the same issue.

    Testing After the Change

    • Solr document counts became nonzero:

      • telligent-content: 25 docs

      • telligent-conversations: 3 docs

    • Fresh job logs showed successful indexing for Article Collections, Blogs, Calendars, Forums, Groups, Users, Wikis, and Wiki Pages.

    • The previous Solr write/permission failure was no longer blocking indexing.

    • A public /search?q=admin request reached the site and redirected to login when unauthenticated, which is expected for this demo site.



    exceptions.xml?=027beda0987b30484488d6e49d960d1e

Reply
  • Hi  , it was a separate issue. Attached is the exception and our resolution

    Root Cause

    The Solr/search container was running and healthy, and both Solr cores responded, but the Solr indexes were empty.

    The actual failure was file ownership on the persisted Solr bind mount:

    /opt/verint-community/data/solr -> /var/solr

    Nested Solr core/index files were owned by UID/GID 1000:1000, while the Solr process in the search container runs as UID/GID 8983:8983. As a result, Solr could start and pass health checks but could not write index files.

    The logs showed errors like:

    java.nio.file.AccessDeniedException: /var/solr/data/telligent-content/data/index/_0.fdm
    java.nio.file.AccessDeniedException: /var/solr/data/telligent-conversations/data/index/_0.fdm

    Fix Applied

    sudo chown -R 8983:8983 /opt/verint-community/data/solr
    cd /opt/verint-community
    sudo docker compose restart search job

    Our installer was then updated to repair Solr ownership idempotently so future installs, reruns, or copied demo instances do not recreate the same issue.

    Testing After the Change

    • Solr document counts became nonzero:

      • telligent-content: 25 docs

      • telligent-conversations: 3 docs

    • Fresh job logs showed successful indexing for Article Collections, Blogs, Calendars, Forums, Groups, Users, Wikis, and Wiki Pages.

    • The previous Solr write/permission failure was no longer blocking indexing.

    • A public /search?q=admin request reached the site and redirected to login when unauthenticated, which is expected for this demo site.



    exceptions.xml?=027beda0987b30484488d6e49d960d1e

Children