Did these two different jenkins/hudson instances run on the same path simultaneously? I can see how this could cause some very, very odd behaviour. I'd start by bringing both down, then starting only one. If it is still broken, do you have backups?
Perhaps one feature - a lock file can prevent jenkins starting up where another already is, but the signal/exception handling would need to make sure it wasn't left around. Danny On Friday, 16 March 2012 04:41:39 UTC, Karthik wrote: > > I tried to run the new version of hudson from a separate jboss > instance. It seem to have affected existing hudson. Suddenly the jobs > don't appear in GUI. While re-starting Hudson, I notice below error in > jbossstart.log > > </Snip> > > 08:25:39,873 ERROR [STDERR] Mar 16, 2012 8:25:39 AM hudson.model.Hudson > $5 onTaskFailed > SEVERE: Failed Loading job STAR-FRAMEWORK > hudson.util.IOException2: Unable to read /home/star/.hudson/jobs/STAR- > FRAMEWORK/config.xml > at hudson.XmlFile.read(XmlFile.java:130) > at hudson.model.Items.load(Items.java:108) > at hudson.model.Hudson$13.run(Hudson.java:2268) > at org.jvnet.hudson.reactor.TaskGraphBuilder > $TaskImpl.run(TaskGraphBuilder.java:146) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at hudson.model.Hudson$4.runTask(Hudson.java:734) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > at java.util.concurrent.ThreadPoolExecutor > $Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor > $Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > Caused by: com.thoughtworks.xstream.converters.ConversionException: > Invalid reference > ---- Debugging information ---- > reference : ../project-properties/entry[9]/scm-property/originalValue > class : hudson.maven.MavenModuleSet > required-type : hudson.maven.MavenModuleSet > path : /maven2-moduleset/scm > line number : 98 > ------------------------------- > > </Snip> > > Likewise this is the same error that appears for all jobs. Please help > me to fix this. let me know, if you need more information
