"Young, Darren" <[EMAIL PROTECTED]> writes: > Apr 24 14:35:33 gsbtestfilervm automount[8138]: Starting automounter > version 5.0.1-0.rc2.55, master map auto.master > > On: > > [EMAIL PROTECTED] log]# cat /etc/redhat-release > Red Hat Enterprise Linux Server release 5.1 (Tikanga) > > Added daemon.* to syslog and started autofs: > > Apr 24 14:47:16 gsbtestfilervm automount[8283]: parse_ldap_config: ldap > authentication configured with the following options: > Apr 24 14:47:16 gsbtestfilervm automount[8283]: parse_ldap_config: > use_tls: 0, tls_required: 0, auth_required: 2, sasl_mech: DIGEST-MD5 > Apr 24 14:47:16 gsbtestfilervm automount[8283]: parse_ldap_config: user: > cn=Directory Manager, secret: specified, client principal: (null) > Apr 24 14:47:16 gsbtestfilervm automount[8283]: sasl_bind_mech: > Attempting sasl bind with mechanism DIGEST-MD5 > Apr 24 14:47:16 gsbtestfilervm automount[8283]: sasl_log_func: No worthy > mechs found > Apr 24 14:47:16 gsbtestfilervm automount[8283]: sasl_bind_mech: > sasl_client start failed with error: SASL(-4): no mechanism available: > No worthy mechs found
Hmm. Do you have the cyrus-sasl-md5 package installed? rpm -q cyrus-sasl-md5 will tell you. If so, then can you get a packet capture during the autofs start (and failure)? Be sure to capture packet data by specifying a snaplen of 0 if using tcpdump. Thanks! Jeff _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
