subject:"\[JIRA\] \[core\] $JENKINS\-22525$ A Slave disappears every time Jenkins boots up"

Martin Kutter
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up on IBM Java

The ConversionException: Could not call hudson.EnvVars.readObject() : Invalid reference above is probably unrelated: It looks like my config had invalid references. After cleaning them up, this message disappeared.

However, the IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" could be the reason for this issue.

I reproduced the issue with Jenkins-1.656 with the following JDKs:

IBM JDK 6 SR 16 on AIX 7.1
IBM JDK 7 SR 6 on AIX 7.1
IBM JDK 7 SR 7 (latest). on AIX 7.1
IBM JDK 7 (build 2.6) on Windows.

In my case, the "missing" slave is always the first slave in the config.xml, so I would assume that loading a Slave from disk (and creating a hudsom.model.Queue$ItemList) does not work the first time,
but works on subsequent tries.

I've also found that the same error is thrown when creating a new slave on a fresh jenkins (on save / doCreateItem):

A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.

Stack trace

javax.servlet.ServletException: java.lang.IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)

The slave is saved nonetheless.

Subsequent slaves can be created without this error.

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

--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java

Martin Kutter
commented on JENKINS-22525

A Slave disappears every time Jenkins boots up on IBM Java

However, the IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" could be the reason for this issue.

I reproduced the issue with Jenkins-1.656 with the following JDKs:

IBM JDK 6 SR 16 on AIX 7.1
IBM JDK 7 SR 6 on AIX 7.1
IBM JDK 7 SR 7 (latest). on AIX 7.1
IBM JDK 7 (build 2.6) on Windows.

I've also found that the same error is thrown when creating a new slave on a fresh jenkins (on save / doCreateItem):

Stack trace

The slave is saved nonetheless.

Subsequent slaves can be created without this error.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java

Martin Kutter
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up on IBM Java

However, the IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" could be the reason for this issue.

I reproduced the issue with Jenkins-1.656 with the following JDKs:

IBM JDK 6 SR 16 on AIX 7.1
IBM JDK 7 SR 6 on AIX 7.1
IBM JDK 7 SR 7 (latest). on AIX 7.1
IBM JDK 7 (build 2.6) on Windows.

I've also found that the same error is thrown when creating a new slave on a fresh jenkins (on save / doCreateItem):

Stack trace

The slave is saved nonetheless.

Subsequent slaves can be created without this error.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java

Martin Kutter
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up on IBM Java

However, the IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" could be the reason for this issue.

I reproduced the issue with Jenkins-1.656 with the following JDKs:

IBM JDK 6 SR 16 on AIX 7.1
IBM JDK 7 SR 6 on AIX 7.1
IBM JDK 7 SR 7 (latest). on AIX 7.1
IBM JDK 7 (build 2.6) on Windows.

I've also found that the same error is thrown when creating the first slave node on a fresh jenkins instance (on save / doCreateItem):

Stack trace

The slave is saved nonetheless.

Subsequent slaves can be created without this error.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java













































 
Martin Kutter
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up on IBM Java
















The ConversionException: Could not call hudson.EnvVars.readObject() : Invalid reference above is probably unrelated: It looks like my config had invalid references. After cleaning them up, this message disappeared.

However, the IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" could be the reason for this issue.

I reproduced the issue with Jenkins-1.656 with the following JDKs:


	IBM JDK 6 SR 16 on AIX 7.1
	IBM JDK 7 SR 6 on AIX 7.1
	IBM JDK 7 SR 7 (latest). on AIX 7.1
	IBM JDK 7 (build 2.6) on Windows.



In my case, the "missing" slave is always the first slave in the config.xml, so I would assume that loading a Slave from disk (and creating a hudsom.model.Queue$ItemList) does not work the first time,
but works on subsequent tries.

I've also found that the same error is thrown when creating the first slave node on a fresh jenkins instance (on save / doCreateItem):


 
Stack trace (excerpt):

