Jenkins › Jenkins users

'This node is offline because it uses old slave.jar'

Classic

List

Threaded

4 messages Options

lata

'This node is offline because it uses old slave.jar'

I just updated Jenkins Master to 1.447.

All the nodes went offline.

Jenkins is installed as a windows service on these nodes.

I've stopped the service, and gave the jnlp command as follows:

javaws http://localhost:8080/computer/<slavename>/slave-agent.jnlp

Restarted the service.

But nothing happens.

found this but no resolution to it: https://issues.jenkins-ci.org/browse/JENKINS-10985

does anyone know how to fix this? (ofcourse it's really urgent, :-) )

Richard Bywater-2

Re: 'This node is offline because it uses old slave.jar'

What version did you upgrade from?

Richard.

On Sat, Aug 18, 2012 at 4:36 AM, Lata Kopalle <[hidden email]> wrote:

> I just updated Jenkins Master to 1.447.
> All the nodes went offline.
> Jenkins is installed as a windows service on these nodes.
> I've stopped the service, and gave the jnlp command as follows:
> javaws http://localhost:8080/computer/<slavename>/slave-agent.jnlp
> Restarted the service.
> But nothing happens.
>
> found this but no resolution to it:
> https://issues.jenkins-ci.org/browse/JENKINS-10985
>
> does anyone know how to fix this? (ofcourse it's really urgent, :-) )

lata

Re: 'This node is offline because it uses old slave.jar'

Richard, it was from 1.443. It seemed to have been caused due to the version column plugin. And when I disabled the plugin, the gui itself went down.

[ JENKINS-14401 ]. We couldn't afford the down-time, this is what we did, re-enabled the plugin (by removing the data/plugins/versioncolumn.hpi.disabled file), downgrade the Jenkins version back (and when the nodes didn't come back online, realized there are the lines <temporaryOfflineCause>...</temporaryOfflineCause> in the config.xml that need to be taken care of manually. Haven't tried the upgrade after that. thanks.

On Saturday, August 18, 2012 1:06:39 PM UTC+5:30, Richard Bywater wrote:

What version did you upgrade from?

Richard.

On Sat, Aug 18, 2012 at 4:36 AM, Lata Kopalle <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="npF367izHoIJ">la...@...> wrote:

> I just updated Jenkins Master to 1.447.
> All the nodes went offline.
> Jenkins is installed as a windows service on these nodes.
> I've stopped the service, and gave the jnlp command as follows:
> javaws http://localhost:8080/computer/<slavename>/slave-agent.jnlp
> Restarted the service.
> But nothing happens.
>
> found this but no resolution to it:
> https://issues.jenkins-ci.org/browse/JENKINS-10985
>
> does anyone know how to fix this? (ofcourse it's really urgent, :-) )

Pawel

Re: 'This node is offline because it uses old slave.jar'

In reply to this post by lata

Linux slaves will automatically update required jar, but Windows machines will not. Each Jenkins version requires specific slave.jar to be on all machines, otherwise it will turn them offline, until proper version is place there. You need to do this manually. [stop the service before doing so and start it afterwards]

You should have it at jenkins/jnlpJars/slave.jar
Old one that needs replacing is in your Jenkins slave folder, where you configured it with "Remote FS root" setting

It should be really working :)

On Friday, 17 August 2012 18:36:21 UTC+2, lata wrote:

I just updated Jenkins Master to 1.447.
All the nodes went offline.
Jenkins is installed as a windows service on these nodes.
I've stopped the service, and gave the jnlp command as follows:

javaws http://localhost:8080/computer/<slavename>/slave-agent.jnlp
Restarted the service.
But nothing happens.

found this but no resolution to it: https://issues.jenkins-ci.org/browse/JENKINS-10985

does anyone know how to fix this? (ofcourse it's really urgent, :-) )