HTTP 500 on create bucket error":"Internal Server Error"
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 437
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 15
Description
Kinto 15.1.1
Confgiuration of kinto instalation:
cli ( curl ) ->> nginx ( 1.18.0 ) --> uwsgi ( 2.0.18 ) -> kinto ( 15.1.1 )
uwsgi vassal kinito.ini
[uwsgi]
wsgi-file = /srv/kinto/app.wsgi
virtualenv = /srv/kinto/kinto-15.1.1/
socket = /run/kinto/kinto.sock
env = = KINTO_INI=/etc/kinto/kinto.ini
uid = kinto
gid = kinto
enable-threads = true
chmod-socket = 666
processes = 3
master = true
module = kinto
harakiri = 120
lazy = true
lazy-apps = true
single-interpreter = true
buffer-size = 65535
post-buffering = 65535
plugin = python3
logto = /var/log/uwsgi/uwsgi-kinto.log
Uwsgi Error:
[pid: 2715084|app: 0|req: 9/19] 10.29.4.69 () {38 vars in 527 bytes} [Fri Mar 17 11:31:56 2023] POST /v1/buckets => generated 177 bytes in 295 msecs (HTTP/1.1 500) 5 headers in 302 bytes (1 switches on core 0)
Nginx Access Log:
10.AA.BB.CC - xxx [17/Mar/2023:11:31:23 +0100] "POST /v1/buckets HTTP/1.1" 500 177 "-" "curl/7.85.0"
10.AA.BB.CC - xxx [17/Mar/2023:11:31:56 +0100] "POST /v1/buckets HTTP/1.1" 500 177 "-" "curl/7.85.0"
Contributor guide
Research direction
Start by reproducing POST /v1/buckets with curl through the nginx and uWSGI setup, then inspect the uWSGI error log and the KINTO_INI configuration at /etc/kinto/kinto.ini. Done means identifying why bucket creation returns HTTP 500 and verifying that the same request succeeds without the internal server error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100