Hi Mathew I'm guessing some rake tasks were run without RAILS_ENV=production - have a look at the currently running processes to see if you've actually got more than one searchd running...
ps aux | grep searchd I would recommend stopping all searchd instances, make sure those pid files are deleted, and then rebuild your indexes and restart the daemon: rake ts:rebuild RAILS_ENV=production Cheers -- Pat On 14/10/2010, at 1:23 PM, Mathew wrote: > In my production environment, somehow I've ended up with > production.searchd.pid in my config/ directory & > searchd.development.pid in my log/ directory. > > I think that this is causing the Model.search to look up an empty or > non-existent development index instead of the existing and accurate > production index since Model.search is returning an empty set in > production. Sphinx/TS is working as desired locally on my dev machine. > > Does anyone have any ideas how this might be happening, and how I > might fix it? > > Thank you so so much! > > Mathew > > -- > 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.
