Project

General

Profile

Actions

Bug #11131

closed

Transitory error on LDAP at upgrade of Rudder 4.1 to 4.2 beta2 on debian8

Added by Nicolas CHARLES over 7 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - UI & UX
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

When upgrading Rudder, on Debian 8, I got an error when logging on the web interface for policy generation

⇨ Policy update error for process '6' at 2017-07-12 08:43:51
⇨ Cannot write configuration node
⇨ Can't get a new LDAP connection

Logs show that DSC ldap itemps where correctly created, but then I got

2017-07-12 08:43:48] DEBUG com.normation.rudder.services.policies.PromiseGenerationServiceImpl - Node's target configuration built in 1250 ms, start to update rule values.
[2017-07-12 08:43:48] DEBUG com.normation.rudder.services.policies.PromiseGenerationServiceImpl - RuleVals updated in 94 ms, start to detect changes in node configuration.
[2017-07-12 08:43:48] DEBUG com.normation.rudder.services.policies.PromiseGenerationServiceImpl - Checked node configuration updates leading to rules serial number updates and serial number updated in 26 ms
[2017-07-12 08:43:48] INFO  com.normation.rudder.services.policies.nodeconfig.NodeConfigurationServiceImpl - Configuration of following nodes were updated, their promises are going to be written: [root]
2017-07-12 08:43:48.647:INFO:oejsh.ContextHandler:started o.e.j.w.WebAppContext{/rudder,file:/var/rudder/tmp/jetty/jetty-127.0.0.1-8080-rudder.war-_rudder-any-/webapp/},/opt/rudder/share/webapps/rudder.war
[2017-07-12 08:43:49] INFO  bootstrap.liftweb.Boot - classpath
[2017-07-12 08:43:49] INFO  application - Application Rudder started
2017-07-12 08:43:49.564:INFO:oejs.AbstractConnector:Started SelectChannelConnector@127.0.0.1:8080
[2017-07-12 08:43:51] DEBUG com.normation.rudder.services.policies.PromiseGenerationServiceImpl - Node configuration written on filesystem in 2657 ms
[2017-07-12 08:43:51] ERROR com.normation.ldap.sdk.RWPooledSimpleAuthConnectionProvider - Can't get a new LDAP connection
com.unboundid.ldap.sdk.LDAPException: An error occurred while attempting to connect to server localhost:389:  java.io.IOException: LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server localhost/127.0.0.1:389:  ConnectException(message='Connection refused (Connection refused)', trace='socketConnect(PlainSocketImpl.java:native) / doConnect(AbstractPlainSocketImpl.java:350) / connectToAddress(AbstractPlainSocketImpl.java:206) / connect(AbstractPlainSocketImpl.java:188) / connect(SocksSocketImpl.java:392) / connect(Socket.java:589) / run(ConnectThread.java:146)', revision=24201)')

Regenerating policies fixed the issue

Indeed, in the upgrade log, it shows

INFO: The migration has completed successfully.
INFO: End of migration script
INFO: Restarting Rudder webapp and inventory-endpoint... Done
Setting up rudder-inventory-ldap (4.2.0~beta2-jessie0) ...
INFO: Restarting syslogd... Done
INFO: Restarting rudder-slapd... Done
Setting up rudder-inventory-endpoint (4.2.0~beta2-jessie0) ...
INFO: Launching script to check if a migration is needed
INFO: End of migration script
Setting up rudder-reports (4.2.0~beta2-jessie0) ...
INFO: Waiting for PostgreSQL to be up... Done
Setting up rudder-server-root (4.2.0~beta2-jessie0) ...
Processing triggers for libc-bin (2.19-18) ...

We are restarting rudder webapp, then rudder-slapd

Actions

Also available in: Atom PDF