Skip to main content
ExLibris

  • Subscribe by RSS
    • Back
    Primo
    Ex Libris Knowledge Center

    Indexing 'stopped'

    1. Last updated
    2. Save as PDF
    • 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