self-hosted icon indicating copy to clipboard operation
self-hosted copied to clipboard

unhealthy sentry_web in sentry_self_hosted25.7.0

Open jetwing opened this issue 3 months ago • 4 comments

Problem Statement

I use install.sh install sentry_self_hosted 25.7.0 when I use docker-compose up -d to start the images, I found sentry-self-hosted-web-1 is unhealthy. I can't open http://localhost:9000 connection refused. I use docker logs sentry-self-hosted-web-1 found errors: uWSGI listen queue of socket "127.0.0.1:37845" (fd: 3) full !!! (101/100) why ?

Solution Brainstorm

No response

jetwing avatar Sep 26 '25 08:09 jetwing

We had the same problem. In sentry/sentry.conf.py - SENTRY_WEB_OPTIONS uncomment and adjust the value of the harakiri option according to the description there and comments in #1573

We've also increased the proxy_read_timeout to 60s in nginx.conf so we set harakiri to 55.

hostalp avatar Sep 29 '25 22:09 hostalp

Thank you very much!I will be try it!

jetwing avatar Sep 30 '25 01:09 jetwing

I have to say that we recently encountered the "uWSGI listen queue full !!! (101/100)" issue even with the harakiri option set. In our case we have set harakiri to 55s and proxy_read_timeout to 60s

We may try decreasing these values, but the traffic isn't particularly high here, therefore I wouldn't expect this kind of issue to occur even with the current values. Moreover, the harakiri setting is rather a bandaid and not a real solution as it shouldn't be normally needed to use such features.

hostalp avatar Oct 20 '25 16:10 hostalp

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

getsantry[bot] avatar Dec 08 '25 08:12 getsantry[bot]