This behaviour started about 1-2 weeks ago, we are running nightly builds and we noticed that they started to hang. Interestingly enough, it often happens happens during "package-index", so its not a source fetcher problem: ps auxww | grep bitbake oebuild 26788 0.0 0.3 222340 122820 ? S 03:38 0:04 /opt/poky/2.0/sysroots/x86_64-pokysdk-linux/usr/bin/python2.7 /oe/dss-oe/yocto/feedconfig/devel/poky/bitbake/bin/bitbake -DDD package-index oebuild 26803 0.0 0.6 377292 196464 ? Sl 03:38 0:03 /opt/poky/2.0/sysroots/x86_64-pokysdk-linux/usr/bin/python2.7 /oe/dss-oe/yocto/feedconfig/devel/poky/bitbake/bin/bitbake -DDD package-index oebuild 26805 0.0 0.3 298224 119308 ? Sl 03:38 0:11 /opt/poky/2.0/sysroots/x86_64-pokysdk-linux/usr/bin/python2.7 /oe/dss-oe/yocto/feedconfig/devel/poky/bitbake/bin/bitbake -DDD package-index There is no timeout, it will stay in this state for days. netstat -t -W shows: tcp 0 0 CentOS-70-64-minimal:39783 yocto-www.yoctoproject.org:https ESTABLISHED I added -DDD to my build script and now I can see where it actually hangs, the last entry is: DEBUG: Testing URL http://bugzilla.yoctoproject.org/report.cgi At this very moment bitbake still hangs, at the same time the URL can be opened in a browser. I now killed bitbake (had to use -9) and restarted the build and it works again, but it is failing very consistently every night (the build is started at 3:30 A.M. CEST I also had a couple of cases where it was also hanging when I manually restarted the build, I can not trace it to any network outages or similar. In any case there should be a timeout. I am building poky 2.0.1: BB_VERSION = "1.28.0" DISTRO = "poky" DISTRO_VERSION = "2.0.1"
Lowering importance since there turned out to be a workaround CONNECTIVITY_CHECK_URIS=""
Sometimes networks and connections are just plain flakey. There was a commit on master back in January (423a2645377bff2cd7292e1dc9796eeb3595e937) that replaced CONNECTIVITY_CHECK_URIS in meta-yocto/conf/distro/poky.conf with just "https://www.example.com/". You might try that and see if it solves your problem.
There's a series in review for jethro which includes backporting 423a2645377bff2cd7292e1dc9796eeb3595e937
Patch backported to jethro: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=jethro&id=16d64def97154d76fc1134ecd6cf9d704621e689