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

    Primo Central Stopped Returning Results

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

    Problem Symptoms:
    * Primo Central unexpectedly stopped returning results.
    * No changes had been made to configuration files.
    * Customer's IP does not show up in the Primo Central logs, not in the refused request nor in succeeded queries.

    In order to trace the core issue, use the following Unix command from the FE server:

    curl -v -H "Content-Type: text/xml" -H "Soapaction: ddd" --data-binary '<soapenv:Envelope xmlns:api="" xmlns:xsi="" xmlns:soapenv="" xmlns:soapenc="" soapenv:encodingStyle="><soapenv:Body><api:searchXCompressed><query xsi:type="soapenc:string">Book</query><sort xsi:type="soapenc:string"></sort><strDidumean xsi:type="soapenc:string"></strDidumean><language xsi:type="soapenc:string">eng</language><strFromrom><strTake xsi:type="soapenc:string">10</strTake><asFull xsi:type="xsd:boolean">false</asFull><searchAuthorization xsi:type="soapenc:string">[PRIMO CENTRAL KEY]</searchAuthorization><availabilityAuthorization xsi:type="soapenc:string"><availabilityAuthorization xsi:type="soapenc:string">[PRIMO CENTRAL KEY]</availabilityAuthorization></api:searchXCompressed></soapenv:Body></soapenv:Envelope>'

    The result of the above command provides a hint as to what is the root cause of the issue.

    For example, (response from the command)
    * About to connect() to port 1701 (#0)
    * Trying Connection refused
    * couldn't connect to host
    * Closing connection #0
    curl: (7) couldn't connect to host

    In this case the connection was refused by an internal IP within the network, this was a proxy server.

    Testing using telnet:
    telnet 80
    Connected to
    Escape character is '^]'.

    telnet 1701
    telnet: Unable to connect to remote host: Connection refused
    The telnet shows that while port 80 connects, port 1701 is refused.

    In this case, fixing the port permission on the proxy server resolved the problem and Primo Central started working again.

    Additional Information


    See Also

    Does Primo Central return results for a particular PC key?

    • Article last edited: 9/2/2015