[JIRA] (JENKINS-57569) Can't boot Jenkins since upgrade to 2.178

241 views
Skip to first unread message

TechnologyDatalakeServices@axa-im.com (JIRA)

unread,
May 20, 2019, 2:28:03 PM5/20/19
to jenkinsc...@googlegroups.com
Technology Services created an issue
 
Jenkins / Bug JENKINS-57569
Can't boot Jenkins since upgrade to 2.178
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 2019-05-20 18:27
Priority: Blocker Blocker
Reporter: Technology Services

I update jenkins.war from 2.177 to 2.178 and restart the service.

Then I get below stacktrace in the Jenkins website:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ldapUserSearch': Cannot resolve reference to bean 'initialDirContextFactory' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'initialDirContextFactory': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.acegisecurity.ldap.DefaultInitialDirContextFactory]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: An LDAP connection URL must be supplied.
 at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275)
 at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104)
 at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:495)
 at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:162)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:835)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
 at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
 at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
 at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
 at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
 at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
 at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
 at hudson.util.spring.DefaultRuntimeSpringConfiguration.getApplicationContext(DefaultRuntimeSpringConfiguration.java:94)
 at hudson.util.spring.BeanBuilder.createApplicationContext(BeanBuilder.java:391)
 at hudson.security.LDAPSecurityRealm.createSecurityComponents(LDAPSecurityRealm.java:645)
 at hudson.security.SecurityRealm.getSecurityComponents(SecurityRealm.java:448)
 at hudson.security.HudsonFilter.reset(HudsonFilter.java:138)
 at jenkins.model.Jenkins.setSecurityRealm(Jenkins.java:2527)
 at jenkins.model.Jenkins$16.run(Jenkins.java:3225)
 at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
 at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)
 at jenkins.model.Jenkins$5.runTask(Jenkins.java:1091)
 at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
 at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:748)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'initialDirContextFactory': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.acegisecurity.ldap.DefaultInitialDirContextFactory]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: An LDAP connection URL must be supplied.
 at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:254)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:835)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
 at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
 at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
 at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
 at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:269)
 ... 32 more
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.acegisecurity.ldap.DefaultInitialDirContextFactory]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: An LDAP connection URL must be supplied.
 at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
 at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87)
 at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:248)
 ... 44 more
Caused by: java.lang.IllegalArgumentException: An LDAP connection URL must be supplied.
 at org.springframework.util.Assert.hasLength(Assert.java:136)
 at org.acegisecurity.ldap.DefaultInitialDirContextFactory.setProviderUrl(DefaultInitialDirContextFactory.java:135)
 at org.acegisecurity.ldap.DefaultInitialDirContextFactory.<init>(DefaultInitialDirContextFactory.java:124)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
 at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
 ... 46 more
Caused: org.jvnet.hudson.reactor.ReactorException
 at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282)
 at jenkins.InitReactorRunner.run(InitReactorRunner.java:48)
 at jenkins.model.Jenkins.executeReactor(Jenkins.java:1125)
 at jenkins.model.Jenkins.<init>(Jenkins.java:932)
 at hudson.model.Hudson.<init>(Hudson.java:85)
 at hudson.model.Hudson.<init>(Hudson.java:81)
 at hudson.WebAppMain$3.run(WebAppMain.java:233)
Caused: hudson.util.HudsonFailedToLoad
 at hudson.WebAppMain$3.run(WebAppMain.java:250)
 

 

I try to downgrade the war to 2.177 and restart the service, but I still get the same issue:

I check the jenkins.log and get this;

