SASL-Plugins not found, path mismatch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fedora Directory Server |
Fix Released
|
Unknown
|
|||
389-ds-base (Ubuntu) |
Fix Released
|
Medium
|
Timo Aaltonen | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
Quantal |
Won't Fix
|
Undecided
|
Unassigned | ||
Raring |
Won't Fix
|
Undecided
|
Unassigned | ||
Saucy |
Fix Released
|
Medium
|
Timo Aaltonen |
Bug Description
I tried to enable SASL GSSAPI-Support in 389-ds but a ldapsearch on supportedSASLMe
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/
Check:
root@ldap-
dn:
supportedSASLMe
supportedSASLMe
supportedSASLMe
supportedSASLMe
supportedSASLMe
supportedSASLMe
supportedSASLMe
supportedSASLMe
supportedSASLMe
supportedSASLMe
supportedSASLMe
I think it's not a big deal to fix this but I have no time to do it myself.
Regards
Mathias Kaufmann
Changed in fedora-ds: | |
status: | Unknown → Confirmed |
Changed in fedora-ds: | |
status: | Confirmed → Fix Released |
confirmed, it's hardcoded in the source, if the path is not set in the config.
we'd need to make the default build-time configurable, so that it would use the triplet path of the builder arch.