Hi Sumeet

Good to know you have it figured out. I would expect Sphinx to delete the PID 
file automatically when it stops - this is how it happens on Linux machines, 
and I think behaves the same way on Windows in other situations... but I'm not 
sure.

Maybe someone else using Windows and Sphinx can confirm?

-- 
Pat

On 30/03/2010, at 6:19 AM, Sumeet Panchal wrote:

> Hi,
> 
> I figured out what the problem is why it does not stop and start
> properly.
> 
> when you do rake ts:stop
> 
> It do not wipe the value (process id value) from the
> searchd.development.pid file (or this file search
> search.<environment>.pid)
> so each time it go to the gem and thinks that searchd is still
> running.
> 
> <solution> manually delete the value from pid file and try to start it
> again. it will work. I am trying to write a line in gem to do so
> I don't know whether it works on LINUX or not.
> 
> 
> If you guys have any other solution let me know.
> 
> Thanks
> 
> On Mar 29, 11:30 am, Sumeet Panchal <[email protected]> wrote:
>> Hi,
>> 
>> When I reboote my system
>> 
>> rakets:start (it works)rakets:stop(it says it works and stopped searchd )
>> but when I try torakets:start (it says searchd already is running)rakets:stop
>> 
>> it throws error
>> 
>> ** Execute thinking_sphinx:stoprakeaborted!
>> Operationnotpermitted
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/riddle-1.0.10/lib/riddle/
>> controller.rb:51:in `kill'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/riddle-1.0.10/lib/riddle/
>> controller.rb:51:in `stop'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/thinking-sphinx-1.3.16/lib/
>> thinking_sphinx/tasks.rb:49
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 636:in `call'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 636:in `execute'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 631:in `each'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 631:in `execute'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 597:in `invoke_with_call_chain'
>> C:/InstantRails/ruby/lib/ruby/1.8/monitor.rb:242:in `synchronize'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 590:in `invoke_with_call_chain'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 607:in `invoke_prerequisites'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 604:in `each'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 604:in `invoke_prerequisites'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 596:in `invoke_with_call_chain'
>> C:/InstantRails/ruby/lib/ruby/1.8/monitor.rb:242:in `synchronize'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 590:in `invoke_with_call_chain'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 583:in `invoke'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 2051:in `invoke_task'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 2029:in `top_level'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 2029:in `each'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 2029:in `top_level'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 2068:in `standard_exception_handling'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 2023:in `top_level'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 2001:in `run'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 2068:in `standard_exception_handling'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:
>> 1998:in `run'
>> C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
>> C:/InstantRails/ruby/bin/rake:19:in `load'
>> C:/InstantRails/ruby/bin/rake:19
>> 
>> I don't know what todo(is it a deadlock)
>> 
>> please help
>> 
>> Thanks
>> SumeetPanchal
> 
> -- 
> 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.

Reply via email to