From: Kir Kolyshkin (no email)
Date: Mon Apr 22 2002 - 09:03:17 EDT
> I thought it would be the best way to separate everything into different
> directories (program and data) and databases.
> I used debug level "debug" now in searchd.conf to see what happens.
> The log files state:
> Starting search daemon from ASPSeek v.1.2.5
> Loading unicode charset [iso-8859-1] from table tables/iso8859-1.txt
> Loading stop words from /usr/local/aspseek/etc/stopwords/german
> Loaded 177989 values from lastmod file v.44
> Loaded 177993 values from ranks file v.76
> Started accepting queries on port 12345
> ---> Waits on 12345
> Starting search daemon from ASPSeek v.1.2.8
> Loading stop words from /usr/local/aspseek128/etc/stopwords/english
> Loaded 40 values from lastmod file v.2
> Loaded 30 values from ranks file v.2
> Started accepting queries on port 12348
> ---> Waits on 12348
> I copied the s.cgi from 128 to cgi-bin/128/s-128.cgi and
> started it, searching for "elsner".
> There is NO s-128.htm in the 125 branch, so s-128.cgi can only
> be resolved in the 128 branch (/usr/local/aspseek128/etc/s-128.htm).
> still return results from the 125 database (the 128 database
> contains only 16 documents from the site search.rz.uni-osnabrueck.de) ?
> Looking into the stat table from the 128 database, there is no search entry:
> mysql> use aspseek128;
> mysql> select query from stat;
> Empty set (0.02 sec)
> This means:
> Thought searchd (from 128) is listening on port 12348 and s-128.cgi (from 128)
> should use the config entries from searchd.conf (from 128), the
> wrong database (125) is selected.
> My conclusion:
> s-128.cgi connects to the wrong search daemon (125), it seems as if the
> port number from searchd.conf is not evaluated.
You can easily see this by not running searchd on port 12345, only on
12348. If it is so, debug s.cgi to see what it reads from config and
what port it connects to.
PS What I wrote about unability of s.cgi to load appropriate s.htm
is my morning glitch. Actually 1.2.8 does not understand tmpl=