kernelci.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Todd Kjos <tkjos@google.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: "Michał Gałka" <michal.galka@collabora.com>,
	kernelci@groups.io, "Guenter Roeck" <groeck@google.com>,
	"Kevin Hilman" <khilman@baylibre.com>
Subject: Re: can't access kernelci results
Date: Fri, 18 Mar 2022 08:47:22 -0700	[thread overview]
Message-ID: <CAHRSSEwB_L-i0UZH01s424vPog7ArU=uSutsqmexMSO92JtTNA@mail.gmail.com> (raw)
In-Reply-To: <803b89a9-9141-636f-8fd3-f519b0440075@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 3102 bytes --]

Is the MongoDB server down again? I don't get results at
https://linux.kernelci.org/job/android/.

On Wed, Dec 1, 2021 at 1:49 AM Guillaume Tucker <
guillaume.tucker@collabora.com> wrote:

> Hi Todd,
>
> On 30/11/2021 16:54, Todd Kjos wrote:
> > ...and now it's working again. Sorry about the noise if the issue was
> > on my side.
>
> The MongoDB server did crash but it was restarted a few minutes
> later.  There's some kind of watchdog to do that automatically,
> maybe you were out of luck and checked the website during that
> window.  Thanks for reporting the issue in any case.
>
> Best wishes,
> Guillaume
>
> > On Tue, Nov 30, 2021 at 8:35 AM Todd Kjos <tkjos@google.com> wrote:
> >>
> >> I can't load the data from https://linux.kernelci.org/job/android/
> >> ("Error loading build data."). Is mongod "borked" again?
> >>
> >> On Thu, Sep 2, 2021 at 12:28 PM Todd Kjos <tkjos@google.com> wrote:
> >>>
> >>> It's working again. Thanks.
> >>>
> >>> On Thu, Sep 2, 2021 at 8:58 AM Todd Kjos <tkjos@google.com> wrote:
> >>>>
> >>>> I'm getting errors again when attempting to access
> >>>> https://linux.kernelci.org/job/android/. mongod issues again?
> >>>>
> >>>> "Error while loading data from the server (error code: 500). Please
> >>>> contact the website administrator"
> >>>>
> >>>> On Tue, Jun 22, 2021 at 8:17 AM Guillaume Tucker
> >>>> <guillaume.tucker@collabora.com> wrote:
> >>>>>
> >>>>> On 22/06/2021 16:07, Todd Kjos wrote:
> >>>>>> Hmm, it's still not working for me -- did it break again?
> >>>>>
> >>>>> Yes there was an OOM issue:
> >>>>>
> >>>>> [4316410.416514] Killed process 20620 (mongod) total-vm:20171340kB,
> anon-rss:18654740kB, file-rss:0kB, shmem-rss:0kB
> >>>>> [4316412.060511] oom_reaper: reaped process 20620 (mongod), now
> anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
> >>>>>
> >>>>> We're looking into moving the Mongo DB instance to the cloud in
> >>>>> Azure.  Hopefully that will save us fixing this kind of
> >>>>> maintenance issues.  Meanwhile, we should take a look and see if
> >>>>> there's some config option to limit the amount of RAM used by
> >>>>> Mongo DB to work around the problem.
> >>>>>
> >>>>> Best wishes,
> >>>>> Guillaume
> >>>>>
> >>>>>
> >>>>>> On Tue, Jun 22, 2021 at 2:43 AM Michał Gałka <
> michal.galka@collabora.com <mailto:michal.galka@collabora.com>> wrote:
> >>>>>>
> >>>>>>     On 21.06.2021 21:59, Todd Kjos via groups.io <http://groups.io>
> wrote:
> >>>>>>     > I'm having this issue again (can't access kernelci results
> >>>>>>     > at https://linux.kernelci.org/job/android/ <
> https://linux.kernelci.org/job/android/>
> >>>>>>     > <https://linux.kernelci.org/job/android/ <
> https://linux.kernelci.org/job/android/>>). Is the mongod service borked
> >>>>>>     > again?
> >>>>>>     >
> >>>>>>
> >>>>>>     Yes, there was an issue with mongod service again. It's working
> now,
> >>>>>>     celery processed pending tasks and everything seems responsive.
> >>>>>>
> >>>>>>     Thanks,
> >>>>>>     Michał
> >>>>>>
> >>>>>
>
>

[-- Attachment #2: Type: text/html, Size: 5507 bytes --]

  reply	other threads:[~2022-03-18 15:47 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
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 [this message]
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='CAHRSSEwB_L-i0UZH01s424vPog7ArU=uSutsqmexMSO92JtTNA@mail.gmail.com' \
    --to=tkjos@google.com \
    --cc=groeck@google.com \
    --cc=guillaume.tucker@collabora.com \
    --cc=kernelci@groups.io \
    --cc=khilman@baylibre.com \
    --cc=michal.galka@collabora.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).