From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: git.ipfire =>very slow loading
Date: Wed, 15 Aug 2018 09:34:40 +0100 [thread overview]
Message-ID: <0b636cea0d7e25fd380787d4e2e76c18be2d00ca.camel@ipfire.org> (raw)
In-Reply-To: <7a0b1340-b14d-d6a3-43db-9fdc36a42fa1@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 3084 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I created a ticket to have a look at it later:
https://bugzilla.ipfire.org/show_bug.cgi?id=11818
- -Michael
On Sun, 2018-08-12 at 09:10 +0200, Peter Müller wrote:
> 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
> > >
> > >
>
>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAltz5aAACgkQgHnw/2+Q
CQekFA//V8LYupgPNjIiyhrFndtGQgmUeT+wN+quLdQDN5rB14IwLKDlmHzRfXlr
mCEDT7Z02ejLo/FAUlvn946iX6uF/qibhO6UQ0OG0Xe2c3vMEYfJM9toKnN7Ghhk
9M3wEtawliV0+qNTTfc/0RsJbcTJQB0GaQory4e7zuFCL0oQslq6UODIzqQGkMl5
x3Uqg7vrKXeETpHeI94ktKsD0znEH44ih9pvdB6+KqvzGBVqmnan4LxgGOdboAYW
j363TCM95vFbiS2CxC9wUwsb3A9eHDT6acg+grDDt/aA4v6AIcSh0z+4aJppDTXZ
+YcAuklRaXW9XAPTPn58Mjx6IYMJvKfdGlJpRTNkCWOMuAzNuVfPmf88GcWAqKdj
08kTPa42YAqqoilv/vsasmowgel2Ze7VsQ1tCPYzSmdHoeSM42YY482nOcWjnhu8
Cb6U0VEami1OT9pSoXwVYgwpFOYchFAcsIynReJdkbX+lZk5jfh9zwJQmS9kYYD3
k4dZ00IjHahhRIh8mYz//19Q1NrAmPCT7peX2EeENKsfTlo/qMHLLCrUPP8LSHO9
l0rPp0MHWbtqGsgpRvR0KK8jYvuuzzPDC5HSLQZTyshiMck9BmNEqeWFtzI4cp/o
8ygw4J6qWk2DLei7AG6I+SzXvB7FHmI3gSEOqwyze+Oh6NtQwxM=
=VrTQ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2018-08-15 8:34 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
2018-08-15 8:34 ` Michael Tremer [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:
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=0b636cea0d7e25fd380787d4e2e76c18be2d00ca.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--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