On Thu, 2022-01-13 at 19:37 +0100, Michael Opdenacker wrote:
> Hi Jose,
>
> Thanks for your advice!
>
> On 1/13/22 6:37 PM, Jose Quaresma wrote:
> > Hi,
> >
> > I've seen the same for some time now when building core-image-minimal
> > with yocto state mirror and hashequiv servers.
> >
> > After some investigation I think the root cause is some
> > bandwidth/connection limitation on the http yocto mirror.
> >
> > Reducing the BB_NUMBER_THREADS="1" to a single core solves many of the
> > fetch issues for me,
> > my config is the default one with:
> >
> >   BB_NUMBER_THREADS="1"
> >   SSTATE_MIRRORS = "file://.*
> > http://sstate.yoctoproject.org/dev/PATH;downloadfilename=PATH
> > <http://sstate.yoctoproject.org/dev/PATH;downloadfilename=PATH>"
> >   BB_HASHSERVE_UPSTREAM = "typhoon.yocto.io:8687
> > <http://typhoon.yocto.io:8687>"
>
>
> Oops, it seems you're right. I have the same SSTATE_MIRRORS and
> BB_HASHSERVE_UPSTREAM settings as you do, and adding
> BB_NUMBER_THREADS="1" makes the errors disappear.
>
> It seems I should file a bug about that. The error messages just mention
> local paths, not remote ones, so it sounds like a local issue while it's
> apparently not.

That is useful to debug it but suggests there is an issue with concurrent
connections to the YP server.

I think we should have an open bug and get Michael Halstead's input on this.

Cheers,

Richard