tag:support.flying-sphinx.com,2011-01-05:/discussions/problems/10468-flying-sphinx-index-hangsFlying Sphinx: Discussion 2018-02-09T09:53:40Ztag:support.flying-sphinx.com,2011-01-05:Comment/427488952017-06-12T02:16:28Z2017-06-12T02:16:29Zflying-sphinx index Hangs<div><p>I have tried running flying-sphinx and likewise bundle exec rake fs:index and the process just hangs on "INFO -- : Executing Action: index". I have configured the certificate chain to use a MySQL database from ClearDB. The application deploys to heroku without issue and I can see successful queries in the heroku logs, but nothing is showing an obvious error. I always have to ctrl-c out of the process as it runs for far too long and goes nowhere. The result of running heroku run bundle exec rake fs:index is:</p>
<p>/app/vendor/bundle/ruby/2.3.0/gems/newrelic_rpm-3.9.1.236/lib/new_relic/agent/configuration/default_source.rb:675: warning: key :disable_mongo is duplicated and overwritten on line 987 ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Starting the New Relic agent in "production" environment. ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : To prevent agent startup add a NEWRELIC_AGENT_ENABLED=false environment variable or modify the "production" section of your newrelic.yml. ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Reading configuration from config/newrelic.yml ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] WARN : Agent is configured not to use SSL when communicating with New Relic's servers ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Environment: production ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : No known dispatcher detected. ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Application: Sharetribe ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : delayed_job not available: No DJ worker present /app/vendor/bundle/ruby/2.3.0/gems/newrelic_rpm-3.9.1.236/lib/new_relic/agent/vm/mri_vm.rb:32: warning: GC.stat keys were changed from Ruby 2.1. In this case, you refer to obsolete <code>total_allocated_object' (new key is</code>total_allocated_objects'). Please check <a href="https://bugs.ruby-lang.org/issues/9924">https://bugs.ruby-lang.org/issues/9924</a> for more information. ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Installing Dalli Memcache instrumentation ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Installing DelayedJob instrumentation [part 1/2] ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Installing Net instrumentation ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Installing deferred Rack instrumentation ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Installing Rack::Builder middleware instrumentation ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Installing Rails 3+ middleware instrumentation ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Installing ActiveRecord 4 instrumentation ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Installing Rails 4 Error instrumentation ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Installing Rails 4 view instrumentation ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Installing Rails 4 Controller instrumentation ** [NewRelic][06/12/17 01:12:49 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Finished instrumentation I, [2017-06-12T01:12:50.065723 #4] INFO -- : Executing Action: configure<br>
** [NewRelic][06/12/17 01:12:50 +0000 48878c54-80b8-4384-8844-a7f4abd68535 (4)] INFO : Reporting to: <a href="https://rpm.newrelic.com/accounts/1653428/applications/53911869">https://rpm.newrelic.com/accounts/1653428/applications/53911869</a> /app/vendor/bundle/ruby/2.3.0/gems/multipart-post-1.2.0/lib/composite_io.rb:19: warning: UploadIO#respond_to?(:to_ary) is old fashion which takes only one parameter /app/vendor/bundle/ruby/2.3.0/gems/multipart-post-1.2.0/lib/composite_io.rb:105: warning: respond_to? is defined here /app/vendor/bundle/ruby/2.3.0/gems/multipart-post-1.2.0/lib/composite_io.rb:19: warning: UploadIO#respond_to?(:to_ary) is old fashion which takes only one parameter /app/vendor/bundle/ruby/2.3.0/gems/multipart-post-1.2.0/lib/composite_io.rb:105: warning: respond_to? is defined here /app/vendor/bundle/ruby/2.3.0/gems/multipart-post-1.2.0/lib/composite_io.rb:19: warning: UploadIO#respond_to?(:to_ary) is old fashion which takes only one parameter /app/vendor/bundle/ruby/2.3.0/gems/multipart-post-1.2.0/lib/composite_io.rb:105: warning: respond_to? is defined here /app/vendor/bundle/ruby/2.3.0/gems/multipart-post-1.2.0/lib/composite_io.rb:19: warning: UploadIO#respond_to?(:to_ary) is old fashion which takes only one parameter /app/vendor/bundle/ruby/2.3.0/gems/multipart-post-1.2.0/lib/composite_io.rb:105: warning: respond_to? is defined here I, [2017-06-12T01:12:53.840877 #4] INFO -- : Action Finished: configure<br>
I, [2017-06-12T01:12:53.841054 #4] INFO -- : Executing Action: index<br>
^Crake aborted!</p>
<p>How can I fix this?</p></div>Liam Elliotttag:support.flying-sphinx.com,2011-01-05:Comment/427488952017-06-12T02:18:26Z2017-06-12T02:18:30Zflying-sphinx index Hangs<div><p>If it is needed, the application is hosted at lehhko.herokuapp.com</p></div>Liam Elliotttag:support.flying-sphinx.com,2011-01-05:Comment/427488952017-06-12T02:26:49Z2017-06-12T02:26:49Zflying-sphinx index Hangs<div><p>Hi Liam,</p>
<p>Thanks for getting in touch, and providing the app name, that’s definitely helped me investigate a bit further.</p>
<p>I’m not yet sure of the cause of the problem though… but I can see in the logs that a full index (as part of the rebuild command) takes less than a minute, so I’d expect to have the command wrap up by then. However, while I’m seeing the configure commands coming through (as noted in the output you shared), I’m not seeing indexing requests appear, which is definitely odd.</p>
<p>Can you confirm the versions of flying-sphinx and thinking-sphinx gems you’re using?</p>
<p>Thanks,</p>
<p>— Pat</p></div>Pat Allantag:support.flying-sphinx.com,2011-01-05:Comment/427488952017-06-12T02:30:06Z2017-06-12T02:30:09Zflying-sphinx index Hangs<div><p>Hi Pat, thanks for the speedy reply. I am running:</p>
<p>flying-sphinx (1.2.0)<br>
thinking-sphinx (3.1.4)</p></div>Liam Elliotttag:support.flying-sphinx.com,2011-01-05:Comment/427488952017-06-12T02:33:29Z2017-06-12T02:33:29Zflying-sphinx index Hangs<div><p>Just figured out the problem - some overzealous caching which wasn’t up-to-date with the fact you’d configured your app (indexing doesn’t bother attempting otherwise - a relatively new change (and thus, new bug) I’d made).</p>
<p>I’ve cleared the cache and am in the process of putting in a permanent fix, but indexing will work for your app right now :)</p></div>Pat Allantag:support.flying-sphinx.com,2011-01-05:Comment/427488952017-06-12T02:36:35Z2017-06-12T02:36:36Zflying-sphinx index Hangs<div><p>Holy crap, thanks a lot Pat! Honestly, I'm incredibly impressed with the customer service. If this is how you guys generally respond to concerns, keep up the good work!</p></div>Liam Elliotttag:support.flying-sphinx.com,2011-01-05:Comment/427488952017-06-12T02:39:01Z2017-06-12T02:39:01Zflying-sphinx index Hangs<div><p>I certainly aim to be quick, though the timing was just particularly good on your part, I wasn’t in the middle of anything else (and it’s also the middle of my day right now) 👍</p></div>Pat Allantag:support.flying-sphinx.com,2011-01-05:Comment/427488952018-02-09T09:53:38Z2018-02-09T09:53:40Zflying-sphinx index Hangs<div><p>I have same problem. I have tried both command "heroku run flying-sphinx index" and "heroku run rake fs:index" but both hang up and do not respond.</p></div>Ghulam Jilani