Hi Pat, I regret to bring another open issue but I've been working with this one for some time today and no dice. Definitely very impressed with the patience and attention it takes to handle all these threads ...
So I'm using 0.3.0 pusher-client, the flying-sphinx from your Github and thinking-sphinx 3.0.0.
from Gemfile:
gem "thinking-sphinx", "~> 3.0.0"
gem 'pusher-client', :git =>
'git://github.com/pusher/pusher-ruby-client.git'
gem 'flying-sphinx',
:git =>
'git://github.com/flying-sphinx/flying-sphinx.git',
:branch => 'master', :ref => '18e3d2784d'
$ heroku run bundle exec flying-sphinx rebuild ... [Mon Apr 15
22:17:36.944 2013] [27373] using config file
'/mnt/local/flying-sphinx/2ddba01066b1e169c/sphinx.conf'... [Mon
Apr 15 22:17:36.945 2013] [27373] WARNING: compat_sphinxql_magics=1
is deprecated; please update your application and config Sphinx
2.0.4-release (r3135)
Copyright (c) 2001-2012, Andrew Aksyonoff
Copyright (c) 2008-2012, Sphinx Technologies Inc (http://sphinxsearch.com)
listening on all interfaces, port=9323
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
bind() failed on 0.0.0.0, retrying...
FATAL: bind() failed on 0.0.0.0: Address already in use
Sphinx 2.0.4-release (r3135)
Copyright (c) 2001-2012, Andrew Aksyonoff
Copyright (c) 2008-2012, Sphinx Technologies Inc (http://sphinxsearch.com)
Sphinx 2.0.4-release (r3135)
Copyright (c) 2001-2012, Andrew Aksyonoff
Copyright (c) 2008-2012, Sphinx Technologies Inc (http://sphinxsearch.com)
I, [2013-04-15T22:18:16.749116 #2] INFO -- : Action Finished:
rebuild
$
This is on a fresh app that's never had sphinx running. Any clues?
Best regards,
jesse
#1 Posted by Pat Allan Support staff on 16 Apr, 2013 12:52 AM
Hi Jesse
There was a former customer's searchd daemon running and taking your assigned port. I've removed that process, so you should be able to start the daemon up now without any issues - and I'll look into why it was hanging around when it should have disappeared a while ago.
Sorry about the hassle - let me know if there's any further issues.
Kind regards,
Pat
#2 Posted by jesseoliversanf... on 16 Apr, 2013 01:00 AM
Looks great, thanks!
Pat Allan closed this discussion on 13 Jan, 2014 11:23 PM.