Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Received-SPF: neutral (athena.apache.org: local policy)
References: <236394550.9984.1410735492600.JavaMail.jenkins@crius>
 <1410761480.20530.YahooMailNeo@web28905.mail.ir2.yahoo.com>
 <BE61E4A4-7C15-4700-8D82-19FC75C8EED6@16degrees.com.au>
 <CAPbPdOaZkct0Z3g=Obw27+q32R0N2mZUOCUSZcn6SucfVhwxag@mail.gmail.com>
Message-ID: <1410797065.6728.YahooMailNeo@web28901.mail.ir2.yahoo.com>
Date: Mon, 15 Sep 2014 17:04:25 +0100
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: Re: plz restart Jenkins
To: Andrew Bayer <andrew.bayer@gmail.com>,
  "builds@apache.org" <builds@apache.org>
Cc: "infra@apache.org" <infra@apache.org>
In-Reply-To: 
 <CAPbPdOaZkct0Z3g=Obw27+q32R0N2mZUOCUSZcn6SucfVhwxag@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="542325855-2771561-1410797065=:6728"

--542325855-2771561-1410797065=:6728
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Gav and Andrew!=0A=0ASorry for using the wrong list and txs for taking c=
are (as always)!=0A=0ALieGrue,=0Astrub=0A=0A=0A=0AOn Monday, 15 September 2=
014, 18:01, Andrew Bayer <andrew.bayer@gmail.com> wrote:=0A =0A=0A>=0A>=0A>=
I think the problem here was=0A>https://issues.jenkins-ci.org/browse/JENKIN=
S-22641 - Jenkins not=0A>cleaning up after itself. I've backported the fix =
to our Jenkins and=0A>restarted it. I'll watch to see how things look.=0A>=
=0A>A.=0A>=0A>=0A>On Mon, Sep 15, 2014 at 1:53 AM, Gavin McDonald <gavin@16=
degrees.com.au> wrote:=0A>> Please direct any build related queries to the =
builds@ mailing list.=0A>>=0A>> I had a look, 'Jenkins' consists of one mas=
ter and lots of slaves.=0A>> The Master is fine and did not need a restart.=
 The error message indicated=0A>> that the slave it was running on was the =
problem, in this case H10.=0A>>=0A>> I looked and both the H10 and H11 slav=
es were running 4 concurrent builds=0A>> at the time of the failures. Other=
 projects running on H10 also had the same=0A>> failures.=0A>>=0A>> I reduc=
ed the executors to run max 2 executors and this has helped.=0A>>=0A>> Than=
ks=0A>>=0A>> Gav=E2=80=A6=0A>>=0A>>=0A>>=0A>> On 15/09/2014, at 7:11 AM, Ma=
rk Struberg <struberg@yahoo.de> wrote:=0A>>=0A>>> Jenkins seems to be out o=
f memory=0A>>>=0A>>>=0A>>> On Monday, 15 September 2014, 0:58, Apache Jenki=
ns Server <jenkins@builds.apache.org> wrote:=0A>>>=0A>>>=0A>>> See <https:/=
/builds.apache.org/job/OpenWebBeans-trunk/1031/changes>=0A>>>=0A>>> Changes=
:=0A>>> ...=0A>>> [trunk] $ /home/jenkins/tools/java/latest1.6/bin/java -cp=
 /home/jenkins/jenkins-slave/maven-agent.jar:/home/jenkins/jenkins-slave/cl=
assworlds.jar hudson.maven.agent.Main /home/jenkins/tools/maven/apache-mave=
n-2.2.1 /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/m=
aven-interceptor.jar 39938 /home/jenkins/jenkins-slave/maven2.1-interceptor=
.jar=0A>>> #=0A>>> # There is insufficient memory for the Java Runtime Envi=
ronment to continue.=0A>>> # Cannot create GC thread. Out of system resourc=
es.=0A>>> # An error report file with more information is saved as:=0A>>> #=
 <https://builds.apache.org/job/OpenWebBeans-trunk/ws/trunk/hs_err_pid6437.=
log>=0A>>> [locks-and-latches] Releasing all the locks=0A>>> [locks-and-lat=
ches] All the locks released=0A>>> ERROR: Failed to launch Maven. Exit code=
 =3D 1=0A>>>=0A>>>=0A>>>=0A>>=0A>=0A>
--542325855-2771561-1410797065=:6728--