Quantcast

[JIRA] (JENKINS-15697) 1.487: Automatic JNLP installation breaks Xserve OS X slaves

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15697) 1.487: Automatic JNLP installation breaks Xserve OS X slaves

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: Kohsuke Kawaguchi
Components: slave-setup
Created: 01/Nov/12 3:30 PM
Description:

Since 1.487, Jenkins apparently attempts to run a graphical JNLP installer on all OS X slaves. This is a bad idea because some OS X slaves (such as Xserve-based ones) will not let the jenkins user connect to a window manager, so starting the slave connection always fails.

A fix suggested by Kenny Ayers on the mailing list is to pass -Djava.awt.headless=true to the JVM, which works. But this should be a more readily accessible option in the slave settings UI - especially considering that this new behavior actively prevents previously working slaves from working.

(I would even argue that this behavior should not be the default, but as long as there's an option, I'm happy.)

Environment: Host: Arch Linux x86-64
Slave: OS X 10.8 x86-64
Project: Jenkins
Priority: Major Major
Reporter: Alex Rønne Petersen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15697) 1.487: Automatic JNLP installation breaks Xserve OS X slaves

JIRA noreply@jenkins-ci.org
aleksas commented on Bug JENKINS-15697

Same issue on mac 10.6.8 when running headless slave. Using jenkins v1.489.

Adding -Djava.awt.headless=true to slave launch command line fixed the issue.

Slave log prior to fix:
Java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
at hudson.remoting.Command.readFrom(Command.java:90)
at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Nov 7, 2012 11:19:16 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15697) 1.487: Automatic JNLP installation breaks Xserve OS X slaves

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Oliver Bock commented on Bug JENKINS-15697

Same here on all my OS X build slaves (all types of hardware and OS X versions). The proposed workaround does the trick for the time being...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15697) 1.487: Automatic JNLP installation breaks Xserve OS X slaves

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
Oliver Bock edited a comment on Bug JENKINS-15697

Same regression here on all my OS X build slaves (all types of hardware and OS X versions). The proposed workaround does the trick for the time being...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Loading...