I have the same issue after upgrading from 1.480.1 to 1.480.2 on Ubuntu 12.04. I am able to launch the windows slaves manually, but unable to have them run as a windows service from the gui. I am able to install it as a service from the command line, but the master never connects to the slave. The only hint I have is if I try to run the command for a headless slave, then I get
java.io.IOException: Failed to load http://jenkins/computer/server-bld-pc1/slave-agent.jnlp: 403 Forbidden at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:238) at hudson.remoting.Launcher.run(Launcher.java:200) at hudson.remoting.Launcher.main(Launcher.java:173) I'm obviously missing something here so any pointers greatly appreciated. I have removed all the jar, exe and xml files from the slaves several times, completely deleted the service from the slave, but no change in the behavior. thanks, chanda On Mon, Jan 7, 2013 at 11:17 AM, Richard Mortimer <ri...@oldelvet.org.uk>wrote: > Hi Mark, > > > On 07/01/2013 18:21, Mark Waite wrote: > >> I upgraded my Debian Jenkins LTS from 1.480.1 to 1.480.2 today using the >> Debian package manager. The machine was running with authentication >> enabled and was using Debian, CentOS, Red Hat, and Windows slave agents. >> The Linux slave agents are launched with ssh. The Windows slave >> agents are launched with JNLP from a batch file on the Windows machines. >> >> The upgrade seems to have blocked all connections from the Windows >> (JNLP) slaves. I assume that is intentional since I had authentication >> enabled and 1.480.2 attempts to disallow unauthenticated slave agent >> connections. I resolved that by disabling authentication on the master >> server. >> >> I believe that is a consequence of the changes made in 1.480.2. I > haven't upgraded my Jenkins instance yet to see this but I read the > following advisory earlier today and believe the change is related to that. > > https://wiki.jenkins-ci.org/**display/SECURITY/Jenkins+** > Security+Advisory+2013-01-04<https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04> > > Regards > > Richard > > > > After the upgrade, I see some "Dead" entries in the list of slaves on >> the left side of the Jenkins opening page. When I click the red "Dead" >> entry, it shows the following stack trace: >> >> java.lang.NullPointerException >> at hudson.matrix.**MatrixConfiguration.newBuild(** >> MatrixConfiguration.java:218) >> at hudson.matrix.**MatrixConfiguration.newBuild(** >> MatrixConfiguration.java:64) >> at hudson.model.AbstractProject.**createExecutable(** >> AbstractProject.java:1197) >> at hudson.model.AbstractProject.**createExecutable(** >> AbstractProject.java:136) >> at hudson.model.Executor.run(**Executor.java:211) >> >> >> Once I click through that "Dead" thread one or two times, the slave >> agent seems to remain running without interruption. >> >> Are those expected results that are part of the transition from 1.480.1 >> to 1.480.2? >> >> Thanks, >> Mark Waite >> > -- *Confidentiality Notice*: This e-mail, including all attachments, is confidential information of Lytro, Inc. If the reader of this e-mail is not the intended recipient or its authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
