List for cgit developers and users
 help / color / mirror / Atom feed
From: roy at (Roy Marples)
Subject: Error downloading snapshots from remote sites
Date: Mon, 4 May 2020 14:29:19 +0100
Message-ID: <> (raw)
In-Reply-To: <1588598577.igqg9k4jc9.none@localhost>

Hi Alex

On 04/05/2020 14:23, Alex Xu (Hello71) wrote:
> Excerpts from Roy Marples's message of May 4, 2020 5:45 am:
>> Hi
>> I only get this error downloading from a remote VM.
>> Another user has reported the error here:
>> Error is a sample error logged by nginx:
>> I use uwsgi to proxy the cgi to nginx.
>> *248 open() "/var/db/nginx/uwsgi_temp/6/00/0000000006" failed (13: Permission
>> denied) while reading upstream, client: 2001:470:a085:999::80, server:
>>, request: "GET /cgit/dhcpcd.git/snapshot/master.tar.xz
>> HTTP/1.1", upstream: "uwsgi://unix:/var/run/uwsgi/cgit.sock:", host:
>> ""
>> Otherwise this setup works fine.
>> The user uwsgi/cgit runs as owns the directory /var/db/nginx/uwsgi_temp.
>> Any pointers on how to fix this?
>> Thanks
>> Roy
> nginx buffers large responses to disk by default. most likely your whole
> uwsgi buffering is broken, but you only see it with snapshots because
> nginx decides that the response cannot fit into memory. in particular,
> /var/db/nginx needs to be owned by the nginx user (nginx/http/www-data),
> not the uwsgi user.
> this behavior can be adjusted with various tuning knobs:
> you may want
> to set uwsgi_buffering off. however, this prevents some useful features,
> including as I recall output compression. you can also try setting
> something like location ^ /snapshot/ { uwsgi_buffering off; }. that
> won't fix your temp_path issues though, which you will still have if
> someone requests some other large file.

Thanks for the reply.
It turned out the process needed to access ALL the folders in the path and one 
was locked out.
Discovered thanks to this post:



      reply	other threads:[~2020-05-04 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04  9:45 roy
2020-05-04 13:23 ` alex_y_xu
2020-05-04 13:29   ` roy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \
    --to= \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

List for cgit developers and users

This inbox may be cloned and mirrored by anyone:

	git clone --mirror

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 cgit cgit/ \
	public-inbox-index cgit

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone