I'm trying to start a Flying-Sphinx (Wooden) but getting Faraday::Error::ParsingError seemingly because something returns a response that looks like Rails default error page for internal server error. I suppose this response is coming from Flying-Sphinx server (although not sure), so I though this is good to report, as it might be a bug there.
What makes it interesting is that our staging server (another Heroku app) starts ok, with same settings (even if I make it use the same database as the (to-be) production server. So I can't figure out what is the difference in my config, but the different heroku apps get different behavior when running the same code on same database.
Indexing works ok, but when I run heroku run flying-sphinx
start it produces:
Running `flying-sphinx start` attached to terminal... up, run.1
[2012-10-01 16:13:59 UTC] API Request: GET '/'; params: {}
[2012-10-01 16:13:59 UTC] API Response: #<Hashie::Rash database_port=10318 port=9318 server="ec2-23-22-176-191.compute-1.amazonaws.com" ssh_server="ec2-23-22-176-191.compute-1.amazonaws.com" status="OK">
[2012-10-01 16:13:59 UTC] API Request: POST 'start'; params: {}
/app/vendor/bundle/ruby/1.9.1/gems/json-1.7.5/lib/json/common.rb:155:in `parse': 757: unexpected token at '<!DOCTYPE html> (Faraday::Error::ParsingError)
<html>
<head>
<title>We're sorry, but something went wrong (500)</title>
<style type="text/css">
body { background-color: #fff; color: #666; text-align: center; font-family: arial, sans-serif; }
div.dialog {
width: 25em;
padding: 0 4em;
margin: 4em auto 0 auto;
border: 1px solid #ccc;
border-right-color: #999;
border-bottom-color: #999;
}
h1 { font-size: 100%; color: #f00; line-height: 1.5em; }
</style>
</head>
<body>
<!-- This file lives in public/500.html -->
<div class="dialog">
<h1>We're sorry, but something went wrong.</h1>
<p>We've been notified about this issue and we'll take a look at it shortly.</p>
</div>
</body>
</html>
'
from /app/vendor/bundle/ruby/1.9.1/gems/json-1.7.5/lib/json/common.rb:155:in `parse'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday_middleware-0.8.8/lib/faraday_middleware/response/parse_json.rb:11:in `block in <class:ParseJson>'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday_middleware-0.8.8/lib/faraday_middleware/response_middleware.rb:48:in `call'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday_middleware-0.8.8/lib/faraday_middleware/response_middleware.rb:48:in `parse'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday_middleware-0.8.8/lib/faraday_middleware/response_middleware.rb:39:in `process_response'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday_middleware-0.8.8/lib/faraday_middleware/response_middleware.rb:32:in `block in call'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.4/lib/faraday/response.rb:63:in `on_complete'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday_middleware-0.8.8/lib/faraday_middleware/response_middleware.rb:30:in `call'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.4/lib/faraday/response.rb:8:in `call'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.4/lib/faraday/request/url_encoded.rb:14:in `call'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.4/lib/faraday/connection.rb:226:in `run_request'
from /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.4/lib/faraday/connection.rb:99:in `post'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/lib/flying_sphinx/api.rb:23:in `block in post'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/lib/flying_sphinx/api.rb:69:in `call'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/lib/flying_sphinx/api.rb:69:in `log'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/lib/flying_sphinx/api.rb:22:in `post'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/lib/flying_sphinx/configuration.rb:16:in `start_sphinx'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/lib/flying_sphinx/cli.rb:64:in `start'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/lib/flying_sphinx/cli.rb:20:in `block in run'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/lib/flying_sphinx/cli.rb:20:in `each'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/lib/flying_sphinx/cli.rb:20:in `all?'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/lib/flying_sphinx/cli.rb:20:in `run'
from /app/vendor/bundle/ruby/1.9.1/gems/flying-sphinx-0.8.4/bin/flying-sphinx:5:in `<top (required)>'
from bin/flying-sphinx:16:in `load'
from bin/flying-sphinx:16:in `<main>'
#1 Posted by Pat Allan Support staff on 01 Oct, 2012 09:27 PM
Hi Antti
Sorry about that - a previous customer's Sphinx daemon hadn't been shut off properly, and it was still using your port. I've killed that process, so you should be good to go. Let me know if there's any other issues.
Kind regards
Pat
#2 Posted by antti on 01 Oct, 2012 10:16 PM
Hi!
Now it works! Thanks Pat!
-Antti
#3 Posted by sapna.j on 25 Apr, 2013 11:24 AM
Hello Pat,
I am also getting same error when I am trying to start flying sphinix on the heroku....
my heroku logs is
Pat Allan closed this discussion on 13 Jan, 2014 11:23 PM.