Sorry, this is another thread that's lain dormant - Dean, did you get anywhere
with this? Still need help?
--
Pat
On 03/05/2011, at 8:55 PM, Dean wrote:
> Pat:
>
> Changing the bin/path still produced the same "failed to start
> searchd" messages that I had originally.
>
> Since then, I've added "production" to the end of my searchd_file_path
> in sphinx.yml:
>
> searchd_file_path: "/home/dean/rails_projects/shared/db/sphinx/
> production"
>
> And I added "production" in two places to my symlink tasks in
> deploy.rb:
>
> run "ln -nfs #{shared_path}/db/sphinx/production #{release_path}/db/
> sphinx/production"
>
> I then created this "production" directory by hand.
>
> Now cap deploy proceeds without errors and searchd is running on our
> server. In particular, I notice that capistrano runs the various
> commands with -c followed by my correct configuration file path. The
> clue to me figuring this out was that when I used the -c option and
> added the desired configuration file location, I got a different error
> than I had before.
>
> Of course, I can't get the deploy to bring passenger / our website up
> in production mode, but that's another story.
>
> Thanks for your help!
>
> --Dean
>
> On May 2, 8:24 pm, Pat Allan <[email protected]> wrote:
>> Hi Dean
>>
>> Can you give me an update on the output from cap with that bin_path change?
>>
>> It isn't a permissions issue - at least, the output from searchd you've
>> provided shouldn't be taken to mean that. TS calls searchd with arguments
>> that point it to a different config file, which in turn references a
>> different pid file.
>>
>> --
>> Pat
>>
>> On 03/05/2011, at 2:51 AM, Dean wrote:
>>
>>
>>
>>
>>
>>
>>
>>> Hi Pat:
>>
>>> OK, made that change... still no luck.
>>
>>> Reading through some of your previous responses to this kind of
>>> question, I also tried a few other things on the production server:
>>
>>> ~/app_name/current$ which indexer
>>> yields
>>> /usr/bin/indexer
>>
>>> ~/app_name/current$ which searchd
>>> yields
>>> /usr/bin/searchd
>>
>>> ~/app_name/current$ searchd
>>> yields
>>> Sphinx 0.9.9-release (r2117)
>>> Copyright (c) 2001-2009, Andrew Aksyonoff
>>
>>> using config file '/etc/sphinxsearch/sphinx.conf' ...
>>> FATAL: failed to create pid file '/var/run/searchd.pid': Permission
>>> denied
>>
>>> Do I need to change the permissions on the /var/run directory somehow?
>>
>>> Thanks,
>>
>>> Dean
>>> On May 1, 2:14 am, Pat Allan <[email protected]> wrote:
>>>> Hi Dean
>>
>>>> You don't need the actual binary name in the bin_path setting - just the
>>>> path to the binary. So, try changing that to /usr/bin and see if that
>>>> helps.
>>
>>>> Cheers
>>
>>>> --
>>>> Pat
>>
>>>> On 29/04/2011, at 6:13 AM, Dean wrote:> So I'm using
>>>> Sphinx/Thinking_Sphinx in my rails app. It works great on
>>>>> the original (Windows) development server, and it works in development
>>>>> on the new Ubuntu Linux server as well. But now that I'm trying to
>>>>> deploy to production on the Ubuntu box using Capistrano, no luck.
>>
>>>>> Here's the main error that shows up in response to "cap deploy" issued
>>>>> on the development machine:
>>
>>>>> http://pastie.org/1844319
>>
>>>>> Here's my /config/sphinx.yml file:
>>
>>>>> http://pastie.org/1844327
>>
>>>>> Here's my production.sphinx.conf file, as generated by capistrano on
>>>>> the Ubuntu server:
>>
>>>>> http://pastie.org/1844345
>>
>>>>> And here's my deploy.rb file:
>>
>>>>> http://pastie.org/1844735
>>
>>>>> The version of the thinking-sphinx gem I have installed on our Ubuntu
>>>>> server is 1.3.20.
>>
>>>>> Any suggestions/advice would be much appreciated.
>>
>>>>> Thanks,
>>
>>>>> Dean Richardson
>>>>> Molex Fiber Optics
>>
>>>>> --
>>>>> 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
>>>>> athttp://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
>>> athttp://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.
>
--
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.
