0000373: agent 192.168.1.4:3312: connect() timed out warning

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000373

Sphinx

general

public

2009-07-01 22:10

2011-12-09 20:25

Reporter

TECK

Assigned To

shodan

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

fixed

Product Version

0.9.9-rc2

Target Version

Fixed in Version

Summary

0000373: agent 192.168.1.4:3312: connect() timed out warning

Description

I'm using the 0.9.10-dev r1873. File searchd.cpp was patched with the modification related to the host:port:proto bug we already talked about. Using SphinxQL, the connection times out, if applied to a distributed index. However, it runs well if applied to a regular index (see screenshot attached).

This the logged info, when I ran the queries:
[Wed Jul 1 16:02:06.912 2009] 0.050 sec [scan/0/ext 846242 (0,20)] [alphathread]
[Wed Jul 1 16:02:12.029 2009] 1.001 sec [scan/0/ext 0 (0,20)] [thread] <-- connect timeout
[Wed Jul 1 16:02:22.653 2009] 0.071 sec [scan/0/ext 1250613 (0,20)] [alphapost]

Additional Information

sphinx.conf related info:
# thread index data
index thread
{
    type = distributed
    agent = 192.168.1.4:3312:alphathread,scanthread
    local = omegathread
    local = scanthread
}

# post index data
index post
{
    type = distributed
    local = alphapost
    local = omegapost
    local = scanpost
}

# searchd settings
searchd
{
    listen = 192.168.1.4:3307:mysql41
    listen = 192.168.1.4:3312:sphinx
    log = /var/log/searchd.log
    query_log = /var/log/query.log
    read_timeout = 5
    client_timeout = 60
    max_children = 30
    max_matches = 1000
    seamless_rotate = 1
    preopen_indexes = 1
    unlink_old = 1
    mva_updates_pool = 1M
    max_packet_size = 8M
    max_filters = 256
    max_filter_values = 4096
    read_buffer = 1M
    read_unhinted = 64K
}

Tags

No tags attached.

Attached Files

sphinxql.png [^] (60,438 bytes) 2009-07-01 22:10

Relationships

Notes
(0000477) TECK (reporter) 2009-07-01 22:21 edited on: 2009-07-01 22:30	I forgot to mention that if I run this query: mysql> SELECT * FROM post; I get proper results. The messages log has this entry: Jul 1 16:23:44 hermes kernel: searchd[7143]: segfault at 0000000000000000 rip 0000003b31878d80 rsp 00007fff0ceaeb28 error 4

(0000478) TECK (reporter) 2009-07-01 23:07	In order to help debugging I also performed the following steps. 1) Created a new config file, with master running on port 3313. sphinx.conf.agent file: # thread index data index thread { type = distributed agent = 192.168.1.4:3312:alphathread,scanthread local = omegathread local = scanthread } # searchd settings searchd { listen = 127.0.0.1:3307:mysql41 listen = 127.0.0.1:3313:sphinx ... more options ... } 2) Changed sphinx.conf to match the new agent host/port values. sphinx.conf file: # thread index data index thread { type = distributed agent = 127.0.0.1:3313:alphathread,scanthread local = omegathread local = scanthread } # searchd settings searchd { listen = 192.168.1.4:3307:mysql41 listen = 192.168.1.4:3312:sphinx ... more options ... } 3) Run both master and agent in --console mode. # killall -TERM searchd # searchd --console # searchd --config /etc/sphinx/sphinx.conf.agent --console 4) Run the SphinxQL query: $ mysql -h 192.168.1.4 -P 3307 Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 0.9.10-dev (r1873) Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> SELECT * FROM thread; ERROR 2013 (HY000): Lost connection to MySQL server during query mysql> The messages log shows: Jul 1 17:03:35 hermes kernel: searchd[8676]: segfault at 0000000000000000 rip 0000003b31878d80 rsp 00007fff3f7f8918 error 4 5) Ran again the SphinxQL query: $ mysql -h 127.0.0.1 -P 3307 Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 0.9.10-dev (r1873) Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> SELECT * FROM thread; Empty set, 1 warning (0.02 sec) mysql>

(0000479) shodan (administrator) 2009-07-02 03:23	Should be fixed in r1881. (For reference, it was strlen(NULL) on q.m_sGroupBy in remote request builder.)

Issue History
Date Modified	Username	Field	Change
2009-07-01 22:10	TECK	New Issue
2009-07-01 22:10	TECK	File Added: sphinxql.png
2009-07-01 22:21	TECK	Note Added: 0000477
2009-07-01 22:30	TECK	Note Edited: 0000477
2009-07-01 23:07	TECK	Note Added: 0000478
2009-07-02 00:35	TECK	Issue Monitored: TECK
2009-07-02 03:23	shodan	Note Added: 0000479
2009-07-02 03:23	shodan	Status	new => resolved
2009-07-02 03:23	shodan	Resolution	open => fixed
2009-07-02 03:23	shodan	Assigned To	=> shodan
2011-12-09 20:25	Tomat	Status	resolved => closed