Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Primo

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Primo
    3. Knowledge Articles
    4. Indexing 'stopped'

    Indexing 'stopped'

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Primo
    • Product Version: 2

    Description:
    The Indexing process will not start on our Prod2 server (will report 'stopped' within a minute of execution).

    Resolution:
    This is the order of indexing in topology=nSlices:

    Indexing is first done on repository and then copied to NFS. For doing these actions FE machine needs
    1) repository path to be configured
    2) NFS should be mounted.

    The NFS is not mounted and the FE machine is looking for the indexstatus file that can be found on the NFS machine.

    Since the NFS is not mounted on the FE machine, the indexing process stops at the start of the process.

    This explains the error displayed:
    2009-09-25 15:50:26,035 ERROR [t-Thread-135] [c-IndexManager] - Failed to init indexer.

    After mounting the NFS on FE indexing should succeed.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Indexer does not restart after slice failover
      • Indexing_and_Hotswapping failed
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Community Content Type
      How To
      Content Type
      Knowledge Article
      Language
      English
      Product
      Primo
    2. Tags
      1. 2
      2. contype:kba
      3. Prod:Primo
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved