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 [thread overview]
Message-ID: <D33827C8-487A-4BB4-9E46-D5BC0B6376AF@ipfire.org> (raw)
In-Reply-To: <e5753a65-4f4b-27a7-e02c-d608178050ec@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
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 hardware nodes rebooted at the same time. As a result the entire project was offline. This isn’t great at all and I am still investigating what it was.
However, most of the infrastructure came back fine. BZ could not start properly because of a SELinux issue which prevented apache to read the bugzilla configuration file.
Best,
-Michael
> On 31 Dec 2018, at 17:27, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> it seems I'm the one with the bad news these days... ;-)
>
> If someone has the time - and the nerves:
>
> https://bugzilla.ipfire.org doesn't talk to us anymore, it only says:
>
> "Bad Request
> Your browser sent a request that this server could not understand."
>
> Best regards for the coming New Year,
>
> Matthias
parent reply other threads:[~2019-01-02 13:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <e5753a65-4f4b-27a7-e02c-d608178050ec@ipfire.org>]
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=D33827C8-487A-4BB4-9E46-D5BC0B6376AF@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