-
Notifications
You must be signed in to change notification settings - Fork 546
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I request my site sometimes I get an error "application did not send a complete response" #1606
Comments
This happens when your application exits prematurely. To understand what this means, consider that Passenger works by sitting between the client and the app. Passenger acts like a reverse proxy, so it forwards the request to your app, then processes the response that the app sends.
If, after Passenger has sent the request, the app crashes or otherwise exits before sending a response, then you will see "application did not send a complete response". So the question is actually: why does the application exit? Unfortunately I do not know, and neither does Passenger. Passenger only starts your app and expects your app to respond to requests as normal. Maybe there is a bug in the app, or the app encountered some sort of fatal error. Normally the app will print an error message when that happens, but Passenger did not encounter any such messages, or it would have printed them. So the best thing I can recommend you to do is that you insert debugging statements inside your app and find out what makes it exit. |
Thanks, FooBarWidget! |
Info for future researchers: there was a "out of memory" error. My app was deployed on a small OpenVZ VPS hosting and without swap (vswap). |
How did you figure out if it's an "out of memory" error? free -t -m
Mem: 1500 1184 315 17 58 624 |
passenger start --daemonize --port 4040 --user webmaster -e production
The text was updated successfully, but these errors were encountered: