From: Todd Kjos <tkjos@google.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: kernelci@groups.io, Guenter Roeck <groeck@google.com>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: can't access kernelci results
Date: Mon, 5 Apr 2021 16:14:50 -0700 [thread overview]
Message-ID: <CAHRSSEwnBrT0wnc+-dA2FXvu1udstwArFRYtHu+f-79fZgd2JQ@mail.gmail.com> (raw)
In-Reply-To: <2a6d7691-b8a5-da92-865c-8cdf5efb673f@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
Working again. Thanks Guillaume.
On Mon, Apr 5, 2021 at 1:58 PM Guillaume Tucker <
guillaume.tucker@collabora.com> wrote:
> On 05/04/2021 21:39, Guenter Roeck via groups.io wrote:
> > On Mon, Apr 5, 2021 at 12:30 PM Todd Kjos via groups.io
> > <tkjos=google.com@groups.io> wrote:
> >>
> >> I get errors when attempting to access
> https://linux.kernelci.org/job/android/. Is this a known issue? Any ETA
> for a fix?
> >>
> > Looks like the problem is not limited to android. I get error 500 for
> > jobs and build results.
>
> That was another case of the mongod service stopping, it's pretty
> rare but has happened a couple of times before. Things are now
> back to normal, but we've missed a few results while it was down.
> Sorry for the disruption.
>
> We've deployed a monitoring tool on some servers but not yet on
> this one, it should happen soon so this kind of issues would be
> detected much quicker. We've also started looking into using a
> Mongo database in Azure rather than a manual install to reduce
> maintenance work.
>
> Best wishes,
> Guillaume
>
[-- Attachment #2: Type: text/html, Size: 1763 bytes --]
next prev parent reply other threads:[~2021-04-05 23:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 19:02 can't access kernelci results Todd Kjos
2021-04-05 20:39 ` Guenter Roeck
2021-04-05 20:58 ` Guillaume Tucker
2021-04-05 23:14 ` Todd Kjos [this message]
2021-06-21 19:59 ` Todd Kjos
2021-06-22 9:43 ` Michał Gałka
2021-06-22 15:07 ` Todd Kjos
2021-06-22 15:16 ` Guillaume Tucker
2021-09-02 15:58 ` Todd Kjos
2021-09-02 19:28 ` Todd Kjos
2021-11-30 16:35 ` Todd Kjos
2021-11-30 16:54 ` Todd Kjos
2021-12-01 9:48 ` Guillaume Tucker
2022-03-18 15:47 ` Todd Kjos
2022-03-18 17:19 ` Guillaume Tucker
2022-03-18 17:26 ` Guillaume Tucker
2022-09-26 15:29 ` Todd Kjos
2022-09-26 15:35 ` Denys Fedoryshchenko
[not found] ` <17187305E642C450.18151@groups.io>
2022-09-26 16:06 ` Denys Fedoryshchenko
2022-09-26 16:13 ` Todd Kjos
2022-10-14 18:12 ` Todd Kjos
2022-10-14 18:16 ` Denys Fedoryshchenko
2022-10-14 18:39 ` Todd Kjos
2022-10-21 16:25 ` Todd Kjos
2022-10-22 7:00 ` Denys Fedoryshchenko
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=CAHRSSEwnBrT0wnc+-dA2FXvu1udstwArFRYtHu+f-79fZgd2JQ@mail.gmail.com \
--to=tkjos@google.com \
--cc=groeck@google.com \
--cc=guillaume.tucker@collabora.com \
--cc=kernelci@groups.io \
--cc=khilman@baylibre.com \
/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;
as well as URLs for NNTP newsgroup(s).