All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Marta Rybczynska <rybczynska@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	Marta Rybczynska <marta.rybczynska@syslinbit.com>,
	Steve Sakoman <steve@sakoman.com>
Subject: Re: [OE-core] [PATCH] cve-check-update-nvd2-native: Incremement DL_DIR database location
Date: Fri, 11 Oct 2024 12:19:36 +0100	[thread overview]
Message-ID: <0092cbd5b19661f2c88084cc2c00811c7c2f6563.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAApg2=RmrYULa7KMi6EMdGAhW3-uVA81ggVJg5BGDMSg0M0nLA@mail.gmail.com>

On Fri, 2024-10-11 at 13:17 +0200, Marta Rybczynska wrote:
> 
> On Fri, Oct 11, 2024 at 1:02 PM Richard Purdie via
> lists.openembedded.org
> <richard.purdie=linuxfoundation.org@lists.openembedded.org> wrote:
> > 
> > I now do have an example of a corrupted database:
> > 
> > https://valkyrie.yocto.io/pub/shared-failure-data/nvdcve_2-1.db
> > 
> > I'm not sure why this is happening but the older releases are all
> > accessing the DB over NFS which makes me nervous. We're seeing a
> > lot of
> > failures on the new cluster, hopefully this will help isolate the
> > problem.
> > 
> 
> 
> The database isn't completely corrupted, it looks like it is partial,
> however. What was the error
> that you got in that build? Any or just strange results? I'm running
> a verification vs a fresh database.

https://valkyrie.yoctoproject.org/#/builders/23/builds/238/steps/14/logs/stdio

Exception: sqlite3.DatabaseError: database disk image is malformed

Cheers,

Richard


  reply	other threads:[~2024-10-11 11:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17FD60BEC9A54A4B.2207@lists.openembedded.org>
2024-10-11 11:02 ` [OE-core] [PATCH] cve-check-update-nvd2-native: Incremement DL_DIR database location Richard Purdie
2024-10-11 11:17   ` Marta Rybczynska
2024-10-11 11:19     ` Richard Purdie [this message]
2024-10-11 11:24       ` Marta Rybczynska
2024-10-13  7:26         ` Richard Purdie
     [not found]         ` <17FDF275CE46F21A.4702@lists.openembedded.org>
2024-10-14 16:07           ` Richard Purdie
2024-10-14 16:15             ` Marta Rybczynska
2024-10-14 16:23               ` Richard Purdie

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=0092cbd5b19661f2c88084cc2c00811c7c2f6563.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=marta.rybczynska@syslinbit.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rybczynska@gmail.com \
    --cc=steve@sakoman.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.