Re: [OE-core] [PATCH] cve-check-update-nvd2-native: Incremement DL_DIR database location

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2024-10-11 at 13:24 +0200, Marta Rybczynska wrote:
> 
> 
> On Fri, Oct 11, 2024 at 1:19 PM Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > 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
> > 
> > 
> 
> 
> Managed to get the same error with the sqlite command line.


I merged this patch as it would rule out a lot of things. The error recurred:

https://valkyrie.yoctoproject.org//#/builders/76/builds/235/steps/14/logs/stdio

This means that it happens with the access patterns in master alone.
I'm also noticing there seems to be a trend for this to happen on alma9
(older centos systems?).

Running those tests manually on that worker passed the tests ok.

It has python 3.9.18 with sqlite3 not available as an external command.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=14899

Cheers,

Richard