Great to hear it helped :)

I think Sphinx expects normal protocol for non-mysql41 ports, and mysql-only 
for mysql41. So, if you want to test via that, just add a second `listen` 
setting on a different port with the mysql41 flag.

Cheers

-- 
Pat

On 08/10/2011, at 10:21 AM, gonzoprosperity wrote:

> Boom - that was it. Removing "mysql41" from the "listen" line in
> sphinx.conf allowed me to issue a query from remote.
> 
> This seems like a fairly innocuous setting - I wonder why it caused
> this grief (?)
> 
> Thanks. I can rock without "mysql41" it was mainly for testing.
> 
> On Oct 6, 9:21 pm, Pat Allan <[email protected]> wrote:
>> What happens if you don't add the mysql41 setting?
>> 
>> --
>> Pat
>> 
>> On 05/10/2011, at 11:45 PM, gonzoprosperity wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> Good morning.
>> 
>>> So my config/sphinx.yml looks like:
>> 
>>> production:
>>>  address: sphinx.foo.com
>>>  port: 3312
>>>  mem_limit: 64M
>>>  enable_star: true
>>>  searchd_file_path: /var/searchd/data
>>>  searchd_log_file: /var/log/searchd/logs/searchd.log
>>>  query_log_file: /var/log/searchd/logs/searchd.query.log
>>>  pid_file: /var/run/searchd.pid
>>>  morphology: stem_en
>>>  config_file: /etc/sphinxsearch/sphinx.conf
>> 
>>> And I've added this line to config/environments/production.rb - not
>>> sure if its needed any more but I found on a GitHub Issue page:
>> 
>>> ThinkingSphinx.remote_sphinx = true
>> 
>>> In the console I get:
>> 
>>> irb(main):003:0> ThinkingSphinx::Search.new.client.server
>>> => "sphinx.foo.com"
>>> irb(main):004:0> ThinkingSphinx::Search.new.client.port
>>> => 3312
>>> irb(main):005:0> Client.search "foo"
>>>  Sphinx Query (232.7ms)  foo
>>> Riddle::ResponseError: No response from searchd (status: 2610,
>>> version: 11824)
>>>    from /u/apps/foo/shared/bundle/ruby/1.9.1/gems/riddle-1.4.0/lib/
>>> riddle/client.rb:651:in `request'
>> 
>>>> Are you making any changes to sphinx.yml to get the mysql41 in the 
>>>> configuration file?
>> 
>>> I modified the remote /etc/sphinxsearch/sphinx.conf to add mysql41
>>> support
>> 
>>> searchd
>>> {
>>>  listen = 3312:mysql41
>>> }
>> 
>>> And I've ensured connectivity as I can telnet to the machine:
>> 
>>> $ telnet sphinx.foo.com 3312
>>> Connected to sphinx.foo.com.
>>> Escape character is '^]'.
>>> @
>>> 2.0.1-beta (r279?)
>> 
>>> Thanks for any help you can provide.
>> 
>>> On Oct 4, 10:03 pm, Pat Allan <[email protected]> wrote:
>>>> Just committed that fix to Riddle, thanks.
>> 
>>>> Not really sure why this problem is occurring otherwise - although it's 
>>>> worth noting that TS doesn't yet use SphinxQL, so maybe that's not the 
>>>> best way to test it. Are you making any changes to sphinx.yml to get the 
>>>> mysql41 in the configuration file?
>> 
>>>> Also, what's the output of the following - or rather, do the values match 
>>>> the expected settings?
>> 
>>>>   ThinkingSphinx::Search.new.client.port
>>>>   ThinkingSphinx::Search.new.client.server
>> 
>>>> Cheers
>> 
>>>> --
>>>> Pat
>> 
>>>> On 04/10/2011, at 8:43 AM, gonzoprosperity wrote:
>> 
>>>>> I am in the process of moving from a local searchd process (on same
>>>>> box as the Rails app) to its own machine.
>> 
>>>>> I have Sphinx 2.0.1-beta running on the new box and can query it via
>>>>> SphinxQL from the Rails box.
>> 
>>>>> However, when I update sphinx.yml "address" and "port" to point to the
>>>>> sphinx box and then attempt to issue queries I get:
>> 
>>>>> NameError: uninitialized constant Riddle::Client::TcpSocket
>> 
>>>>> I looked in the Riddle gem and in $RIDDLE_GEM/lib/client.rb -
>>>>> request() line 643
>> 
>>>>> I see this line:
>> 
>>>>>          break if part.length == 0 && socket.is_a?(TcpSocket)
>> 
>>>>> I think this is supposed to be "TCPSocket" which is part of the Ruby
>>>>> standard lib (?)
>> 
>>>>> When I add
>> 
>>>>> require 'socket'
>> 
>>>>> and change that line to
>> 
>>>>>          break if part.length == 0 && socket.is_a?(TCPSocket)
>> 
>>>>> And then try a search I get
>> 
>>>>> Riddle::ResponseError: No response from searchd (status: 2610,
>>>>> version: 11824)
>> 
>>>>> Like I said, I *am* able to connect to my Sphinx box via telnet or the
>>>>> mysql command line and issue straight SphinxQL queries - so the box is
>>>>> available on the network and accessible.
>> 
>>>>> On top of this: whats the deal with the TcpSocket => TCPSocket stuff?
>> 
>>>>> --
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "Thinking Sphinx" group.
>>>>> To post to this group, send email to [email protected].
>>>>> To unsubscribe from this group, send email to 
>>>>> [email protected].
>>>>> For more options, visit this group 
>>>>> athttp://groups.google.com/group/thinking-sphinx?hl=en.
>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Thinking Sphinx" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to 
>>> [email protected].
>>> For more options, visit this group 
>>> athttp://groups.google.com/group/thinking-sphinx?hl=en.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Thinking Sphinx" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/thinking-sphinx?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Thinking Sphinx" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/thinking-sphinx?hl=en.

Reply via email to