From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga05.intel.com ([192.55.52.89] helo=fmsmga101.fm.intel.com) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SHHWJ-0003vf-TD for openembedded-core@lists.openembedded.org; Mon, 09 Apr 2012 18:32:48 +0200 Received: from mail-pz0-f44.google.com ([209.85.210.44]) by mga01.intel.com with ESMTP/TLS/RC4-SHA; 09 Apr 2012 09:23:29 -0700 Received: by dadz14 with SMTP id z14so18656380dad.17 for ; Mon, 09 Apr 2012 09:23:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=I+5vBjHHUeLtIEwsDtpSWdElX4wsdE0aoXCRnnaUHrA=; b=OIX/Cqm7/+sWG8AraJCbZ+Gl0tqbtiAefe+LiVwZXWlqU3nWuB3p6yZhbIbuBhJ7BS BBgmI09OU5HNjezBuYl83qyt78wHNlt4dIDMs/e3gwScWnFNu+lDP93cvGu2nwzzsFTr yOlxciquYr4chlTTzojyB8J0bs9zOQOBS8zMMx86A3NIgQqsFcLITja5PYiWgTo/NH+8 UHgbza9TzNgVPjwrz8m6lZxhhFSUAI/wjRHsE6OLVvSU++Kw+kQ+PMm4XSFgdeuqShCX Qjlub7NL4uOAcn4eDsFAR3OJKIiOiZ8hzZaNwAB2t3iOJBWv+kJm4jLeZxKZlxm7Qd/y +olg== Received: by 10.68.194.198 with SMTP id hy6mr21303372pbc.0.1333988609558; Mon, 09 Apr 2012 09:23:29 -0700 (PDT) Received: from [10.1.10.192] (c-50-137-42-92.hsd1.or.comcast.net. [50.137.42.92]) by mx.google.com with ESMTPS id ng1sm492634pbc.68.2012.04.09.09.23.27 (version=SSLv3 cipher=OTHER); Mon, 09 Apr 2012 09:23:28 -0700 (PDT) Message-ID: <4F830CFE.8050703@intel.com> Date: Mon, 09 Apr 2012 09:23:26 -0700 From: Scott Garman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1 MIME-Version: 1.0 To: Saul Wold References: <4F80D4EF.8090704@linux.intel.com> <4F826CEE.9040107@intel.com> <4F830078.9020403@linux.intel.com> In-Reply-To: <4F830078.9020403@linux.intel.com> X-Gm-Message-State: ALoCoQm8MqcRcP/jr1fhn2YQOhPQVPRm65NZ5i3LPgsDdCcYOPjpcx0kEkf2ICutHXanbeIlN91f Cc: Patches and discussions about the oe-core layer Subject: Re: [PATCH 0/1] shadow-native: disable logging to syslog X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 16:32:48 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 04/09/2012 08:30 AM, Saul Wold wrote: > On 04/08/2012 10:00 PM, Scott Garman wrote: >> On 04/07/2012 04:59 PM, Saul Wold wrote: >>> On 04/05/2012 11:53 PM, Scott Garman wrote: >>>> Hello, >>>> >>>> This pull request includes a patch to shadow to disable logging to >>>> syslog, to prevent sysroot user and group additions from writing >>>> entries to the host's syslog. >>>> >>>> I have build-tested this with core-image-sato (which builds a few >>>> useradd-based recipes, such as avahi and dbus) for all 5 of our >>>> qemu architectures, while watching my syslog to verify that no >>>> useradd or groupadd entries were written. >>>> >>> >>> With this patch applied, the following error was seen on the AB: >>> >>> | Running useradd commands... >>> | WARNING: useradd command did not succeed. Retrying... >>> | WARNING: useradd command did not succeed. Retrying... >>> | WARNING: useradd command did not succeed. Retrying... >>> | WARNING: useradd command did not succeed. Retrying... >>> | WARNING: useradd command did not succeed. Retrying... >>> | WARNING: useradd command did not succeed. Retrying... >>> | WARNING: useradd command did not succeed. Retrying... >>> | WARNING: useradd command did not succeed. Retrying... >>> | WARNING: useradd command did not succeed. Retrying... >>> | WARNING: useradd command did not succeed. Retrying... >>> | ERROR: tried running useradd command 10 times without success, >>> giving up >>> >>> Check the AB here: >>> >>> http://autobuilder.yoctoproject.org:8010/builders/nightly-arm/builds/369/steps/shell_19/logs/stdio >>> >>> >> >> Hi Saul, >> >> The syslog disable patch cannot trigger this error, I'm pretty certain >> you have encountered another problem. >> >> The useradd class now uses code which checks that the user account or >> group account was created in the passwd and group files, respectively. >> If the account was not created (which is verified via a grep command), >> the script sleeps for 1 second and tries again, up to 10 times. This is >> intended to avoid lockfile races, as useradd and groupadd lock the >> passwd and group files when creating accounts. >> >> It seems extremely unlikely that the passwd file was locked for a full >> 10s worth of attempts to access it. I also see from the logs that the >> base-passwd package was installed before this error was encountered, >> which *should* rule out the possibility that the useradd command was >> failing because /etc/passwd didn't exist yet. >> >> Later useradd commands are also failing in this manner, which makes me >> suspect that something is wrong with the /etc/passwd file in this image. >> The groupadd commands, on the other hand, are succeeding without any >> retries. >> >> So it would be helpful for me to know answers to the following: >> >> Was this a build from scratch or from sstate? >> > This was from sstate. > >> Is this problem reproducible? (I'm starting a build from scratch >> overnight on my end) >> > Only saw it on one build over the weekend, but turns out a bug already > existed with this issue, but it was filed as a PAM build failure (see > 2218) , which maybe I need to re-assign to you. Yes, I've re-assigned this bug to myself. >> What does the etc/passwd file in this image look like? >> > You can get it from the AB yourself, correct? If not, let me know please. This was a nightly build and it no longer appears to be on the server - assuming I'm connected to the correct one? Scott -- Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center