From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: git.ipfire =>very slow loading
Date: Sun, 12 Aug 2018 09:10:26 +0200 [thread overview]
Message-ID: <7a0b1340-b14d-d6a3-43db-9fdc36a42fa1@link38.eu> (raw)
In-Reply-To: <95c692e6-2836-79b2-d20d-097f76b010b7@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1911 bytes --]
Hello,
same here... Sometimes with, sometimes without an XML parsing error.
Best regards,
Peter Müller
> Hi,
>
> On 05.08.2018 12:24, Michael Tremer wrote:
>> Errr, no. This is not migrating any more, but has been migrated.
>
> As it seems - it migrated "very far away".
>
> First try gives me:
>
> ...
> XML Parsing Error: no root element found Location:
> https://git.ipfire.org/ Line Number 27, Column 1:
>
> ^
> ...
>
> Second try:
> A white page with "git://git.ipfire.org" and a project search box.
>
> Third try:
> Same as first: "XML Parsing error..."
>
> Any one else?
>
> Best,
> Matthias
>
>> Since we are having some things we can do better with our many web
>> servers, I started using haproxy on our primary firewall and everything
>> else is now being proxies from there to the right internal server.
>>
>> That means, that the git repositories are now coming directly from the
>> server where they are hosted and are not being transferred over NFS
>> first. Same goes for downloads. That puts quite a bit less load on the
>> servers and makes the downloads slightly faster.
>>
>> I also moved Gitweb to a new server which is now running Apache and not
>> nginx any more. However, apache doesn't correctly cache the index page.
>> I don't know why that is, but it is just being stupid. Hence the slight
>> delay to render the page.
>>
>> Best,
>> -Michael
>>
>> On Sat, 2018-08-04 at 21:39 +0200, Matthias Fischer wrote:
>>> On 04.08.2018 15:54, Michael Tremer wrote:
>>>> I just spent two hours to debug this fe**cking thing. It was a
>>>> configuration issue that was caused by the migration.
>>>
>>> Besides, since a few days loading git.ipfire.org takes about 15-20
>>> seconds. FF shows "Transferring data from git.ipfire.org" and nothing
>>> happens...
>>>
>>> Migration!?
>>>
>>> Best,
>>> Matthias
>>
>>
>
--
"We don't care. We don't have to. We're the Phone Company."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-12 7:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 8:00 patchwork.ipfire.org didn't get last two patches Matthias Fischer
2018-08-04 11:57 ` ummeegge
2018-08-04 13:54 ` Michael Tremer
2018-08-04 16:04 ` Matthias Fischer
2018-08-04 17:58 ` Michael Tremer
2018-08-04 19:35 ` Matthias Fischer
2018-08-04 19:39 ` git.ipfire =>very slow loading (was: Re: patchwork.ipfire.org didn't get last two patches) Matthias Fischer
2018-08-05 10:24 ` Michael Tremer
2018-08-11 19:45 ` git.ipfire =>very slow loading Matthias Fischer
2018-08-12 7:10 ` Peter Müller [this message]
2018-08-15 8:34 ` Michael Tremer
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=7a0b1340-b14d-d6a3-43db-9fdc36a42fa1@link38.eu \
--to=peter.mueller@link38.eu \
--cc=development@lists.ipfire.org \
/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