Heya Pat!
I'm working over at Icelab these days. We have flying sphinx set up with the thousands site.
Recently they noticed that search results were not including some of the articles they expected. After a brief investigation I found that the deltas weren't updating because the database details were wrong:
using config file '/mnt/local/flying-sphinx/70c3c15e58eddf7a5/sphinx.conf'...
indexing index 'media_core'...
ERROR: index 'media_core': sql_connect: could not connect to server: Connection refused
Is the server running on host "ec2-54-225-107-174.compute-1.amazonaws.com" (10.152.152.59) and accepting
TCP/IP connections on port 5872?
(DSN=pgsql://X:[email blocked]:5872/Z).
The DSN is wrong—the host isn't even correct. It looks like a heroku deploy has migrated our database somewhere else or something and flying sphinx didn't notice. Running a fs:{configure,restart,index} fixed the issue.
My question is mainly can flying sphinx detect when the configuration becomes out of date and kick itself into gear?
See you at RoRo tonight,
Sam.
#1 Posted by Pat Allan Support staff on 26 Sep, 2013 04:46 AM
Heya Sam
Good pickup - but unfortunately it's nothing something Flying Sphinx can detect (add-ons only have access to their own environment variables, which is a wise idea, just gets in the way in this situation). Nor can Flying Sphinx automatically invoke the configure task.
If it wasn't a pretty rare event, a solution would be pretty sweet, but probably not worth the time now :)
Catch you in a few hours!
--
Pat
#2 Posted by sj26 on 26 Sep, 2013 05:57 AM
Ah, shame. See you later!
Pat Allan closed this discussion on 13 Jan, 2014 11:20 PM.