Caused by: java.lang.IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"
	at java.lang.Class.getDeclaringClass(Class.java:821)
	at sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl.init(ParameterizedTypeImpl.java:52)
	at sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl.make(ParameterizedTypeImpl.java:95)
	at sun.reflect.generics.factory.CoreReflectionFactory.makeParameterizedType(CoreReflectionFactory.java:105)
	at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:140)
	at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:49)
	at sun.reflect.generics.repository.FieldRepository.getGenericType(FieldRepository.java:85)
	at java.lang.reflect.Field.getGenericType(Field.java:237)
	at com.thoughtworks.xstream.mapper.AnnotationMapper.processTypes(AnnotationMapper.java:224)
	at com.thoughtworks.xstream.mapper.AnnotationMapper.processAnnotations(AnnotationMapper.java:182)
	at com.thoughtworks.xstream.mapper.AnnotationMapper.serializedClass(AnnotationMapper.java:129)
	at hudson.util.xstream.MapperDelegate.serializedClass(MapperDelegate.java:39)
	at com.thoughtworks.xstream.mapper.MapperWrapper.serializedClass(MapperWrapper.java:26)
	at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:62)
	at hudson.slaves.NodeList$ConverterImpl.marshal(NodeList.java:151)




The slave is saved nonetheless. 

Subsequent slaves can be created without this error.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java















































Martin Kutter
 commented on  JENKINS-22525


A Slave disappears every time Jenkins boots up on IBM Java















We're running Jenkins on IBM JDK on AIX.

I haven't met this issue with Jenkins-1.532.2-LTS - however, I've seen this issue with 1.565. Maybe this helps narrowing down the issue.

System details:

