We use airbrake to capture errors. And we are getting exceptions
that seem to be caused by flying sphinx error pages.
Initially we got a maintenace page, but now we are getting 500
error page.
Looking at the logs the most recent action is on the 9th April, but
the most recent entry in the index log is 3rd March.
Maintenance page.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
html, body, iframe { margin: 0; padding: 0; height: 100%; } iframe
{ display: block; width: 100%; border: none; } Offline for
Maintenance
Application Error
500 error page.
<!DOCTYPE html> We're sorry, but something went wrong (500)
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; } <!-- This
file lives in public/500.html -->
We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it shortly.
#1 Posted by Pat Allan Support staff on 10 Apr, 2013 12:16 AM
Hi Eamonn
Just to be clear: are you seeing this error on responses from the Flying Sphinx API? Or from your own site? If Airbrake's tracking the errors, what is the stack trace of the exception? And what is your app's name, so I can check the behaviour on the Flying Sphinx servers?
Also: actions are now the definitive record - I'm working on clearing that up in the dashboard.
Kind regards,
Pat
#2 Posted by Eamonn Webster on 10 Apr, 2013 05:04 PM
Pat,
You might be right, I've attached the backtrace from the most recent occurrence
April 9, 2013 - 15:51:37 UTC
The app name on heroku is qs-alpha
FLYING_SPHINX_HOST: ec2-23-22-176-191.compute-1.amazonaws.com
FLYING_SPHINX_IDENTIFIER: a87b6d04db3dcb339
Let me know if there is anything else you need.
Eamonn.
#3 Posted by Pat Allan Support staff on 11 Apr, 2013 12:31 AM
Can you update to flying-sphinx 0.8.5? I know there's issues with 0.8.0, so best to go with a version that doesn't have known bugs.
#4 Posted by Eamonn Webster on 11 Apr, 2013 09:23 AM
Will do, we are in the process of reviewing and upgrading our gems.
Pat Allan closed this discussion on 13 Jan, 2014 11:23 PM.