Re: Can't launch 2 slaves (having two different masters) on the same machine
when not specified, jenkins seems to use an account called anonymous to communicate with slaves What's the problem with using the same file system ? can you explain please ? ps: i'd like to remind you that it was working pretty well under 1.456, so what has changed since then ? 2013/10/3 Les Mikesell lesmikes...@gmail.com On Thu, Oct 3, 2013 at 9:32 AM, Raouf abdelhamid.ra...@gmail.com wrote: By the way, i also noticed when using the built in ssh plugin, the slaves are launched by the anonymous account even if i created them with a specific admin user. What is an anonymous account? And are you trying to run in the same FS root? I wouldn't expect that to work at all, at least not concurrently. -- Les Mikesell lesmikes...@gmail.com -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/sP31OAOj9k0/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't launch 2 slaves (having two different masters) on the same machine
Actually i did try it and it worked well. But i don't know exactly wich
slave jar was lanched, and i can't just abandon the scripts since they're
doing some other stuff (logging, restarting on fail ...etc.)
2013/10/1 Les Mikesell lesmikes...@gmail.com
On Tue, Oct 1, 2013 at 9:30 AM, Raouf abdelhamid.ra...@gmail.com wrote:
Hi everybody,
Ii'm using two servers, one for jenkins master, and one for the slave
instance
I'm using Jenkins 1.456 as a main stream version, and was trying to
prepare
an upgrade to 1.518, so i just installed another jenkins master for
testing
puropose, and defined different ports for each one (the main master and
the
test master)
then i added a slave node to the test-master, and i had already a slave
node
for the main master.
i launch each slave by calling a script through ssh, something like
ssh me@my-slaves-server '/home/me/ slave_test.ksh start'
and the script is calling slaves that way
nohup /.../JAVA-6/bin/java -Xms512m -Xmx1024m -Djava.io.tmpdir=/tmp -jar
/.../hudson_slave/jar/${HUDSON_VERSION}/slave.jar -jnlpUrl
http://
${MASTER_HOST}:${MASTER_PORT}/computer/${SLAVE_HOST}/slave-agent.jnlp
The problem is, each time i launch the test-slave the main-slave goes
offline and i have this stack trace
ERROR: Unable to launch the slave agent for my-slaves-server
java.io.EOFException: unexpected stream termination
at hudson.remoting.Channel.init(Channel.java:408)
at hudson.remoting.Channel.init(Channel.java:366)
at hudson.remoting.Channel.init(Channel.java:327)
at hudson.remoting.Channel.init(Channel.java:323)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:313)
at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Any ideas about this issue ?
What happens if you use the built-in ssh support instead of your own
script? And for testing, I'd start the slave as a different user for
the 2nd instance.
--
Les Mikesell
lesmikes...@gmail.com
--
You received this message because you are subscribed to a topic in the
Google Groups Jenkins Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-users/sP31OAOj9k0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: strange heap space
Many thanks ! that solved my problem. I was actually using the default HTTP wagon, so i moved to DAV wagon and now everythings is working fine. Thanks to everyone for your help. Regards, Raouf. 2013/7/19 Vincent Latombe vincent.lato...@gmail.com Hi, See [1] for a possible workaround (this is the one I use). Basically when using maven 3, you just have to prefix your deployment url with dav: (ex. dav:http://yourmavenserver). It will use the dav wagon instead of the default http one, which has the bad habbit of loading the full file in memory before sending it away. HTH, Vincent |1] http://maven.40175.n5.nabble.com/Heap-overflow-in-deploy-deploy-td3211324.html Vincent 2013/7/19 Raouf Abdelhamid abdelhamid.ra...@gmail.com: Okay thanks guys, i'll check the activity of maven-deploy and give you some feedback 2013/7/19 Daniel Beck m...@beckweb.net IIRC a few years ago I experienced an issue with very large artifacts being uploaded to an artifact repository. maven-deploy-plugin couldn't handle files larger than one third of the available heap space. On 19.07.2013, at 12:09, Raouf abdelhamid.ra...@gmail.com wrote: Hi there, I'm getting a java heap space that i can't really explain. i tried to increase the memory allocated to jenkins, but that doesn't change a thing The most strange thing, is that i configured jenkins to not launch sonar analysis if the build fails, but sonar analysis is launched anyway, goes sucessful, and then the build is red ! I even tryied to montir the execution of this build with visual VM remotely connected to jenkins, but didn't see any heap space error at any moment. here's the corresponding log Uploading: http://server/archiva/repository/snapshot/project-SNAPSHOT/project-SNAPSHOT-bin.tar.gz [JENKINS] Archiving /basepath/hudson/workspace/ project/package/pom.xml to /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/module-version- SNAPSHOT.pom [JENKINS] Archiving /basepath/hudson/workspace/ project/package/targetproject-version-SNAPSHOT.jar to /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/project-version- SNAPSHOT.jar [JENKINS] Archiving /basepath/hudson/workspace/ project/package/target/project-version-SNAPSHOT-bin.tar.gz to /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/project-version- SNAPSHOT-bin.tar.gz [INFO] -- -- [ERROR] FATAL ERROR [INFO] [INFO] Java heap space [INFO] -- -- [INFO] Trace java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf( Arrays.java:2786) at java.io.ByteArrayOutputStream. write(ByteArrayOutputStream. java:94) at sun.net.www.http. PosterOutputStream.write( PosterOutputStream.java:61) at org.apache.maven.wagon. AbstractWagon.transfer( AbstractWagon.java:338) at org.apache.maven.wagon. AbstractWagon.transfer( AbstractWagon.java:305) at org.apache.maven.wagon. AbstractWagon.transfer( AbstractWagon.java:267) at org.apache.maven.wagon. AbstractWagon.putTransfer( AbstractWagon.java:238) at org.apache.maven.wagon. StreamWagon.put(StreamWagon. java:143) at org.apache.maven.wagon. providers.http.LightweightHttpWagon.put( LightweightHttpWagon.java:148) at org.apache.maven.artifact. manager.DefaultWagonManager.putRemoteFile( DefaultWagonManager.java:244) at org.apache.maven.artifact. manager.DefaultWagonManager.putArtifact( DefaultWagonManager.java:160) at org.apache.maven.artifact. deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java: 80) at org.apache.maven.plugin. deploy.DeployMojo.execute( DeployMojo.java:169) at org.apache.maven.plugin. DefaultPluginManager.executeMojo( DefaultPluginManager.java:451) at hudson.maven.agent. PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java: 182) at org.apache.maven.lifecycle. DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 558) at org.apache.maven.lifecycle. DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java: 499) at org.apache.maven.lifecycle. DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 478) at org.apache.maven.lifecycle. DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java: 330
