Ok. This is fixed now. It seems that searchd was still running in the background even though rake ts:stop said it was not running. Killing all my processes and restarting them has fixed the problem.
On Aug 14, 1:37 am, anrake <[email protected]> wrote: > Hi, I'm having some trouble with TS. It was working fine until I > switched from a test site I manually uploaded to a Capistrano > controlled one using the same directory. > > rake ts:conf runs fine, production.sphinx.conf is created > rake ts:index runs fine. index is created with no errors. > rake ts:start gives me the following > > Failed to start searchd daemon. Check /home/castle/webapps/rails/ > castle/releases/20100813153201/log/searchd.log > > There is no searchd.log to check. I tried creating a blank one but > nothing was written there. I've tried several deploys, but no good. > > searchd returns this: > > FATAL: no readable config file (looked in /home/castle/etc/ > sphinx.conf, ./sphinx.conf) > > any ideas? I'm using the latest Gem 1.3.18, and Rails 2.3.8 -- 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.
