Hello!
I'm not sure of the root cause here. I deployed my latest app to Heroku (Rails 3.1.5, Flying Sphinx 0.8.4) and search was not working. It was attempting to connect to what appear to be the defaults (localhost), and was reporting a connection refused error.
Eventually I discovered that Flying Sphinx normally would add an initializer that did this. For some reason this was not running, and when I copied/pasted it into my own initializer the problem was resolved. Any idea what's up?
Thanks!
Mike
#1 Posted by Pat Allan Support staff on 02 Nov, 2012 02:41 AM
That is odd indeed. I don't suppose flying-sphinx is listed above rails in your Gemfile? That could cause the railtie not being loaded at all.
#2 Posted by Michael Swieton on 02 Nov, 2012 01:09 PM
I wasn't sure so I just double checked. Rails is the first gem listed.
The whole thing is quite surprising. Not really sure what's happening
here. It's not a critical problem since I got it running, but this is
so strange.
#3 Posted by Pat Allan Support staff on 05 Nov, 2012 11:27 AM
Will keep an ear out for whether anyone else hits this problem. If it does, access to the app's source would be certainly helpful to determine the cause.
But as you've said, you've got a fix sorted, so there's no rush on that right now.
#4 Posted by Pat Allan Support staff on 09 Nov, 2012 11:46 AM
Hi Mike
So, I had another customer hit a problem like this, but it turns out the issue for them was having the flying-sphinx gem listed in a non-standard group in their Gemfile. I don't suppose that's the case for you? Or is flying-sphinx listed with most other gems, outside of any groups?
Cheers
Pat