| Hudson slaves killed (3.1.2 update) [message #1310460] |
Wed, 23 April 2014 03:42  |
Eclipse User |
|
|
|
Hi,
I've tried to install Hudson 3.1.2, but since this update, our slaves died after each build.
Our Hudson configuration uses two slaves (one on Linux, one on Windows), and both of them is killed each time a build is launched on it. The build is not even performed. For information, the slaves are connected using the JNLP mechanism.
When the slave executor thread is killed, I have the following stack trace :
com.google.common.util.concurrent.UncheckedExecutionException: java.lang.NullPointerException
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2263)
at com.google.common.cache.LocalCache.get(LocalCache.java:4000)
at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:4004)
at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4874)
at hudson.model.RunMap$LazyRunValueCache.get(RunMap.java:793)
at hudson.model.RunMap$LazyRunValueCache.access$1900(RunMap.java:736)
at hudson.model.RunMap$LazyRunValue.getBuild(RunMap.java:1559)
at hudson.model.RunMap$4.apply(RunMap.java:545)
at hudson.model.RunMap$4.apply(RunMap.java:541)
at com.google.common.collect.Lists$TransformingRandomAccessList.get(Lists.java:575)
at java.util.AbstractList$Itr.next(Unknown Source)
at hudson.model.Job.getEstimatedDuration(Job.java:1317)
at hudson.model.queue.MappingWorksheet.<init>(MappingWorksheet.java:353)
at hudson.model.queue.MappingWorksheet.<init>(MappingWorksheet.java:335)
at hudson.model.Queue.maintain(Queue.java:990)
at hudson.model.Queue.pop(Queue.java:817)
at hudson.model.Executor.grabJob(Executor.java:188)
at hudson.model.Executor.run(Executor.java:113)
Caused by: java.lang.NullPointerException
at hudson.model.RunMap$LazyRunValueCache$1.load(RunMap.java:776)
at hudson.model.RunMap$LazyRunValueCache$1.load(RunMap.java:770)
at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3599)
at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2379)
at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2342)
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2257)
... 17 more
The master is also killed at the same time with the following stack trace :
com.google.common.util.concurrent.UncheckedExecutionException: java.lang.NullPointerException
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2263)
at com.google.common.cache.LocalCache.get(LocalCache.java:4000)
at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:4004)
at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4874)
at hudson.model.RunMap$LazyRunValueCache.get(RunMap.java:793)
at hudson.model.RunMap$LazyRunValueCache.access$1900(RunMap.java:736)
at hudson.model.RunMap$LazyRunValue.getBuild(RunMap.java:1559)
at hudson.model.RunMap$4.apply(RunMap.java:545)
at hudson.model.RunMap$4.apply(RunMap.java:541)
at com.google.common.collect.Lists$TransformingRandomAccessList.get(Lists.java:575)
at java.util.AbstractList$Itr.next(Unknown Source)
at hudson.model.Job.getEstimatedDuration(Job.java:1317)
at hudson.model.queue.MappingWorksheet.<init>(MappingWorksheet.java:353)
at hudson.model.queue.MappingWorksheet.<init>(MappingWorksheet.java:335)
at hudson.model.Queue.maintain(Queue.java:990)
at hudson.model.Queue.pop(Queue.java:817)
at hudson.model.Executor.grabJob(Executor.java:188)
at hudson.model.Executor.run(Executor.java:113)
Caused by: java.lang.NullPointerException
at hudson.model.RunMap$LazyRunValueCache$1.load(RunMap.java:776)
at hudson.model.RunMap$LazyRunValueCache$1.load(RunMap.java:770)
at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3599)
at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2379)
at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2342)
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2257)
Do you have any idea on how I can correct this ? May I must downgrade to 3.1.1 ? Or it's because of one of my installed plugins ?
[Updated on: Wed, 23 April 2014 03:44] by Moderator |
|
|
| Re: Hudson slaves killed (3.1.2 update) [message #1310644 is a reply to message #1310460] |
Wed, 23 April 2014 05:58  |
| Eclipse User |
|
|
|
Resolved ! 
The problem was not due to the new Hudson version, but to how we have made the update.
Indeed, after a first step to update Hudson to 3.1.2, we have installed the plugin 'Build Pipeline Plugin' to evaluate it, but this causes some errors (don't known why). Thus, we have uninstalled it and made a backup restoration.
But, as some builds have been done since the last backup, the files '_runmap.xml' located in the directory of the job executed on the slaves were corrupted by the new builds : they were containing two <build> with the same identifier, as the restoration reverted the also next build number... After deleting the duplicated builds in '_runmap.xml', and correcting the next build number, the slaves reacts correctly.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03187 seconds
Home