From patchwork Wed Sep 21 05:45:14 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?b?5bCP5Y+j55Ci5aSrIC8gS09HVUNISe+8jFRBS1VP?= X-Patchwork-Id: 9342845 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id 7C28A607D0 for ; Wed, 21 Sep 2016 05:46:07 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 6DEE529F4D for ; Wed, 21 Sep 2016 05:46:07 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 618CA29F50; Wed, 21 Sep 2016 05:46:07 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=2.0 tests=BAYES_00, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 Received: from mail.linuxfoundation.org (mail.linuxfoundation.org [140.211.169.12]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id C62E829F4D for ; Wed, 21 Sep 2016 05:46:06 +0000 (UTC) Received: from mail.linux-foundation.org (localhost [127.0.0.1]) by mail.linuxfoundation.org (Postfix) with ESMTP id 0014F899; Wed, 21 Sep 2016 05:46:05 +0000 (UTC) X-Original-To: ltsi-dev@lists.linuxfoundation.org Delivered-To: ltsi-dev@mail.linuxfoundation.org Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 14845722; Wed, 21 Sep 2016 05:46:04 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail4.hitachi.co.jp (mail4.hitachi.co.jp [133.145.228.5]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1460C1DF; Wed, 21 Sep 2016 05:46:03 +0000 (UTC) Received: from mlsw2.hitachi.co.jp (unknown [133.144.234.166]) by mail4.hitachi.co.jp (Postfix) with ESMTP id A8B992CF4C8; Wed, 21 Sep 2016 14:46:01 +0900 (JST) Received: from mfilter2.hitachi.co.jp by mlsw2.hitachi.co.jp (8.13.8/8.13.8) id u8L5k1T1005614; Wed, 21 Sep 2016 14:46:01 +0900 Received: from vshuts01.hitachi.co.jp (vshuts01.hitachi.co.jp [10.201.6.83]) by mfilter2.hitachi.co.jp (Switch-3.3.4/Switch-3.3.4) with ESMTP id u8L5k09b007908; Wed, 21 Sep 2016 14:46:01 +0900 Received: from GSjpTKYDCehcs29.service.hitachi.net (unknown [158.212.188.199]) by vshuts01.hitachi.co.jp (Postfix) with ESMTP id 711CCF2039; Wed, 21 Sep 2016 14:46:00 +0900 (JST) Received: from GSJPTKYDCEMBX31.service.hitachi.net ([169.254.4.162]) by GSjpTKYDCehcs29.service.hitachi.net ([158.212.188.199]) with mapi id 14.03.0224.002; Wed, 21 Sep 2016 14:46:00 +0900 From: =?utf-8?B?5bCP5Y+j55Ci5aSrIC8gS09HVUNISe+8jFRBS1VP?= To: "'Kotaro HASHIMOTO'" , "'Bird, Timothy'" , "'Doug Crawford'" Thread-Topic: [!]Re: [LTSI-dev] Jenkins error Thread-Index: AQHSE6tojVaKOUTa2EmKxgCXxra8S6CCzV2AgACgxFA= Date: Wed, 21 Sep 2016 05:45:14 +0000 Deferred-Delivery: Wed, 21 Sep 2016 05:46:00 +0000 Message-ID: <390B4EACA1A32748BA6BC7F859F7D71655221555@GSjpTKYDCembx31.service.hitachi.net> References: <995787C2-ECB0-40C8-B304-81C8D01365CF@zonoff.com> <001b01d213c5$ca7b29c0$5f717d40$@ds.MitsubishiElectric.co.jp> In-Reply-To: <001b01d213c5$ca7b29c0$5f717d40$@ds.MitsubishiElectric.co.jp> Accept-Language: ja-JP, en-US Content-Language: ja-JP X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.198.219.41] MIME-Version: 1.0 X-TM-AS-GCONF: 00 Cc: "ltsi-dev@lists.linuxfoundation.org" , "fuego@lists.linuxfoundation.org" Subject: Re: [LTSI-dev] Jenkins error X-BeenThere: ltsi-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "A list to discuss patches, development, and other things related to the LTSI project" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ltsi-dev-bounces@lists.linuxfoundation.org Errors-To: ltsi-dev-bounces@lists.linuxfoundation.org X-Virus-Scanned: ClamAV using ClamSMTP I failed to send this mail to the mailing list. The second workaround is the same as Kotoro's. In addition, kernel command line option audit=0 is another workarround. https://github.com/tailhook/vagga/issues/71 -Takuo original mail to Doug --- Doug, I had the same issue. I did some search in the net and found it is not a problem of fuego itself. As far as I know there are two workarounds; 1) Rebuild and install libpam with --disable-audit option (in the container) or 2) Modify docker-create-container.sh to add --pid="host" option to docker create command diff --git a/fuego-host-scripts/docker-create-container.sh b/fuego-host-scripts/docker-create-container.sh index 2ea7961..24663d6 100755 Best regards, Takuo Koguchi -- > -----Original Message----- > From: ltsi-dev-bounces@lists.linuxfoundation.org > [mailto:ltsi-dev-bounces@lists.linuxfoundation.org] On Behalf Of Kotaro > HASHIMOTO > Sent: Wednesday, September 21, 2016 2:06 PM > To: 'Bird, Timothy'; 'Doug Crawford' > Cc: ltsi-dev@lists.linuxfoundation.org; fuego@lists.linuxfoundation.org > Subject: [!]Re: [LTSI-dev] Jenkins error > > Hi, > > I met same error on Ubuntu 14.04. > Then I modified docker-create-container.sh as the below and it works on my > environment. > > <> > ----- > [[before]] > CONTAINER_ID=`sudo docker create -it -v $DIR/../userdata:/userdata > --net="host" fuego` [[after]] CONTAINER_ID=`sudo docker create -it -v > $DIR/../userdata:/userdata --pid="host" --net="host" fuego` > ----- > > You can refer the below link also. > https://github.com/docker/docker/issues/5899 > > > Best regards, > Kotaro Hashimoto > > > -----Original Message----- > From: ltsi-dev-bounces@lists.linuxfoundation.org > [mailto:ltsi-dev-bounces@lists.linuxfoundation.org] On Behalf Of Bird, Timothy > Sent: Wednesday, September 21, 2016 10:57 AM > To: Doug Crawford > Cc: ltsi-dev@lists.linuxfoundation.org; fuego@lists.linuxfoundation.org > Subject: Re: [LTSI-dev] Jenkins error > > Sorry for the slow response. I've been out of the office the last few days. > > > -----Original Message----- > > From: ltsi-dev-bounces@lists.linuxfoundation.org [mailto:ltsi-dev- > > > On Ubuntu Trusty 14.04 on VirtualBox VM Updated Docker as per the > > Docker web instructions, getting version 1.12.1 Install.sh and docker > > create script ran without issue, start script had an error: > > Server: jenkinssu: System error failed! > > > > ---- > > vagrant@vagrant-ubuntu-trusty-64:/vagrant/dev/erik/jta-public/jta-host > > - > > scripts$ ls > > docker-build.sh docker-create-container.sh docker-start-container.sh > > vagrant@vagrant-ubuntu-trusty-64:/vagrant/dev/erik/jta-public/jta-host > > - scripts$ sudo ./docker-create-container.sh Created JTA container > > 6a420f901af7847f2afa3100d3fb3852b71bc65f92aecd13a9aefe0823d42b77 > > vagrant@vagrant-ubuntu-trusty-64:/vagrant/dev/erik/jta-public/jta-host > > - scripts$ sudo ./docker-start-container.sh Starting JTA container > > 6a420f901af7847f2afa3100d3fb3852b71bc65f92aecd13a9aefe0823d42b77 > > [....] Starting Jenkins Continuous Integration Server: jenkinssu: > > System error failed! > > [ ok ] Starting OpenBSD Secure Shell server: sshd. > > [ ok ] Starting network benchmark server. > > eth0 Link encap:Ethernet HWaddr 08:00:27:f2:f2:d9 > > inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0 > > inet6 addr: fe80::a00:27ff:fef2:f2d9/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:1927624 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:345482 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:2746559839 (2.5 GiB) TX bytes:23097565 (22.0 MiB) > > > > /var/lib/jenkins/config.xml is a symlink - everything is OK. > > Setting up watches. > > Watches established. > > — > > > > Am I doing something wrong? > > Not that I can see. Can you please do the following: > > Start the container, using the docker-start-container.sh script (like you are doing). > Once "inside" the container, edit /etc/init.d/jenkins and add the line: "set -x" > somewhere near the top of the file (for example, right before the PATH=... line). > > Then exit the shell (terminating the container), and start it again using > docker-start-container.sh > > Then please send the output to this list. The output from /etc/init.d/jenkins should > look something like the following... > + PATH=/bin:/usr/bin:/sbin:/usr/sbin > + DESC='Jenkins Continuous Integration Server' > + NAME=Jenkins > ... > I assume the message is coming from the $SU command inside this script (in the > do_start function), but I'd like to verify that. > > If the 'su' command is having the problem, we may need to strace it to see what > the issue is, but that will be tricky since strace is not put into the container by > default. (But it's not hard to add stuff to the Dockerfile to add additional Debian > packages to the container image.) > > I'm not sure what would be causing the system error. > > FWIW, I'm running fuego (jta renamed) on Ubuntu 14.04.05 (Trusty Tahr), with > docker version 1.12.0, so the environment should be very similar. > -- Tim > > > > > _______________________________________________ > LTSI-dev mailing list > LTSI-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/ltsi-dev > > _______________________________________________ > LTSI-dev mailing list > LTSI-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/ltsi-dev --- a/fuego-host-scripts/docker-create-container.sh +++ b/fuego-host-scripts/docker-create-container.sh @@ -7,7 +7,7 @@ while [ -h "$SOURCE" ]; do # resolve $SOURCE until the file is no longer a symli done DIR="$( cd -P "$( dirname "$SOURCE" )" && pwd )" -CONTAINER_ID=`sudo docker create -it -v $DIR/../userdata:/userdata --net="host" fuego` +CONTAINER_ID=`sudo docker create -it -v $DIR/../userdata:/userdata +--pid="host " --net="host" fuego` CONTAINER_ID_FILE="$DIR/../last_fuego_container.id" echo "Created Fuego container $CONTAINER_ID" echo $CONTAINER_ID > $DIR/../last_fuego_container.id Actually I have not tried the first one and do not know if there is any side effects for the second.