WordPress.org

Ready to get started?Download WordPress

Forums

WordPress Sphinx Search Plugin
WARNING: no process found by PID (4 posts)

  1. poer
    Member
    Posted 3 years ago #

    First, it was failed to start the daemon, but it was fixed after I changed this following line in the config file:

    sql_query_pre = REPLACE INTO wp_sph_counter SELECT 1, MAX(id) FROM my_prefix_posts
    sql_query_pre = REPLACE INTO wp_sph_counter SELECT 2, MAX(comment_id) FROM my_prefix_comments

    into my_prefix_sph_counter to match my table prefix setting.

    But then, when I run the manual indexer, it give me this error:

    WARNING: no process found by PID 18078.
    WARNING: indices NOT rotated.

    searchd.log:

    [Thu Dec 2 15:21:35.454 2010] [18078] creating server socket on 0.0.0.0:3312
    [Thu Dec 2 15:21:35.454 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:21:38.453 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:21:41.453 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:21:44.453 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:21:47.453 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:21:50.453 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:21:53.453 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:21:56.453 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:21:59.453 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:22:02.453 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:22:05.453 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:22:09.690 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...
    [Thu Dec 2 15:22:12.690 2010] [18078] FATAL: failed to bind on 0.0.0.0:3312

    what should i do to fix it?

    thanks.

  2. Ivinco
    Member
    Plugin Author

    Posted 3 years ago #

    Hi

    [Thu Dec 2 15:21:35.454 2010] [18078] failed to bind on 0.0.0.0:3312, retrying...

    It looks like you have one running instance of sphinx, but perhaps it has pid != 18078 as saved in the pid file.
    You can try to do:

    ps aux|grep searchd

    It will show whether you have any searchd instance running.
    Then you can try to kill all searchd with

    killall searchd

    and then try to start the daemon again and reindex.

  3. poer
    Member
    Posted 3 years ago #

    #1. i found searchd, but it is belong to another user/site in my vps, is that why this happened? because i already running searchd in another account?

    #2. can i use single searchd for every user in my vps?

    #3. in my other website where the sphinx successfully installed, i also found this error in my error log:

    [05-Dec-2010 05:50:34] WordPress database error Unknown column 'keywords_full' in 'field list' for query INSERT INTO
    					wp_sph_stats
    						(keywords, keywords_full, date_added)
    					VALUES
    						('keyword', 'keyword', NOW()) made by require, wp, WP->main, WP->query_posts, WP_Query->query, WP_Query->get_posts, apply_filters_ref_array, call_user_func_array, SphinxSearch->posts_request, SphinxSearch_FrontEnd->query, SphinxSearch_FrontEnd->insert_sphinx_stats, W3_Db->query

    after i insert a new column called "keyword_full" in wp_sph_stats table, the error is gone and start recording any searches.

    thanks.

  4. Ivinco
    Member
    Plugin Author

    Posted 3 years ago #

    #1. i found searchd, but it is belong to another user/site in my vps, is that why this happened? because i already running searchd in another account?

    Yes, most probably.

    #2. can i use single searchd for every user in my vps?

    Yes, you can either have multiple searchd instances running (in this case just ensure that they have different 'listen' setting values) or you can have only one instance which would serve all users, just merge the configs (sections 'source' and 'index') in this case.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic