All of lore.kernel.org
 help / color / mirror / Atom feed
* Checking sstate mirror is hanging at 100%
@ 2017-10-30  5:54 Vineeth Karumanchi
  2017-10-30  9:37 ` Alexander Kanavin
  0 siblings, 1 reply; 7+ messages in thread
From: Vineeth Karumanchi @ 2017-10-30  5:54 UTC (permalink / raw)
  To: yocto

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

Hi All,

I am running sstate mirrors on a web server. My network has proxy, 
sstate is sharing well with proxies, .

But, without proxies, bitbake is hanging at "/Checking sstate mirror 
object #######100%/".  Is there a way to change timeout of sstate mirror 
checking.

I did some debugging with "-DD" and I see bitbake is trying to fetch the 
sstate objects, failing and keep on re-trying.


/DEBUG: checkstatus: trying again/


In this case i would expect bitbake to "check for sstate mirrors" for 
some time and rebuild from scratch. Is there any approach to over come 
this ?


Thanks in Advance

Vineeth


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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Checking sstate mirror is hanging at 100%
  2017-10-30  5:54 Checking sstate mirror is hanging at 100% Vineeth Karumanchi
@ 2017-10-30  9:37 ` Alexander Kanavin
  2017-10-30 19:49   ` Andre McCurdy
  0 siblings, 1 reply; 7+ messages in thread
From: Alexander Kanavin @ 2017-10-30  9:37 UTC (permalink / raw)
  To: Vineeth Karumanchi, yocto

On 10/30/2017 07:54 AM, Vineeth Karumanchi wrote:

> In this case i would expect bitbake to "check for sstate mirrors" for 
> some time and rebuild from scratch. Is there any approach to over come 
> this ?

The approach is to fix your infrastructure so that fetching from network 
doesn't fail. We've gotten a similar request recently for enabling 'soft 
sstate cache failure', and RP is firmly against it:

http://lists.openembedded.org/pipermail/openembedded-core/2017-August/141593.html

Alex


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Checking sstate mirror is hanging at 100%
  2017-10-30  9:37 ` Alexander Kanavin
@ 2017-10-30 19:49   ` Andre McCurdy
  2017-10-31  3:52     ` Vineeth Karumanchi
  0 siblings, 1 reply; 7+ messages in thread
From: Andre McCurdy @ 2017-10-30 19:49 UTC (permalink / raw)
  To: Alexander Kanavin; +Cc: Yocto discussion list, Vineeth Karumanchi

On Mon, Oct 30, 2017 at 2:37 AM, Alexander Kanavin
<alexander.kanavin@linux.intel.com> wrote:
> On 10/30/2017 07:54 AM, Vineeth Karumanchi wrote:
>
>> In this case i would expect bitbake to "check for sstate mirrors" for some
>> time and rebuild from scratch. Is there any approach to over come this ?
>
> The approach is to fix your infrastructure so that fetching from network
> doesn't fail. We've gotten a similar request recently for enabling 'soft
> sstate cache failure', and RP is firmly against it:
>
> http://lists.openembedded.org/pipermail/openembedded-core/2017-August/141593.html

It looks like the logic in the wget fetcher retries once, so if it's
getting stuck then that seems like a genuine bug.

Vineeth, are you sure it's really continuously retrying? Or are you
just seeing timeouts for many fetches (which will eventually
complete)? Note that you can reduce the wget timeout by setting your
own value for "FETCHCMD_wget". See bitbake/lib/bb/fetch2/wget.py for
the default value - use that as a starting point for your
modification.


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Checking sstate mirror is hanging at 100%
  2017-10-30 19:49   ` Andre McCurdy
@ 2017-10-31  3:52     ` Vineeth Karumanchi
  2017-10-31 18:41       ` Andre McCurdy
  0 siblings, 1 reply; 7+ messages in thread
From: Vineeth Karumanchi @ 2017-10-31  3:52 UTC (permalink / raw)
  To: Andre McCurdy, Alexander Kanavin; +Cc: Yocto discussion list


> From: Andre McCurdy [mailto:armccurdy@gmail.com]
> Sent: Tuesday, October 31, 2017 1:19 AM
> To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> Cc: Vineeth Karumanchi <VINEETHC@xilinx.com>; Yocto discussion list
> <yocto@yoctoproject.org>
> Subject: Re: [yocto] [Yocto] Checking sstate mirror is hanging at 100%
> 
> On Mon, Oct 30, 2017 at 2:37 AM, Alexander Kanavin
> <alexander.kanavin@linux.intel.com> wrote:
> > On 10/30/2017 07:54 AM, Vineeth Karumanchi wrote:
> >
> >> In this case i would expect bitbake to "check for sstate mirrors" for
> >> some time and rebuild from scratch. Is there any approach to over come
> this ?
> >
> > The approach is to fix your infrastructure so that fetching from
> > network doesn't fail. We've gotten a similar request recently for
> > enabling 'soft sstate cache failure', and RP is firmly against it:
> >
> > http://lists.openembedded.org/pipermail/openembedded-core/2017-
> August/
> > 141593.html
> 
> It looks like the logic in the wget fetcher retries once, so if it's getting stuck
> then that seems like a genuine bug.
> 
> Vineeth, are you sure it's really continuously retrying? 
Yes, I see continuous retry of wget of same sstate files.
With -DD I see the below messages  for every try:

DEBUG: checkstatus: trying again
DEBUG: checkstatus: trying again
DEBUG: checkstatus: trying again
DEBUG: checkstatus: trying again
DEBUG: checkstatus: trying again

>Or are you just seeing
> timeouts for many fetches (which will eventually complete)? Note that you
> can reduce the wget timeout by setting your own value for
> "FETCHCMD_wget". See bitbake/lib/bb/fetch2/wget.py for the default value
> - use that as a starting point for your modification.

No fetch failure error, Just hanging at 100%.

I did some more analysis:
My network needs proxy to access any site.

To validate a URL, bitbake/lib/bb/fetch2/__init__.py:  urllib.parse.urlparse(uri) and checking for netloc.
This is returning true without proxy being set, but the same uri is not establishing connection without proxies.

bitbake is thinking it as a valid  and keep retrying without any errors.

Thanks
Vineeth






^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Checking sstate mirror is hanging at 100%
  2017-10-31  3:52     ` Vineeth Karumanchi
@ 2017-10-31 18:41       ` Andre McCurdy
  2017-11-01  3:58         ` Vineeth Karumanchi
  2017-11-01 14:47         ` Vineeth Chowdary Karumanchi
  0 siblings, 2 replies; 7+ messages in thread
From: Andre McCurdy @ 2017-10-31 18:41 UTC (permalink / raw)
  To: Vineeth Karumanchi; +Cc: Yocto discussion list

>>
>> It looks like the logic in the wget fetcher retries once, so if it's getting stuck
>> then that seems like a genuine bug.
>>
>> Vineeth, are you sure it's really continuously retrying?
> Yes, I see continuous retry of wget of same sstate files.

The fetcher explicitly tries to avoid that by retrying each file only
once. See retry logic in:

  http://git.openembedded.org/bitbake/commit/?id=54b1961551511948e0cbd2ac39f19b39b9cee568

However, there is a later commit which may also be related:

  http://git.openembedded.org/bitbake/commit/?id=6fa07752bbd3ac345cd8617da49a70e0b2dd565f

Does the version of bitbake which you are using contain both commits?


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Checking sstate mirror is hanging at 100%
  2017-10-31 18:41       ` Andre McCurdy
@ 2017-11-01  3:58         ` Vineeth Karumanchi
  2017-11-01 14:47         ` Vineeth Chowdary Karumanchi
  1 sibling, 0 replies; 7+ messages in thread
From: Vineeth Karumanchi @ 2017-11-01  3:58 UTC (permalink / raw)
  To: Andre McCurdy; +Cc: Yocto discussion list



On 11/1/2017 12:11 AM, Andre McCurdy wrote:
>>> It looks like the logic in the wget fetcher retries once, so if it's getting stuck
>>> then that seems like a genuine bug.
>>>
>>> Vineeth, are you sure it's really continuously retrying?
>> Yes, I see continuous retry of wget of same sstate files.
> The fetcher explicitly tries to avoid that by retrying each file only
> once. See retry logic in:
>
>    http://git.openembedded.org/bitbake/commit/?id=54b1961551511948e0cbd2ac39f19b39b9cee568
>
> However, there is a later commit which may also be related:
>
>    http://git.openembedded.org/bitbake/commit/?id=6fa07752bbd3ac345cd8617da49a70e0b2dd565f
>
> Does the version of bitbake which you are using contain both commits?

Thanks Andre
I am not having later patch. I will check the issue with master branch




^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Checking sstate mirror is hanging at 100%
  2017-10-31 18:41       ` Andre McCurdy
  2017-11-01  3:58         ` Vineeth Karumanchi
@ 2017-11-01 14:47         ` Vineeth Chowdary Karumanchi
  1 sibling, 0 replies; 7+ messages in thread
From: Vineeth Chowdary Karumanchi @ 2017-11-01 14:47 UTC (permalink / raw)
  To: Andre McCurdy; +Cc: Yocto discussion list



On 11/1/2017 12:11 AM, Andre McCurdy wrote:

> The fetcher explicitly tries to avoid that by retrying each file only
> once. See retry logic in:
> 
>    http://git.openembedded.org/bitbake/commit/?id=54b1961551511948e0cbd2ac39f19b39b9cee568
> 
> However, there is a later commit which may also be related:
> 
>    http://git.openembedded.org/bitbake/commit/?id=6fa07752bbd3ac345cd8617da49a70e0b2dd565f
I didnt have this patch, presently i am on morty branch. I will check 
with master branch

Thanks for the info
Vineeth
> 
> Does the version of bitbake which you are using contain both commits?
> 


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2017-11-01 15:02 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-10-30  5:54 Checking sstate mirror is hanging at 100% Vineeth Karumanchi
2017-10-30  9:37 ` Alexander Kanavin
2017-10-30 19:49   ` Andre McCurdy
2017-10-31  3:52     ` Vineeth Karumanchi
2017-10-31 18:41       ` Andre McCurdy
2017-11-01  3:58         ` Vineeth Karumanchi
2017-11-01 14:47         ` Vineeth Chowdary Karumanchi

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.