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 <https://issues.jenkins-ci.org/browse/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 <la...@2lini.com<javascript:>> > 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, :-) ) >
