Bug 6301 - nightly-world build hangs on AB machine having OpenSuse 13.1
Summary: nightly-world build hangs on AB machine having OpenSuse 13.1
Status: RESOLVED FIXED
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.7
Assignee: Beth Flanagan
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-05-09 08:28 UTC by Ionut Chisanovici
Modified: 2014-09-09 19:23 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
twistd.log (224.32 KB, text/x-log)
2014-05-09 08:28 UTC, Ionut Chisanovici
no flags Details
auto.conf (526 bytes, application/octet-stream)
2014-05-09 08:29 UTC, Ionut Chisanovici
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ionut Chisanovici 2014-05-09 08:28:47 UTC
Created attachment 1937 [details]
twistd.log

Hi,

On our OpenSuse 13.1 AB machine, the nightly-world build for the 1.5.2 RC3 hangs.
I'm seeing the the yocto-slave/twistd.log a lots of 'broker, client' timeouts.
Attached the twistd.log, and auto.conf.
I have to mention that all the other builds finished successfully (buildtools, nightly-arm, nightly-x86, nightly-multilib, nightly-x86-64-lsb and so on). Also, the nightly-world builds on our Ubuntu 13.10, Fedora 20 and CentOS AB machines were ok.
More, if I do a ps | grep python, I see two python defuncts processes.

Branch for the build is: dora
Commit: 6a92f7ede3be3edd58d7819aa611b0c5270756bf

Cheers,
Ionut C
Comment 1 Ionut Chisanovici 2014-05-09 08:29:10 UTC
Created attachment 1938 [details]
auto.conf
Comment 2 Ionut Chisanovici 2014-05-09 08:31:58 UTC
Forgot to mention that if I start the build manually from the command line, the build is working.

Cheers,
Ionut C
Comment 3 Richard Purdie 2014-05-15 14:45:27 UTC
Initially I wondered if http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ffa8bbf96524c18d40a18334d5f05f3d27737466 was an issue but I believe that one only triggered in LSB configurations. Are there specific default security flags on that distro?
Comment 4 Ionut Chisanovici 2014-07-08 09:15:28 UTC
Within the poky conf file there were no security flags enables.
As far for the OS, there is an OpenSuse 13.1 and I really don't know if there are packages compiled with sec flags.

Cheers,
Ionut C
Comment 5 Beth Flanagan 2014-09-09 19:23:43 UTC
We haven't seen this for a while, so I'm marking it as resolved.