* Re: Bugzilla down
[not found] <e5753a65-4f4b-27a7-e02c-d608178050ec@ipfire.org>
@ 2019-01-02 13:36 ` Michael Tremer
0 siblings, 0 replies; only message in thread
From: Michael Tremer @ 2019-01-02 13:36 UTC (permalink / raw)
To: development
[-- 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-01-02 13:36 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <e5753a65-4f4b-27a7-e02c-d608178050ec@ipfire.org>
2019-01-02 13:36 ` Bugzilla down Michael Tremer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox