Error and problem resolution encountered by CoreSeek under Linux

1. Test the MMSEG word segmentation

perform

/ usr/local/coreseek/bin/etc/indexer – c CSFT. Conf -all

Error:

/usr/local/coreseek/bin/indexer: error while loading shared libraries: libmysqlclient.so.18: cannot open shared object file: No such file or directory

Sphinx Indexer dependency library IBMYSQLClient.so.18 could not be found.

Solutions:

vi /etc/ld.so.conf

Add/usr/local/mysql/lib

Then run ldconfig

Problem solving

2. Indexing

/ usr/local/coreseek/bin/indexer – c/usr/local/coreseek/etc/CSFT. Conf – all – rotate

Error:

FATAL: failed to open /usr/local/coreseek/var/data/article/.tmp.spl: No such file or directory, will not index. Try — rotate option.

ERROR: Unable to find mysql.sock

Solution: Add the following code to the source source of the configuration file csft.conf (a self-created file)

sql_sock   = /tmp/mysql.sock

The index was not created successfully because of a warning that appeared while executing the index

WARNING: failed to open pid_file ‘/usr/local/coreseek/var/log/searchd_ttd_search.pid’.

WARNING: indices NOT rotated.

Cause: The searchd_ttd_search.pid file could not be found

Solution: in ‘/ usr/local/coreseek create searchd_ttd_search under/var/log. The pid file

Perform/usr/local/coreseek/bin/indexer – c/usr/local/coreseek/etc/CSFT. Conf – all – rotate

Another warning came up:

WARNING: failed to scanf pid from pid_file ‘/usr/local/coreseek/var/log/searchd_ttd_search.pid’.

WARNING: indices NOT rotated.

Cause: The searchd_ttd_search.pid file is created, but the process id is not written in it

Solution (root cause) : The searchd service was not started before indexing, so execute the following command

/ usr/local/coreseek/bin/searchd – config/usr/local/coreseek/etc/CSFT. Conf

4. Indexing

/ usr/local/coreseek/bin/indexer – c/usr/local/coreseek/etc/CSFT. Conf – all – rotate

Error:

FATAL: failed to open /usr/local/coreseek/var/data/article.tmp.spl: (Permission denied, will not index. Try — rotate option)

Reason: Permission issues

Solution: Use root to execute the command