AIX 7.1
IBM J9 VM (build 2.6, JRE 1.7.0 AIX ppc-32 20140106_181350 (JIT enabled, AOT enabled)
Tomcat 1.0.50




























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java















































Martin Kutter
 commented on  JENKINS-22525


A Slave disappears every time Jenkins boots up on IBM Java















In my case, reloading the configuration from disk also helps.

Before I reload the configuration from disk, Jenkins complains that there is Old data on disk.
It displays the following:

Type: hudson.model.Hudson
Name:
Error: IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue", ConversionException: Could not call hudson.EnvVars.readObject() : Invalid reference  Debugging information  reference : ../../../../../../../slave/nodeProperties/hudson.slaves.EnvironmentVariablesNodeProperty/envVars/tree-map/default/comparator --- message : Could not call hudson.EnvVars.readObject() cause-exception : com.thoughtworks.xstream.converters.ConversionException cause-message : Invalid reference class : hudson.EnvVars required-type : hudson.EnvVars converter-type : com.thoughtworks.xstream.converters.reflection.SerializableConverter path : /hudson/slaves/slave2/nodeProperties/hudson.slaves.EnvironmentVariablesNodeProperty/envVars/tree-map/default/comparator line number : 243 ---, InstantiationError: null, MissingFieldException: No field 'hudson.tools.ToolLocationNodeProperty' found in class 'hudson.model.Hudson'



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java













































 
Martin Kutter
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up on IBM Java
















In my case, reloading the configuration from disk also helps.

Before I reload the configuration from disk, Jenkins complains that there is Old data on disk.
It displays the following:

{{Type: hudson.model.Hudson
Name:
Error: IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue", ConversionException: Could not call hudson.EnvVars.readObject() : Invalid reference  Debugging information  reference : ../../../../../../../slave/nodeProperties/hudson.slaves.EnvironmentVariablesNodeProperty/envVars/tree-map/default/comparator --- message : Could not call hudson.EnvVars.readObject() cause-exception : com.thoughtworks.xstream.converters.ConversionException cause-message : Invalid reference class : hudson.EnvVars required-type : hudson.EnvVars converter-type : com.thoughtworks.xstream.converters.reflection.SerializableConverter path : /hudson/slaves/slave2/nodeProperties/hudson.slaves.EnvironmentVariablesNodeProperty/envVars/tree-map/default/comparator line number : 243 ---, InstantiationError: null, MissingFieldException: No field 'hudson.tools.ToolLocationNodeProperty' found in class 'hudson.model.Hudson'
}}



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java













































 
Martin Kutter
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up on IBM Java
















In my case, reloading the configuration from disk also helps.

Before I reload the configuration from disk, Jenkins complains that there is Old data on disk.
It displays the following:




Type: hudson.model.Hudson
Name:
Error: IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue", ConversionException: Could not call hudson.EnvVars.readObject() : Invalid reference  Debugging information  reference : ../../../../../../../slave/nodeProperties/hudson.slaves.EnvironmentVariablesNodeProperty/envVars/tree-map/default/comparator --- message : Could not call hudson.EnvVars.readObject() cause-exception : com.thoughtworks.xstream.converters.ConversionException cause-message : Invalid reference class : hudson.EnvVars required-type : hudson.EnvVars converter-type : com.thoughtworks.xstream.converters.reflection.SerializableConverter path : /hudson/slaves/slave2/nodeProperties/hudson.slaves.EnvironmentVariablesNodeProperty/envVars/tree-map/default/comparator line number : 243 ---, InstantiationError: null, MissingFieldException: No field 'hudson.tools.ToolLocationNodeProperty' found in class 'hudson.model.Hudson'



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java













































 
Martin Kutter
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up on IBM Java
















In my case, reloading the configuration from disk also helps.

Before I reload the configuration from disk, Jenkins complains that there is Old data on disk.
It displays the following:


Type: hudson.model.Hudson
Name:
Error: IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue", ConversionException: Could not call hudson.EnvVars.readObject() : Invalid reference 
 Debugging information  
reference : ../../../../../../../slave/nodeProperties/hudson.slaves.EnvironmentVariablesNodeProperty/envVars/tree-map/default/comparator 
--- 
message : Could not call hudson.EnvVars.readObject() 
cause-exception : com.thoughtworks.xstream.converters.ConversionException 
cause-message : Invalid reference 
class : hudson.EnvVars 
required-type : hudson.EnvVars 
converter-type : com.thoughtworks.xstream.converters.reflection.SerializableConverter 
path : /hudson/slaves/slave[2]/nodeProperties/hudson.slaves.EnvironmentVariablesNodeProperty/envVars/tree-map/default/comparator 
line number : 243 
---, 
InstantiationError: null, MissingFieldException: No field 'hudson.tools.ToolLocationNodeProperty' found in class 'hudson.model.Hudson'





























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java

2014-07-03 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-22525


A Slave disappears every time Jenkins boots up on IBM Java















IBM JDK on AIX is probably one of the worst supported environments for Jenkins. Consider moving the master node to e.g. Linux with Oracle JDK 7, which should be fairly reliable.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

2014-05-23 Thread gabriel.lopez.ar...@gmail.com (JIRA)

Gabriel Lopez
commented on JENKINS-22525

A Slave disappears every time Jenkins boots up

Hi. Sorry for the delay.
Oleg- The slave is nothing out of the ordinary, just a simple, Java Web Start slave. It is not happening with the "same" slave always, just one that gets disappeared. If I have 4, and jenkins is restarted, 3 appears. If I restart again, I'm left with 2. My feeling is that it depends on the order in the xml configuration.

John - No, it was a new installation. I recently updated to 1.554.1 LTS, and removed the webapps folder. The issue is still there. I'll try removing the cache directory, though. It is a Windows machine, so I'll see where that folder is.

Daniel- Yes, there is. It says: hudson.model.Hudson IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue.". But I'm not too convinced that it is related, as Oleg said.

While troubleshooting the issue, I found out that the missing slave configuration was in the jenkins' config XML, and discovered that hitting "Reload configuration from disk" makes the slave to appear again. As a workaround, I created a Groovy post-init script (https://wiki.jenkins-ci.org/display/JENKINS/Post-initialization+script), that calls the Reloading function.. So after restarting and just after finishing the initialization process, my jenkins reloads the configuration again, making the slave to appear again. It is a dirty workaround, but has been working for several weeks.

My suspicion is that it is a problem when running Jenkins on IBM Java, maybe even specific with IBM java versions.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

2014-05-23 Thread o.v.nenas...@gmail.com (JIRA)















































Oleg Nenashev
 commented on  JENKINS-22525


A Slave disappears every time Jenkins boots up















There're other issues with classloading on IBM Java. This issue is likely caused by IBM's j9 like it has been mentioned by Pei-Tang and Gabriel.

I'll create a master-issue, which will reference all others



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java

2014-05-23 Thread o.v.nenas...@gmail.com (JIRA)















































Oleg Nenashev
 updated  JENKINS-22525


A Slave disappears every time Jenkins boots up on IBM Java
















Change By:


Oleg Nenashev
(23/May/14 5:20 PM)




Summary:


ASlavedisappearseverytimeJenkinsbootsup
onIBMJava



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

2014-05-21 Thread tangthe...@gmail.com (JIRA)















































Pei-Tang Huang
 commented on  JENKINS-22525


A Slave disappears every time Jenkins boots up















I cahnged the JRE from IBM's j9 to Oracle's one (jdk1.7.0_55 x64), restart, restart, restart, none of my slaves have been taken!



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

2014-05-21 Thread tangthe...@gmail.com (JIRA)













































 
Pei-Tang Huang
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up
















I changed the JRE from IBM's j9 to Oracle's one (jdk1.7.0_55 x64), restart, restart, restart, none of my slaves have been taken!



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

2014-05-20 Thread tangthe...@gmail.com (JIRA)















































Pei-Tang Huang
 commented on  JENKINS-22525


A Slave disappears every time Jenkins boots up















We first encounter this situation from about Oct/13

The jvm info of my installation:

JRE 1.6.0 IBM J9 2.4 Windows Server 2008 R2 amd64-64 jvmwa6460sr10fp1-20120202_101568 (JIT enabled, AOT enabled)J9VM - 20120202_101568JIT  - r9_2007_21307ifx1GC   - 20120202_AA



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

2014-05-17 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-22525


A Slave disappears every time Jenkins boots up















Is there an entry in Manage Jenkins » Manage Old Data for the logged exception?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

2014-05-15 Thread wangxinb...@gmail.com (JIRA)















































Pery Wing
 commented on  JENKINS-22525


A Slave disappears every time Jenkins boots up















I also meet same problems. install both 1.558 version and 1.554.1(LTS). create a slave node then restart web server the slave node lost.
Some time will encounter exception as this ticket show when create the slave node.

I finally install the 1.528 seems works well for me.

I also think that a defect in newer vesion

My isntall evn: RHEL+tomcat8  



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up













































 
John Tal
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up
















FYI - Similar error of incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" occurs on fresh install of Jenkins (v1.5623) when trying to add a newly defined slave.  

When an existing Jenkins installation is updated to latest (v1.5623) and multiple updates to the main configuration are made with restarts you can end up with all nodes disappearing.

In our cases is occurring on RHEL - Linux version 2.6.18-348.6.1.el5



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up













































 
John Tal
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up
















When an existing Jenkins installation is updated to latest (v1.5623) and multiple updates to the main configuration are made with restarts you can end up with all nodes disappearing.

In our case is occurring on RHEL - Linux version 2.6.18-348.6.1.el5

Where in-place upgrades are made, is there a need to clear out directories such as .jenkins/cache or others?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up













































 
John Tal
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up
















Was this an in place update/upgrade done recently?  At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place.  Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in place upgrade.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up













































 
John Tal
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up
















Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)?  At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place.  Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up













































 
John Tal
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up
















