• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
The direct and browse indexes seem to be fine, but after a shutdown for hardware maintenance this morning, the keyword indexes are not working as before. For example, a Keywords Anywhere search for "horse" yields no results, but takes the user to a list starting with "hoxie." The problem is evident in both the Web OPAC and the GUI Search.

Note: we have the Oracle database on a separate server (specified via the ORA_HOST value in aleph_start).

Resolution:
util a/17/14 showed that the z97 Oracle indexes were OK.

When aleph and Oracle were stopped/restarted, keyword searching was working very briefly, but the problem quickly reappeared.

We modified aleph_startup to do just up through the pc_server and then stop. After confirming that the keyword searching was working in the GUI, the www_server and each of the other pieces was started manually.

I have created an "aleph_startup.withsleep" , in which I have:

1. added a "sleep 180" line between the pc_server start and the www_server start

2. added a "sleep 180" after the www_server start

"180" is 180 seconds.

It's possible that there need to be more or longer sleep's -- you can experiment with that -- but since starting these one at a time works, I can only conclude that there is something about the start of the pc_server / www_server just seconds apart which is causing this problem.

• Article last edited: 10/8/2013