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 <[email protected]>

> On Tue, Oct 1, 2013 at 9:30 AM, Raouf <[email protected]> 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
>      [email protected]
>
> --
> 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
> [email protected].
> 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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to