Bug #16055
Updated by François ARMAND over 4 years ago
This happened after a reboot where Rudder was behaving very strangely (slow, no connection to DB, etc). See #16051. The trace is: <pre> Caused by: java.lang.RuntimeException: BackendException: An error occured; cause was: java.lang.Error: null -> com.normation.ldap.sdk.PooledConnectionProvider.liftedTree1$1(LDAPConnectionProvider.scala:243) -> com.normation.ldap.sdk.PooledConnectionProvider.pool(LDAPConnectionProvider.scala:238) -> com.normation.ldap.sdk.PooledConnectionProvider.pool$(LDAPConnectionProvider.scala:238) at com.normation.cfclerk.services.impl.GitTechniqueReader$RunOrThrow.runNow(GitTechniqueReader.scala:149) at com.normation.cfclerk.services.impl.GitTechniqueReader.<init>(GitTechniqueReader.scala:185) at bootstrap.liftweb.RudderConfig$.techniqueReader$lzycompute(RudderConfig.scala:1266) at bootstrap.liftweb.RudderConfig$.techniqueReader(RudderConfig.scala:1228) at bootstrap.liftweb.RudderConfig$.techniqueRepositoryImpl$lzycompute(RudderConfig.scala:1631) at bootstrap.liftweb.RudderConfig$.techniqueRepositoryImpl(RudderConfig.scala:1629) </pre> Which matches that code: <pre> 231 trait PooledConnectionProvider[LDAP <: RoLDAPConnection] extends LDAPConnectionProvider[LDAP] { 232 self:UnboundidConnectionProvider => 233 234 def poolSize : Int 235 def ldifFileLogger:LDIFFileLogger 236 237 // for performance reason, operation on pool can't be wrapped into ZIO 238 protected lazy val pool = try { 239 new LDAPConnectionPool(self.newUnboundidConnection, poolSize) 240 } catch { 241 case ex: LDAPException => 242 LDAPConnectionLogger.error(s"Error during LDAP connection pool initialisation. Exception: ${ex.getDiagnosticMessage}") 243 throw new Error(ex.getDiagnosticMessage) 244 } </pre>