er
>
> ** **
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Chanda Unmack
> *Sent:* 09 January 2013 19:18
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: Null pointer exceptions after upgrade from 1.480.1 to
>
ous”.
Matthew Webber
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Chanda Unmack
Sent: 09 January 2013 19:18
To: jenkinsci-users@googlegroups.com
Subject: Re: Null pointer exceptions after upgrade from 1.480.1 to 1.480.2
Spoke too soon apparently - as soon
Spoke too soon apparently - as soon as I logged out of the slave, the
connection was broken, so back to where I was before.
Any other ideas? I'm going to keep looking in case there is a jnlp hiding
somewhere else on the system.
chanda
On Wed, Jan 9, 2013 at 11:04 AM, Chanda Unmack wrote:
> Tha
Thanks for the pointer - sometimes it takes an external pair of eyes to see
something so obvious :) I did read that advisory, and I thought I was
deleting everything and or it was overwriting the *.jnlp. Unfortunately it
looks as if it was merely adding copies, and not overwriting - found
slave-age
I think that message means that the technique which is launching the slaves
as a windows service from the GUI is using JNLP.
The security advisory page on the wiki [1] says "Slaves that are started
via Java Web Start will fail to reconnect if the *.jnlp file is locally
stored. This is because t
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
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 laun
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 laun