2019-05-20 17:08:02.396+0000 [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Inspecting plugin /data/jenkins/plugins/bouncycastle-api.hpi
2019-05-20 17:08:02.400+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Inspecting plugin /data/jenkins/plugins/ldap.hpi
2019-05-20 17:08:02.425+0000 [id=29] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Inspecting plugin /data/jenkins/plugins/antisamy-markup-formatter.hpi
2019-05-20 17:08:02.435+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Inspecting plugin /data/jenkins/plugins/ant.hpi
2019-05-20 17:08:02.449+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Inspecting plugin /data/jenkins/plugins/external-monitor-job.hpi
2019-05-20 17:08:02.516+0000 [id=29] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin bouncycastle API Plugin v2.16.0 (bouncycastle-api)
2019-05-20 17:08:02.533+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SAML Plugin v1.1.2 (saml)
2019-05-20 17:08:02.774+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Warnings Next Generation Plugin v5.0.0 (warnings-ng)
2019-05-20 17:08:02.778+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SSH Agent Plugin v1.17 (ssh-agent)
2019-05-20 17:08:13.663+0000 [id=27] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading global config
2019-05-20 17:08:13.669+0000 [id=20] SEVERE hudson.util.BootFailure#publish: Failed to initialize Jenkins
2019-05-20 17:09:12.468+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SAML Plugin v1.1.2 (saml)
2019-05-20 17:09:12.654+0000 [id=29] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Warnings Next Generation Plugin v5.0.0 (warnings-ng)
2019-05-20 17:09:12.658+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SSH Agent Plugin v1.17 (ssh-agent)
2019-05-20 17:09:23.609+0000 [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Finalizing set up
2019-05-20 17:09:23.612+0000 [id=20] SEVERE hudson.util.BootFailure#publish: Failed to initialize Jenkins
2019-05-20 17:16:17.516+0000 [id=27] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SAML Plugin v1.1.2 (saml)
2019-05-20 17:16:17.695+0000 [id=27] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Warnings Next Generation Plugin v5.0.0 (warnings-ng)
2019-05-20 17:16:17.700+0000 [id=29] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SSH Agent Plugin v1.17 (ssh-agent)
2019-05-20 17:16:29.174+0000 [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Finalizing set up
2019-05-20 17:16:29.182+0000 [id=20] SEVERE hudson.util.BootFailure#publish: Failed to initialize Jenkins
SEVERE: Failed Loading plugin SAML Plugin v1.1.2 (saml)
SEVERE: Failed Loading plugin Warnings Next Generation Plugin v5.0.0 (warnings-ng)
SEVERE: Failed Loading plugin SSH Agent Plugin v1.17 (ssh-agent)
SEVERE: Failed Finalizing set up
SEVERE: Failed to initialize Jenkins
2019-05-20 17:24:56.858+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SAML Plugin v1.1.2 (saml)
2019-05-20 17:24:57.031+0000 [id=29] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Warnings Next Generation Plugin v5.0.0 (warnings-ng)
2019-05-20 17:24:57.037+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SSH Agent Plugin v1.17 (ssh-agent)
2019-05-20 17:25:09.341+0000 [id=29] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Finalizing set up
2019-05-20 17:25:09.345+0000 [id=20] SEVERE hudson.util.BootFailure#publish: Failed to initialize Jenkins
2019-05-20 17:39:37.391+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SAML Plugin v1.1.2 (saml)
2019-05-20 17:39:37.538+0000 [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Warnings Next Generation Plugin v5.0.0 (warnings-ng)
2019-05-20 17:39:37.541+0000 [id=29] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SSH Agent Plugin v1.17 (ssh-agent)
2019-05-20 17:39:48.532+0000 [id=28] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Finalizing set up
2019-05-20 17:39:48.536+0000 [id=20] SEVERE hudson.util.BootFailure#publish: Failed to initialize Jenkins
2019-05-20 17:40:33.714+0000 [id=29] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SAML Plugin v1.1.2 (saml)
2019-05-20 17:40:33.895+0000 [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Warnings Next Generation Plugin v5.0.0 (warnings-ng)
2019-05-20 17:40:33.899+0000 [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SSH Agent Plugin v1.17 (ssh-agent)
2019-05-20 17:40:45.377+0000 [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Finalizing set up
2019-05-20 17:40:45.385+0000 [id=20] SEVERE hudson.util.BootFailure#publish: Failed to initialize Jenkins

Any idea how to solve it, please?

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

o.v.nenashev@gmail.com (JIRA)

unread,
May 21, 2019, 6:06:02 AM5/21/19
to jenkinsc...@googlegroups.com
Oleg Nenashev commented on Bug JENKINS-57569
 
Re: Can't boot Jenkins since upgrade to 2.178

AFAICT it is coming from the LDAP plugin (hudson.security.LDAPSecurityRealm in the stacktrace) .

https://github.com/jenkinsci/ldap-plugin/blob/master/src/main/java/hudson/security/LDAPSecurityRealm.java

 

o.v.nenashev@gmail.com (JIRA)

unread,
May 21, 2019, 6:06:02 AM5/21/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
 
Change By: Oleg Nenashev
Component/s: ldap-plugin

dbeck@cloudbees.com (JIRA)

unread,
May 21, 2019, 7:50:02 AM5/21/19
to jenkinsc...@googlegroups.com
Daniel Beck commented on Bug JENKINS-57569
 
Re: Can't boot Jenkins since upgrade to 2.178

Yeah but a bad configuration. And that also does not explain why plugins fail to load. Looks more like disk/permissions issues.

flood@itnews-bg.com (JIRA)

unread,
May 22, 2019, 6:10:03 AM5/22/19
to jenkinsc...@googlegroups.com

We are using Jenkins with LDAP as well and upgrading from 2.174 to 2.178 was successful. LDAP Authentication is working just fine for us. We are also using the latest versions of all plugins.

dbeck@cloudbees.com (JIRA)

unread,
May 22, 2019, 1:37:02 PM5/22/19
to jenkinsc...@googlegroups.com
Daniel Beck updated an issue
 
Change By: Daniel Beck
Labels: regression

martin@grachtwal.nu (JIRA)

unread,
May 27, 2019, 6:36:02 AM5/27/19
to jenkinsc...@googlegroups.com

romen@romenrg.com (JIRA)

unread,
May 27, 2019, 12:35:02 PM5/27/19
to jenkinsc...@googlegroups.com
Romen Rodriguez-Gil started work on Bug JENKINS-57569
 
Change By: Romen Rodriguez-Gil
Status: Open In Progress

romen@romenrg.com (JIRA)

unread,
May 27, 2019, 12:35:03 PM5/27/19
to jenkinsc...@googlegroups.com
Romen Rodriguez-Gil stopped work on Bug JENKINS-57569
 
Change By: Romen Rodriguez-Gil
Status: In Progress Open

jake.price@gmail.com (JIRA)

unread,
Aug 22, 2019, 8:56:03 PM8/22/19
to jenkinsc...@googlegroups.com

I experienced this tonight from upgrading to 2.164.3 to 2.176.2.  

 

22-Aug-2019 20:28:22.286 SEVERE [pool-6-thread-8] jenkins.InitReactorRunner$1.onTaskFailed Failed Inspecting plugin /usr/local/jee/hudson/plugins/ldap.hpi
java.io.IOException: Failed to expand /usr/local/jee/hudson/plugins/ldap.hpi
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:478)
at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:174)
at hudson.PluginManager$1$3$1.run(PluginManager.java:431)


at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)

at jenkins.model.Jenkins$5.runTask(Jenkins.java:1095)


at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: src '/usr/local/jee/hudson/plugins/ldap.hpi' doesn't exist.
at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:128)
at hudson.ClassicPluginStrategy.unzipExceptClasses(ClassicPluginStrategy.java:550)
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:475)
... 10 more

 

Eventually I also got the bean issue described in this.  I've since removed ldap.jpi / hpi and ldap directory in /plugins/ replaced it with the HPI from the plugin site and rolled back to 2.164.3.

Reply all
Reply to author
Forward
0 new messages