| Summary: | net-fs/autofs: ldaps broken, needs to link with krb5 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jonas Jonsson <jonas> |
| Component: | Current packages | Assignee: | Stefaan De Roeck (RETIRED) <stefaan> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | DuPol, net-fs, patil.nikhil, pva, spookyghost |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 346537 | ||
| Bug Blocks: | |||
|
Description
Jonas Jonsson
2009-09-16 16:03:25 UTC
I can confirm the bug with [automount] get_proximity:200: socket creation failed: Invalid argument with 5.0.4-r5, interestingly it happened when connecting to an nfs mount. Connecting to a cifs share succeeded. Googling indicates that this is fixed in a newer kernel, my current kernel 2.6.25-gentoo-r6 Sep 8 13:33:19. I will try a new kernel with next reboot. Quote from Mandriva.com: --- Comment #3 from wim.vanderbauwhede@ 2009-08-16 10:49:27 CEST --- I can confirm that with the latest version of the kernel, the bug has indeed been resolved. Wim from http://lists.mandriva.com/bugs/2009-08/msg01489.php I can confirm that updating the kernel resolves the [automount] get_proximity:200: socket creation failed: Invalid argument issue. 2.6.31-gentoo-r6 #4 SMP Wed Jan 13 22:21:30 GMT 2010 i686 However I still can't see shares on nfs, falling back to 5.0.3-r6 for now as it is working. (In reply to comment #2) > However I still can't see shares on nfs, falling back to 5.0.3-r6 for now as it > is working. Daren, could you please test autofs-5.0.5 and report back whether this is still an issue? I am experiencing similar problems after a recent autofs upgade. I have tested autofs-5.0.5 with the results:
Jun 24 15:31:12 [automount] open_lookup:90: cannot open lookup module ldap (/usr/lib64/autofs/lookup_ldap.so: undefined symbol: krb5_princ_realm)
lookup_ldap.so is not linked against any kerberos libraries:
$ ldd /usr/lib64/autofs/lookup_ldap.so
linux-vdso.so.1 => (0x00007fff572e5000)
libldap-2.4.so.2 => /usr/lib/libldap-2.4.so.2 (0x00007fbab8b79000)
liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0x00007fbab896a000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00007fbab8752000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x00007fbab8536000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00007fbab81b2000)
libz.so.1 => /lib/libz.so.1 (0x00007fbab809b000)
libm.so.6 => /lib/libm.so.6 (0x00007fbab7e18000)
libc.so.6 => /lib/libc.so.6 (0x00007fbab7abc000)
libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0x00007fbab7867000)
libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0x00007fbab74d1000)
libdl.so.2 => /lib/libdl.so.2 (0x00007fbab72cd000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007fbab7094000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbab9002000)
According to http://bugs.archlinux.org/task/15654 krb5_princ_realm is also a deprecated interface. I can work around the problems I have with USE=-sasl.
(In reply to comment #4) > I am experiencing similar problems after a recent autofs upgade. I have tested > autofs-5.0.5 with the results: Please see bug 302377 and the proposed patch. Please report back whether it solves your issue. If so, I will use this bug for the nfs issue mentioned in comment #2. I had the same problem and the fix of bug #302377 works for me (with autofs-5.0.4-r5). Patch was added in 5.0.5-r1. Fixed. |
