List for cgit developers and users
 help / color / mirror / Atom feed
From: john at keeping.me.uk (John Keeping)
Subject: cgit v0.10.2-26 + apache2 = random 500 Internal Server Error
Date: Fri, 9 Jan 2015 11:14:39 +0000	[thread overview]
Message-ID: <20150109111439.GC26383@serenity.lan> (raw)
In-Reply-To: <20150109120503.5a88a4ab@FR-B-701-006.Parrot.biz>

On Fri, Jan 09, 2015 at 12:05:03PM +0100, Fabien Bagard wrote:
> I do face a strange problem with cgit 0.10.2-26 (Pulled from git).
> 
> All my repos are correctly scanned, but after a random amount of time,
> from 5 secondes to tens of minutes, it seems something stops working :
> Apache2 throws ans error 500 : Internal server error.
> Sometimes it starts to work again, but most of the time, I have to
> reload apache. Not using apache is not a solution

This sounds like an Apache problem and not anything to do with CGit
(although I guess CGit could be triggering the issue).

Since CGit is a CGI process, there is nothing that persists between
requests, so I would not expect a CGit problem to relate to the lifetime
of the Apache process.


  reply	other threads:[~2015-01-09 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 11:05 fabien.bagard
2015-01-09 11:14 ` john [this message]
2015-01-09 11:24   ` fabien.bagard

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20150109111439.GC26383@serenity.lan \
    --to=cgit@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).