Re: mount error 126 = Required key not available

On Wed, 03 Jun 2009 08:44:36 -0600
Jerry Litteer <[email protected]> wrote:

> I have cifs mounting working on a Ubuntu system.  When I try to transfer
> the environment/capability to Centos
> I get mount error 126 = Required key not available.
> 
> >From what I can tell I have every thing configured correctly.  When I
> try to use Google, I see alot  of  reports of the issue, but I have yet
> to see any suggestions for resolving the issue.
> 
> Here is the information from the Centos system that is failing...
> Script started on Wed 03 Jun 2009 07:54:29 AM MDT
> gll@vastest1: whatami.sh
>     CentOS release 5.3 (Final)
>     System information gathered:
>     HOSTNAME        = vastest1
>     Kernel          = 2.6.18-128.1.6.el5
>     HOST_OS_NAME    = Linux
>     HOST_OS_VERSION = 5.3
>     HOST_HARDWARE   = x86_64
> gll@vastest1: env | grep KRB
> KRB5_CONFIG=/etc/krb5.conf
> KRB5CCNAME=/tmp/krb5cc_118
> -rw------- 1 gll gll 2525 Jun  3 08:08 /tmp/krb5cc_118
> 
> gll@vastest1: ~]$/sbin/mount.cifs //fs1/home3/gll /home/gll/J: -v -o
> sec=krb5,[email protected],noauto,soft
> parsing options: sec=krb5,[email protected],noauto,soft
> 
> mount.cifs kernel mount options
> unc=//fs1\home3,ip=134.20.19.122,ver=1,sec=krb5,[email protected],noauto,soft,uid=118,gid=118,prefixpath=gll
> 
> mount error 126 = Required key not available
> Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
> Mount of  //fs1.inel.gov/home3/gll /home/gll/J: failed
> 
> gll@vastest1: dmesg
>  fs/cifs/cifssmb.c: Dialect: 2
>  fs/cifs/asn1.c: OID len = 7 oid = 0x1 0x2 0x348 0xbb92
>  fs/cifs/asn1.c: OID len = 7 oid = 0x1 0x2 0x348 0x1bb92
>  fs/cifs/asn1.c: OID len = 8 oid = 0x1 0x2 0x348 0x1bb92
>  fs/cifs/asn1.c: OID len = 10 oid = 0x1 0x3 0x6 0x1
>  fs/cifs/asn1.c: Need to call asn1_octets_decode() function for
> [email protected]
>  fs/cifs/cifssmb.c: Signing disabled
>  fs/cifs/cifssmb.c: negprot rc 0
>  fs/cifs/connect.c: Security Mode: 0x3 Capabilities: 0x8001f3fd
> TimeAdjust: 21600
>  fs/cifs/sess.c: sess setup type 7
>  fs/cifs/cifs_spnego.c: key description =
> ver=0x2;host=fs1.inel.gov;ip4=134.20.19.122;sec=mskrb5;uid=0x76;user=gll
>  fs/cifs/sess.c: ssetup freeing small buf ffff81006c3cd300
>  CIFS VFS: Send error in SessSetup = -126
>  fs/cifs/connect.c: cifsd thread killed
>  fs/cifs/connect.c: No session or bad tcon
>  fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 12) rc = -126
>  CIFS VFS: cifs_mount failed w/return code = -126
> Script  ended
> *linux-cifs module parameters>*
> 
> /proc/fs/cifs/cifsFYI = 3
> /proc/fs/cifs/DebugData: CIFS Version 1.54RH
> /proc/fs/cifs/Experimental = 0
> /proc/fs/cifs/LinuxExtensionsEnabled = 1
> /proc/fs/cifs/LookupCacheEnabled = 1
> /proc/fs/cifs/MultiuserMount = 0
> /proc/fs/cifs/OplockEnabled = 1
> /proc/fs/cifs/SecurityFlags = 0x7
> /proc/fs/cifs/traceSMB = 0
> 
> *SUCESSFULL* execution on Ubuntu (8.04, 2.6.24-24-generic, CIFS Version
> 1.52)
> [326461.025812]  /build/buildd/linux-2.6.24/fs/cifs/cifs_spnego.c: key
> description = ver=0x1;host=fs1.inel.gov;ip4=134.20.19.122;sec=krb5;uid=0x3e8
> 
> I noticed in the  /fs/cifs/cifs_spnego.c: key description
> ver on the Centos (RH) box is =0x2 and =0x1 on the Ubuntu box.  
> sec parameter on the Centos system is =mskrb5  and =krb5 on the Ubuntu
> system.
> 
> Both systems are trying to mount the same share from the same file
> server and are using the same AD's.
> 
> 

What does your /etc/request-key.conf look like on the Centos machine?

-- 
Jeff Layton <[email protected]>