• notice
  • Congratulations on the launch of the Sought Tech site

Sphinx common errors and solutions

First error: WARNING: key'sql_query' is not multi-value; value in E:/Lnmp/Bin/Sphinx/sphinx.

using config file'E:/Lnmp/ Bin/Sphinx/sphinx.conf'...WARNING: key'sql_query_info' was permanently removed from Sphinx configuration.Refer to documentation for details.indexing index'test1'...

< /p>

Error prompt: The configuration item sql_query_info has been permanently removed from the configuration file.This is some modification of Sphinx 2.2.10-id64-release (2c212e0).In addition, the removed configuration item is the charset_type setting.

The second error is reported: FATAL: failed to lock E:/Lnmp/Cache/Sphinx/test.spl: No error, will not index.T

using config file'E:/Lnmp/Bin/Sphinx/sphinx.conf'...indexing index'test1'...FATAL: failed to lock E:/Lnmp/Cache/Sphinx/test.spl: No error, will not index.Try --rotate option. pre> Error message: the file test.spl cannot be locked.This is because the index spl file needs to be locked when building the index, and if the search service is being provided, this file cannot Locked.Therefore, if this error is reported, the correct solution is to add a parameter after the indexing command: --rotate can index without stopping searchd.--rotate   send SIGHUP to searchd when indexing is over to rotate updated indexes automatically.

Third error report: WARNING: attribute'id' not found-IGNORING< br>

< span style="white-space:normal;">

using config file'E:/Lnmp/Bin/ Sphinx/sphinx.conf'...indexing index'test1'...WARNING: attribute'id' not found-IGNORING total 0 docs, 0 bytes total 0.051 sec, 0 bytes/sec, 0.00 docs/sec total 0 reads, 0.000 sec, 0.0 kb/call avg, 0.0 msec/call avg total 0 writes, 0.000 sec, 0.0 kb/call avg, 0.0 msec/call avg
Error message: The attribute id was not found because of me The SQL is sql_query=select id,title from webinfo, id is the primary key of the table.And in the index configuration, there is sql_attr_uint = id , and Sphinx cannot use the primary key as the attribute field.Solution: You can remove the sql_attr_uint = id line of configuration , Or change the SQL to sql_query = SELECT id,id as ids,..from table, and then use it in the configuration: sql_attr_uint = ids

The fourth error< /strong>: ERROR: index'test1': No fields in schema-will not index.

using config file'E:/Lnmp/Bin/Sphinx/sphinx.conf'...indexing index'test1'...ERROR: index'test1': No fields in schema-will not index.total 0 docs, 0 bytes total 0.019 sec, 0 bytes/sec, 0.00 docs/sec total 0 reads, 0.000 sec, 0.0 kb/call avg, 0.0 msec/call avg total 0 writes, 0.000 sec, 0.0 kb/call avg, 0.0 msec/call avg
Error prompt: There is no field in the pattern, and it will not be indexed.Simply understand, because my SQL is: sql_query=select id,id as ids,title, from webinfo, and id and title are indexed as attributes.Sphinx search is to pass index items and then query other non-index items , That is, both id and title are indexed, through id, What's in the results of the title search? Even if there are no other fields to search out, the index is meaningless.So you need to change sql and add query fields, such as: sql_query=select id,id as ids,title,url,keywords,description from webinfo.

The errors encountered during the use of Sphinx are definitely not limited to these few, here are just a few of the errors I encountered and resolved through solutions The error was reported.

Tags

Technical otaku

Sought technology together

Related Topic

1 Comments

author

order generic atorvastatin 40mg & lt;a href="https://lipiws.top/"& gt;cost lipitor 20mg& lt;/a& gt; atorvastatin 10mg for sale

Iziwsr

2024-03-10

Leave a Reply

+