Project

General

Profile

Actions

Bug #5015

closed

User story #4928: Allow splitting Rudder into independent role-based entities

LDAP libraries installed by rudder-inventory-ldap conflict with system libraries

Added by Nicolas CHARLES about 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
1
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

I ran the rudder-init script, and it failed to add data in the ldap tree
Here is the complete output of the execution

grep: /opt/rudder/share/webapps/rudder.xml: No such file or directory

Welcome to the Rudder initialization utility

This utility configures a Rudder root server, and may be
called again if reconfiguration is required.

Please enter the fully qualified domain name that will be used to access the web interface of the Rudder server (i.e rudder.example.com): rudder-snapshot-2.11
Enter network allowed to access server (i.e 192.168.0.0/24): 192.168.0.0/16
192.168.0.0/16
Network(s) added:
192.168.0.0/16
Add more networks? (yes/no) no
no

Do you want to add sample data (for demos)? (yes/no) yes
yes

Do you want to reset initial promises ? (yes/no) no
no

Hostname: rudder-snapshot-2.11
Allowed networks: 192.168.0.0/16
Add sample data? yes
Reset Initial Promises? no

Hit any key to continue....
Initializing LDAP database...ERROR: Execution failed! Aborting.
An error occured. Please check /tmp/rudder.JmAKNBJm3D.log for details.

Actions #1

Updated by Jonathan CLARKE about 8 years ago

  • Subject changed from rudder-init.sh script fails to LDAP libraries installed by rudder-inventory-ldap conflict with system libraries
  • Category set to System integration
  • Status changed from New to In progress

The actual error that causes rudder-init to halt is:

ldapadd: /opt/rudder/lib/liblber-2.4.so.2: no version information available (required by ldapadd)
ldapadd: /opt/rudder/lib/libldap-2.4.so.2: no version information available (required by ldapadd)
LDAP vendor version mismatch: library 20430, header 20423

This happens because the system-installed ldapadd command is using the shared LDAP libraries provided by rudder-inventory-ldap, which are in a different version. We should not be sharing our libraries to the world, since we only install these to ensure the base system works. This only occured recently, because Rudder 2.11 introduces LMDB support, which caused us to add the /opt/rudder/lib to ldconfig's path, but that directory not only includes LMDB libraries, but also the LDAP libraries.

Simple solution for now is to move the LDAP libraries to /opt/rudder/lib/ldap, thus avoiding ldconfig indexing them.

Actions #2

Updated by Jonathan CLARKE about 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/368
Actions #3

Updated by Jonathan CLARKE about 8 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset packages:commit:95e1058cadadcb7e3c95298f810046b5a8b462b2.

Actions #4

Updated by Vincent MEMBRÉ about 8 years ago

  • Parent task set to #4928
Actions #5

Updated by Vincent MEMBRÉ about 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.0~beta1 that was released yesterday.

Actions

Also available in: Atom PDF