Was this an in place update/upgrade that done recently from a previous version of Jenkins (or even hudson)?  At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place.  Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in place upgrade.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up













































 
John Tal
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up
















Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)?  At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place.  Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade.

Also note there is a ~/.jenkins/cache directory where jar file versions may be.  Don't suggest you play in there unless step above has been tried and then, if still failing, after you have stopped jenkins to rename/delete cache contents.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

John Tal
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up

Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade.

Also note there is a ~/.jenkins/cache directory where jar file versions may be. Don't suggest you play in there unless step above has been tried and then, if still failing, after you have stopped jenkins to rename/delete cache contents.

With additional testing with in-place .war update Jenkins 1.528 does not show this issue ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas as dropping in-place higher Jenkins versions including 1.562 does have this issue.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

John Tal
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up

For an existing installation we are seeing this same issue when we update to Jenkins 1.562 ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas as dropping in-place a lower Jenkins version such as 1.528 does not show this issue.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

John Tal
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up

For an existing installation we are seeing this same issue when we update to Jenkins 1.562 ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas dropping in-place a lower Jenkins version such as 1.528 does not show this issue.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

John Tal
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up

Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping a new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade.

With further testing we can get this same error to occur with different versions of Jenkins. For an existing installation we are seeing this same issue when we update to Jenkins 1.562 ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas dropping in-place a lower Jenkins version such as 1.528 does not show this issue.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up

John Tal
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up

Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping a new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade.

For an existing installation we are seeing this same issue when we update to Jenkins 1.562 ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas dropping in-place a lower Jenkins version such as 1.528 does not show this issue.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up