Bug 1314521
Summary: | autofs+cifs+kerberos fails to mount cifs-shares with error 5 - IO-Error | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Thomas Schweikle <tschweikle> |
Component: | autofs | Assignee: | Ian Kent <ikent> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | ikent, tschweikle |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-20 19:13:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Thomas Schweikle
2016-03-03 20:09:31 UTC
I've enabled debugging for autofs, setting "--debug" in /etc/sysconfig/autofs OPTIONS. Here is what I see using smbclient to access one of the shares: # kinit <user> Password for <user>@<realm>: Warning: Your password will expire in 16 days on Sun Mar 20 15:46:57 2016 # klist Ticket cache: FILE:/tmp/krb5cc_10947_h4oeCY Default principal: <user>@<realm> Valid starting Expires Service principal 03/03/16 21:14:17 03/04/16 07:14:17 krbtgt/<realm>@<realm> renew until 03/10/16 21:14:12 # smbclient -k //<server>/Allg session setup failed: NT_STATUS_MORE_PROCESSING_REQUIRED did you forget to run kinit? # klist Ticket cache: FILE:/tmp/krb5cc_10947_h4oeCY Default principal: <user>@<realm> Valid starting Expires Service principal 03/03/16 21:14:17 03/04/16 07:14:17 krbtgt/<realm>@<realm> renew until 03/10/16 21:14:12 03/03/16 21:14:21 03/04/16 07:14:17 cifs/<server>@<realm> renew until 03/10/16 21:14:12 # echo $KRB5CCNAME FILE:/tmp/krb5cc_10947_h4oeCY The same setup does work with: - Debian stable, testing, unstable - Ubuntu 14.04.4 LTS - FreeBSD CURRENT (quite different in setup, because FreeBSD doesn't know about multimaps :-( ) -- but works too. Here is what I see connecting to my server from Ubuntu 14.04.4 LTS: -- snip $ kinit <user> Password for <user>@<realm>: Warning: Your password will expire in 16 days on So 20 Mär 2016 15:46:57 CET $ klist Ticket cache: FILE:/tmp/krb5cc_10947 Default principal: <user>@<realm> Valid starting Expires Service principal 03.03.2016 21:38:29 04.03.2016 07:38:29 krbtgt/<realm>@<realm> renew until 10.03.2016 21:38:14 $ smbclient -k //<server>/<user> Domain=[BFS] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] smb: \> ls desktop.ini AHS 80 Tue Nov 27 14:58:16 2012 Documents DR 0 Wed Jan 20 16:19:38 2016 Safes D 0 Tue Sep 10 16:54:58 2013 upcp.sh A 0 Tue May 27 16:53:46 2014 [...] 40960 blocks of size 262144. 40194 blocks available smb: \> q $ klist Ticket cache: FILE:/tmp/krb5cc_10947 Default principal: <user>@<realm> Valid starting Expires Service principal 03.03.2016 21:38:29 04.03.2016 07:38:29 krbtgt/<realm>@<realm> renew until 10.03.2016 21:38:14 03.03.2016 21:38:46 04.03.2016 07:38:29 cifs/<server>@<realm> renew until 10.03.2016 21:38:14 $ kdestroy -- snap (In reply to Thomas Schweikle from comment #1) > I've enabled debugging for autofs, setting "--debug" in > /etc/sysconfig/autofs OPTIONS. > > Here is what I see using smbclient to access one of the shares: > # kinit <user> > Password for <user>@<realm>: > Warning: Your password will expire in 16 days on Sun Mar 20 15:46:57 2016 > > # klist > Ticket cache: FILE:/tmp/krb5cc_10947_h4oeCY > Default principal: <user>@<realm> > > Valid starting Expires Service principal > 03/03/16 21:14:17 03/04/16 07:14:17 krbtgt/<realm>@<realm> > renew until 03/10/16 21:14:12 > > # smbclient -k //<server>/Allg > session setup failed: NT_STATUS_MORE_PROCESSING_REQUIRED > did you forget to run kinit? I think these in the log of comment #0: Mar 3 20:58:25 atmosrv3-fr kernel: CIFS VFS: Send error in SessSetup = -5 Mar 3 20:58:25 atmosrv3-fr automount[9373]: >> mount error(5): Input/output error Mar 3 20:58:25 atmosrv3-fr automount[9373]: >> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and the above from smbclient is fairly clear evidence the CIFS client is the problem with your setup. But I suspect the CIFS maintainer will be equally mystified as I am as to why. I have a similar report against autofs but for authentication to a Windows server for accessing autofs maps. It's the same more precessing type message as you see here with smbclient. I know with some other (apparently unrelated) problems it was apparent some of the underlying libraries have changed away from using OpenSSL and I think this has affected openldap for one, which autofs uses, and those same libraries may be used by the CIFS kernel callback program and smbclient. I don't know what libraries the CIFS executables use so I don't know if the problem is related. Are you ok to change the component to cifs-utils to get input for the CIFS maintainer? Ian Had to do other work with higher priority in between ... back to this now. I've found various bug reports about this problem related to the kernel on launchpad (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1373473). I've tried newer and older kernel to verify against. Kernel from elrepo -- with an up to date system: - 4.5.2-1.el6.elrepo.x86_64: mount error - IO-Error. - 3.10.101-1.el6.elrepo.x86_64: mount error - IO-Error. - 3.8.13-118.4.2.el6uek.x86_64: mount error - IO-Error. - 3.8.13-118.4.1.el6uek.x86_64: mount error - IO-Error. - 3.8.13-118.3.2.el6uek.x86_64: mount error - IO-Error. - 2.6.32-573.22.1.el6.x86_64: mount error - IO-Error. - 2.6.32-573.18.1.el6.x86_64: mount error - IO-Error. - 2.6.32-573.12.1.el6.x86_64: mount error - IO-Error. From the last DVD for CentOS 6: - it is working. Upgrading only kernels breaks it. Going back to an older one makes it work again. - Updating libraries used by cifs breaks it too. Going pack to older ones makes it work again. Think it is something all over together: cifs-utils, libraries, and final the kernel which changed. all together break cifs-mounts. But I am clueless what exactly could be the case why it is broken at now. I've even tried to recompile all of them -- whithout success. Same error. Found it broken with: - Redhat 6, 7 - CentOS 6, 7 - Oracle Linux 6, 7 - Fedora (all supported versions) - Ubuntu 14.04, 15.10, 16.04, (upcoming) 16.10 All up to date. Found it working: - Redhat 6, 7 (original DVD install image or media) - Centos 6, 7 (original DVD install image or media) This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |