Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    What to Do If Primo Is Not Accessible (is it running) ?

    • Article Type: General
    • Product: Primo
    • Product Version: 2

    Description:
    I tried to access the Primo server (BO) and got the following response:

    Internet Explorer cannot display the webpage
    Most likely causes:
    You are not connected to the Internet.
    The website is encountering problems.
    There might be a typing error in the address.

    What next?

    Resolution:
    Follow the following steps:
    [1] Confirm that the address is written correctly and has not changed
    [2] Is the Front End accessible ? If the answer is no, continue
    [3] Is the server running ? (you can login)
    [4] Is Primo running? Run the command:
    ps -ef | grep java
    If the only response is something like:
    primo 26916 26681 0 11:58 pts/0 00:00:00 grep java
    then, Primo is not running.

    To start Primo, run the following start up jobs in alphabetical order: be_start, fe_start, se_start, start_apache

    or run: $primoe_root/primo_startup_all
    (the startup order is slightly different in that apache is started second, but either way works)

    be_start results in something like this response:
    PID file ../../thirdparty/openserver/server/publish/log/pid.lock exists, but the process 7058 is not running.
    Removing ../../thirdparty/openserver/server/publish/log/pid.lock and continuing...
    cycling publish_server.log
    starting jboss
    monitoring startup complete signal
    .........................................done

    fe_start results in something like this response:
    PID file ../../thirdparty/openserver/server/search/log/pid.lock exists, but the process 7348 is not running.
    Removing ../../thirdparty/openserver/server/search/log/pid.lock and continuing...
    cycling library_server.log
    starting jboss
    monitoring startup complete signal
    ......................................................done

    se_start results in something like this response:
    PID file /exlibris/primo/p1_1/ng/jaguar/home/system/bin/../../profile/log/pid.lock exists, but the process 7741 is not running.
    Removing /exlibris/primo/p1_1/ng/jaguar/home/system/bin/../../profile/log/pid.lock and continuing...
    starting agent
    port #i : 9501
    log file : /exlibris/primo/p1_1/ng/jaguar/home/system/bin/../../profile/log/agent_9501.log
    cycling existing log file...

    start_apache results in something like this response:
    /exlibris/primo/p1_1/primoe/apache/bin/apachectl restart: httpd not running, trying to start
    /exlibris/primo/p1_1/primoe/apache/bin/apachectl restart: httpd started

    Then, verify that the system is running correctly:
    1. Open the search user interface.
    2. Perform a search.
    3. Open the Back Office user interface.
    4. Check the Dashboard (refer to "Primo Administrator Guide" > "Monitoring and Maintaining Primo" > "Dashboard Monitoring" p62).
    5. Check system reports (refer to "Primo System Administration Guide" > "Accessing Reports and Log Files" p57).

    If, say, BE were already running, then the response would be:
    >> be_start
    PID file ../../thirdparty/openserver/server/publish/log/pid.lock exists. JBOSS has already been started up


    • Article last edited: 10/8/2013