ubuntu-389-directory-server team mailing list archive

[Andrew Bork <anbork@xxxxxxxxx>]

I am seeing the same issue as David on Ubuntu  armbian on an orange PI
+2e. It's armv7h my symlink that fixed it was

ln -s /usr/lib/arm-linux-gnueabihf/sasl2/ /usr/lib/sasl2

-- 
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-ds-base in Ubuntu.
https://bugs.launchpad.net/bugs/1088822

Title:
  SASL-Plugins not found, path mismatch

Status in Fedora Directory Server:
  Fix Released
Status in 389-ds-base package in Ubuntu:
  Fix Released
Status in 389-ds-base source package in Precise:
  Confirmed
Status in 389-ds-base source package in Quantal:
  Won't Fix
Status in 389-ds-base source package in Raring:
  Won't Fix
Status in 389-ds-base source package in Saucy:
  Fix Released

Bug description:
  I tried to enable SASL GSSAPI-Support in 389-ds but a ldapsearch on
  supportedSASLMechanisms keeps give me SASL EXTERNAL only. I looked
  into /var/log/auth.log and found this:

  Dec 11 10:08:06 ldap-01 ns-slapd: looking for plugins in
  '/usr/lib64/sasl2', failed to open directory, error: No such file or
  directory

  The quick fix with symlinking like below fixed the problem.

  ln -s /usr/lib/x86_64-linux-gnu /usr/lib64

  Check:

  root@ldap-01:/usr/lib64/sasl2# ldapsearch -h localhost -p 389 -x -b "" -s base -LLL supportedSASLMechanisms                                                                                                                           
  dn:
  supportedSASLMechanisms: EXTERNAL
  supportedSASLMechanisms: GS2-IAKERB
  supportedSASLMechanisms: GS2-KRB5
  supportedSASLMechanisms: SCRAM-SHA-1
  supportedSASLMechanisms: GSSAPI
  supportedSASLMechanisms: DIGEST-MD5
  supportedSASLMechanisms: NTLM
  supportedSASLMechanisms: CRAM-MD5
  supportedSASLMechanisms: PLAIN
  supportedSASLMechanisms: LOGIN
  supportedSASLMechanisms: ANONYMOUS

  I think it's not a big deal to fix this but I have no time to do it
  myself.

  Regards
  Mathias Kaufmann

To manage notifications about this bug go to:
https://bugs.launchpad.net/fedora-ds/+bug/1088822/+subscriptions