From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Git, Nightly, Pakfire 503 Service Unavailable
Date: Tue, 12 Jul 2022 09:43:23 +0200 [thread overview]
Message-ID: <F48BBEB9-308C-4AE1-9745-56D080FBA995@ipfire.org> (raw)
In-Reply-To: <795ef342-1221-3f63-da25-ce002d728f4e@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
Good morning,
Yes, there is.
Over the last couple of nights, we rolled out the latest Debian updates, but our main file server keeps crashing with some kernel panic.
I tried debugging this, which was rather unsuccessful and now booted back into the previous kernel, hoping that that will fix the problem for now.
Apologies for the inconvenience.
-Michael
> On 12 Jul 2022, at 02:39, Charles Brown <cab_77573(a)yahoo.com> wrote:
>
> Hi all,
>
> Is there a web-server outage in IPFire infrastructure land?
> or am I the only one getting 503 when visiting: git.ipfire.org, nightly.ipfire.org, or running pakfire update
>
> -Charles
>
next prev parent reply other threads:[~2022-07-12 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <795ef342-1221-3f63-da25-ce002d728f4e.ref@yahoo.com>
2022-07-12 0:39 ` Charles Brown
2022-07-12 0:49 ` Charles Brown
2022-07-12 7:43 ` Michael Tremer [this message]
2022-07-12 8:29 ` Matthias Fischer
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=F48BBEB9-308C-4AE1-9745-56D080FBA995@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