Thanks James,  "rake thinking_sphinx:index RAILS_ENV=production"
worked.

Thanks again!

On Jul 18, 8:23 pm, James Healy <[email protected]> wrote:
> Sphinx takes your database username and password from your database.yml
> file.
>
> Check that:
> - you have the correct details in the production section of database.yml
> - that you're in production mode when your run the TS indexing task
>   - RAILS_ENV=production rake thinking_sphinx:index
>
> The ThinkingSphinx::ConnectionError exception is only indirectly related
> to the indexing issue. Presumably sphinx can't start since there's no
> index files yet, so TS throws a connection error. If you get your
> indexes generating correctly and start sphinx, the exception should go
> away.
>
> -- James Healy <jimmy-at-deefa-dot-com>  Sun, 19 Jul 2009 10:19:23 +1000
>
> temen wrote:
>
> > Hi,
>
> > I am in the process of deploying my app on a production and
> > successfully installed sphinx and thinking sphinx, but I am getting
> > "Access denied for user 'root'@'localhost' (using password: NO)" when
> > I try to index (rake thinking_sphinx:index).
>
> > Production server info: Ubuntu 9.04, using mysql, phusion passenger
>
> > My dev machine has a similar setup, with the only difference being
> > there is no db password for the dev setup while there is on the
> > production.
>
> > Here is production.log ...
>
> > ThinkingSphinx::ConnectionError (Connection to Sphinx Daemon (searchd)
> > failed.):
> >   app/controllers/users_controller.rb:57:in `index'
> >   passenger (2.2.4) lib/phusion_passenger/rack/request_handler.rb:
> > 91:in `process_request'
> >   passenger (2.2.4) lib/phusion_passenger/abstract_request_handler.rb:
> > 206:in `main_loop'
> >   passenger (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:
> > 376:in `start_request_handler'
> >   passenger (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:
> > 334:in `handle_spawn_application'
> >   passenger (2.2.4) lib/phusion_passenger/utils.rb:182:in `safe_fork'
> >   passenger (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:
> > 332:in `handle_spawn_application'
> >   passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:351:in
> > `__send__'
> >   passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:351:in
> > `main_loop'
> >   passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:195:in
> > `start_synchronously'
> >   passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:162:in
> > `start'
> >   passenger (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:
> > 213:in `start'
> >   passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:261:in
> > `spawn_rails_application'
> >   passenger (2.2.4) lib/phusion_passenger/
> > abstract_server_collection.rb:126:in `lookup_or_add'
> >   passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:255:in
> > `spawn_rails_application'
> >   passenger (2.2.4) lib/phusion_passenger/
> > abstract_server_collection.rb:80:in `synchronize'
> >   passenger (2.2.4) lib/phusion_passenger/
> > abstract_server_collection.rb:79:in `synchronize'
> >   passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:254:in
> > `spawn_rails_application'
> >   passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:153:in
> > `spawn_application'
> >   passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:286:in
> > `handle_spawn_application'
> >   passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:351:in
> > `__send__'
> >   passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:351:in
> > `main_loop'
> >   passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:195:in
> > `start_synchronously'
>
> > Thanks for your help.
--~--~---------~--~----~------------~-------~--~----~
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