Unfortunately, Sphinx has not yet reached 100% bug-free (although we are working towards that goal), so you may occasionally experience problems.
It's important to have a detailed report on each issue--because to fix a bug, we have to reproduce the bug and debug it, or infer the cause of the bug based on the information you provide. So here are some guidelines for how to report bugs.
Build-time issues
If the Sphinx build fails, please:
1. Verify that your DBMS's header and library files are properly installed (for example, check that the Mysql-devel package is installed)
2. Report Sphinx version and configuration file (don't forget to delete database connection password), MySQL (or PostgreSQL) profile information, GCC version, operating system version and CPU type (e.g. x86, were, PowerPC, etc.)
Mysql_config
GCC--version
Uhttp://www.aliyun.com/zixun/aggregation/11696.html ">name-a
3. Report configure script or GCC error message (only the error message itself, do not have to attach the entire build log)
Run-time issues
If the Sphinx has been successfully built and can run, but there is a problem during the run, please:
1. Describe the bugs that you are experiencing (that is, the behavior you expect and what you actually do), and the steps you need to reproduce the problem you are experiencing.
2. With Sphinx version and configuration file (don't forget to delete password), MySQL (or PostgreSQL) profile information, GCC version, operating system version and CPU type (e.g. x86, were, PowerPC, etc.)
MySQL--version
GCC--version
Uname-a
3. Build, install, and run all Sphinx programs for the debug version (this will enable many internal checksums, or assertions)
Make Distclean
./configure--with-debug
Make install
Killall-term Searchd
4. Re-indexing to check if any assertions are triggered (if it is, it is likely that the index is corrupted and causing the problem)
5. If the bug is not reproduced in the debug version, go back to the debug version and explain the situation in the report.