From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Bugzilla down
Date: Wed, 02 Jan 2019 13:36:28 +0000
Message-ID: <D33827C8-487A-4BB4-9E46-D5BC0B6376AF@ipfire.org>
In-Reply-To: <e5753a65-4f4b-27a7-e02c-d608178050ec@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7536922010839180776=="
List-Id: <development.lists.ipfire.org>

--===============7536922010839180776==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello,

Thanks. That was a tricky one, but BZ is back.

We had a bit of a larger server meltdown on Sunday where suddenly two hardwar=
e nodes rebooted at the same time. As a result the entire project was offline=
. This isn=E2=80=99t great at all and I am still investigating what it was.

However, most of the infrastructure came back fine. BZ could not start proper=
ly because of a SELinux issue which prevented apache to read the bugzilla con=
figuration file.

Best,
-Michael

> On 31 Dec 2018, at 17:27, Matthias Fischer <matthias.fischer(a)ipfire.org> =
wrote:
>=20
> Hi,
>=20
> it seems I'm the one with the bad news these days... ;-)
>=20
> If someone has the time - and the nerves:
>=20
> https://bugzilla.ipfire.org doesn't talk to us anymore, it only says:
>=20
> "Bad Request
> Your browser sent a request that this server could not understand."
>=20
> Best regards for the coming New Year,
>=20
> Matthias


--===============7536922010839180776==--