Hello again, Here's some more info: I did a "rake RAILS_ENV=staging ts:stop" followed by a "rake RAILS_ENV=production ts:start" and the search daemon started up fine.
But, as you may have guessed (and maybe I am stupid for not knowing), when I did a "rake RAILS_ENV=staging ts:start" I experienced the same problem, i.e. a 20-second wait followed by a "failed to start searchd daemon" error message. So, is there a trick to getting th-sp to run for both staging and production on the same machine or is that just impossible to do? (Man, I sure hope it's not the latter...) Thanks, Larry On May 31, 4:33 pm, Larry <[email protected]> wrote: > Hi, > > I've done some searches but can't find the answer to this problem... > > My staging and production environments are on the same server. I have > th-sp running fine on staging. In production I can generate the > configuration file and index my models, however, whenever I try to > start th-sp it just sits there for about 20 seconds and then comes > back with a "failed to start searchd daemon" error message. > > The message says to check the searchd.log file, but there isn't one. > The index and config files are being generated, and there is a PID > file in the /tmp directory - unfortunately it is 0 bytes. > > Since there is no log file I have no clue as where to start. Is it > possible to have the search daemon servicing both staging and > production environments on the same machine? > > I'm hoping this is a typical problem and that someone can simply say, > "Oh, you just need to do blah blah blah and you'll be all set". > > Thanks, > Larry -- 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.
