-
Notifications
You must be signed in to change notification settings - Fork 548
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
Request Queue Size - determine what's hanging. #1619
Comments
@mmahalwy You manage to figure out the steps to nail the culprit ? I am having the same problem here and would love to know how to find out. |
we have got the same problem. request In queue are stuck. and cpu load show 0%. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have two servers, both high in traffic and usage. Initially we kept getting the error
Request queue full (configured max. size: 100)
and crashed every ~12hrs. Now we bumped it up to 200 and at times every 24hrs we have a crash. Below is thepassenger-status
of both our servers at the time one (the first one) crashed. Note, the latter has a process that was used 4s ago from when passenger-status was run, while the other server (the first) is not getting used.How do we find out what is causing passenger to hang or it's threads to hang? When doing
passenger-status --show=requests
it doesn't show enough information to determine what's causing the hang.Thanks!
First server, down:
Second, working server:
The text was updated successfully, but these errors were encountered: