sentry-cli: error: http error: [55] Failed sending data to the peer (Send failure: Broken pipe)
when i upload-dsym by command:
sentry-cli --log-level debug upload-dsym --org sentry --project myProject .
[INFO] sentry_cli::api request POST http://mysentry.cn:9000/api/0/projects/sentry/myProject/files/dsyms/
[INFO] sentry_cli::api using token authentication
[INFO] sentry_cli::api sending form data
error: http error: [55] Failed sending data to the peer (Send failure: Broken pipe)
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 11
- Comments: 36 (11 by maintainers)
Commits related to this issue
- fix(uwsgi): Fix broken uWSGI config (#237) This patch introduces the following fixes to uWSGI config which was not set up correctly to be used publicly (not behind a router, load balancer, proxy li... — committed to getsentry/self-hosted by BYK 5 years ago
- fix(devserver): Fix broken uWSGI config for bare HTTP We've been using uWSGI in HTTP-proxy mode which was meant to communicate with upstream front-proxies like Nginx. We also lacked the keep-alive op... — committed to getsentry/sentry by BYK 5 years ago
- fix(devserver): Fix broken uWSGI config for bare HTTP (#14462) We've been using uWSGI in HTTP-proxy mode which was meant to communicate with upstream front-proxies like Nginx. We also lacked the ke... — committed to getsentry/sentry by BYK 5 years ago
- fix(uwsgi): Fix broken uWSGI config (#237) This patch introduces the following fixes to uWSGI config which was not set up correctly to be used publicly (not behind a router, load balancer, proxy li... — committed to hinthealth/onpremise by BYK 5 years ago
@robrohan then disable keepalives in the sentry cli config: https://docs.sentry.io/learn/cli/configuration/#configuration-values (
http.keepalivetofalse)@BYK I can confirm that adjusting this config works.
For people using Docker from the command line (or batch files), adding this fixed it!
@Atrejoe for folks using the onpremise repo, it should be resolved after https://github.com/getsentry/onpremise/pull/237/files
If you are only using the Docker images, we probably should update the default configuration in them too but not sure that’d be the best for everyone.
Anyway, if you need this fix ASAP, you can simply apply the changes from https://github.com/getsentry/onpremise/pull/237/files to your own config file and you should be good to go.
Maybe
uwsgican not deal with so many requests, but for nginx ,it is fine