Bug #5020
closedUser story #4798: Upgrade to CFEngine 3.6 in rudder-agent
Debian/Ubuntu: cf-key fails in postinst with "liblmdb.so: cannot open shared object file"
Description
During post install of rudder-agent package on a Ubuntu 12.10 node I got:
/var/rudder/cfengine-community/bin/cf-key: error while loading shared libraries: liblmdb.so: cannot open shared object file: No such file or directory
I figured this out reading the postinst, which is basically:
/var/rudder/cfengine-community/bin/cf-key # Reload the linker cache (to acknowledge LMDB's presence if needed) if [ -e /etc/ld.so.conf.d/rudder.conf ]; then ldconfig; fi
The reload should come before using the program!
Updated by Jonathan CLARKE over 10 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/365/files
Updated by Jonathan CLARKE over 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:55c4c58f91cc95f655e2239c2598b42a4d3e1872.
Updated by Jonathan CLARKE over 10 years ago
- Subject changed from Debian/Ubuntu: cf-key fails in postinst because ldconfig is run too late to Debian/Ubuntu: cf-key fails in postinst with "liblmdb.so: cannot open shared object file"
Actually, I got confused, "ldconfig" is run before cf-key. I moved it up anyway, to be sure we keep it at the top.
So this bug just got weirder: ldconfig is run, but nevertheless cf-key still complains about the missing lib.
However, when I check after the installation, everything works just fine. Indeed, apt-get/aptitude re-runs the postinst script once to "try and recover", and then cf-key works perfectly.
However, when the postinst script gets re-run, many errors appear because there is no CFEngine key. I'm moving the key generation up above the cfengine restart, to avoid this, and adding debug statements to see what is going on.
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.0~beta1 that was released yesterday.
- announcement
- changelog
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/