Am 14.07.2014 17:20, schrieb Stephen Connolly: > On 14 July 2014 16:14, martin flehmig <[email protected]> wrote: > >>> Start with the creation of the slave VM from ISO and give the MD5 of the >>> ISO you use. >> What do you mean by this? The slave node is not a VM. >>> >>> I have tried reproducing various test cases from Jenkins and the way I >> set >>> up by ISOs and install Java on them does not seem to replicate the issue. >>> >>> i.e. I have customers using CentOS 6.5 who have the issue, yet when I >>> replicate their exact plugin configuration and slave config.xml on a >> CentOS >>> 6.5 VM that I installed myself and setup Java myself on... no problem... >>> but they have a problem. >>> >>> So I can only assume that the way I setup Java on e.g. CentOS or Ubuntu >> is >>> somehow different from the way they do it and hence the issues they >> observe! >> >> I installed Jenkins following this instruction >> https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu >> on Linux Mint 15 system and on Ubunut 12.04.4. >> The slave nodes are running SLES 11 SP1. >> > > And how did you install Java on the slaves/master? > > How you install jenkins is not the issue... the issue is how Java gets > installed from what I can tell, as when we dig deep into the logging > messages it seems to be the 64-bit and 32-bit libs getting mixed up when > Java on the slave is calling into GLIBC via JNR > Ah, okay. I will ask the admins...
But as I described, userB can see and use credentials of userA when configuring nodeB. For me it seams to not matter what slave node it is and how Java was installed. Thanks, martin > >> >> Thanks, >> martin >> >> > -- Martin Flehmig Technische Universität Dresden Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH) Zellescher Weg 12, 01062 Dresden WIL A103 Tel. +49 351 463 42303 Fax. +49 351 463 37773 Email: [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
