Home > State Manager > Kernel Error State Manager Failed On Nfsv4 Server

Kernel Error State Manager Failed On Nfsv4 Server

Status Importance Assigned to Milestone linux (Ubuntu) Edit Invalid Low Unassigned Edit You need to log in to change nfs: state manager: check lease failed on nfsv4 server with error 5 this bug's status. Affecting: linux (Ubuntu) Filed here by: Arne Christensen

State Manager Failed On Nfsv4 Server With Error 5

When: 2009-11-07 Completed: 2010-02-10 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux check lease failed on nfsv4 server with error 13 nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Low Assigned to Nobody Me Comment on this change nfs state manager check lease failed on nfsv4 server with error 10008 (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Even after applying kernel patches as described in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/379385 I occasionally experience the following problem on my nfs4 client computer. "Occasionally" means that recently (and according to syslog) it happened on Oct 14, Nov 3,

Kernel: Nfs: State Manager: Check Lease Failed On Nfsv4 Server

Nov 4 and Nov 7. It typically happens after the nfs4 client computer goes out of sleep. I understand why sleep may upset the nfs connection, but it clearly recovers "most of the time". The computers serving as nfs4 client and server both run a fully updated Jaunty (09.04). Exception: The client is a few security patches behind because I'm running a home-built kernel with the patch mentioned in http://bugzilla.kernel.org/attachment.cgi?id=18427 (comment #19). The problem is that nfs4 locks up so that all accesses to my nfs4 mount point get delayed indefinitely, with no way of interrupting it. syslog from a typical failure is: Nov 3 07:07:41 helle kernel: [13262.273844] WARNING: at kernel/power/main.c:177 suspend_test_finish+0x80/0x90() Nov 3 07:07:41 helle kernel: [13262.273847] Component: resume devices Nov 3 07:07:41 helle kernel: [13262.273851] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat usb_storage i915 drm binfmt_misc bridge stp bnep input_polldev video output nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc ipt_REJECT ipt_LOG xt_limit xt_tcpudp xt_state ipt_addrtype ip6table_filter ip6_tables nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_nat nf_conntrack_ipv4 nf

Forgot Password Login: [x] Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next nfsv4 error 5 This bug is not in your last search results. Bug885514 - NFS: nfs state manager error 13 state manager: check lease failed on NFSv4 server filehost with error 93 Summary: NFS: state manager: check lease

Nfs State Manager Lease Expired Failed On Nfsv4 Server

failed on NFSv4 server filehost with error 93 Status: CLOSED WONTFIX Aliases: None Product: Fedora Classification: Fedora Component: kernel (Show other bugs) Sub Component: --- Version: 17 Hardware: Unspecified https://bugs.launchpad.net/bugs/477711 Unspecified Priority unspecified Severity unspecified TargetMilestone: --- TargetRelease: --- Assigned To: nfs-maint QA Contact: Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2012-12-09 18:21 EST by Tethys Modified: 2013-08-01 01:38 EDT (History) CC List: 7 users (show) gansalmon gothmog itamar jonathan kernel-maint madhu.chinakonda rwheeler See Also: Fixed In Version: https://bugzilla.redhat.com/show_bug.cgi?id=885514 Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2013-08-01 01:38:06 EDT Type: Bug Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Tethys 2012-12-09 18:21:34 EST Description of problem: My desktop is an NFS client, with my home directory on a server. Hardware failures forced a reinstall of both server and client, and now my desktop machine is painfully slow. The log file shows that the client is getting the following error once every 5 seconds: Dec 9 23:06:58 leto kernel: [714958.020911] NFS: state manager: check lease failed on NFSv4 server filehost with error 93 This is accompanied by two error lines on the server: Dec 9 23:06:58 riva kernel: svc:, port=813: unknown version (4 for prog 100003, nfsd) Dec 9 23:06:58 riva kernel: svc:, port=813: unknown version (4 for prog 100003, nfsd) Error 93 appears to be "versi

Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us http://serverfault.com/questions/798599/nfs-state-manager-check-lease-failed Learn more about Stack Overflow the company Business Learn more about hiring developers or https://lists.ubuntu.com/archives/foundations-bugs/2011-July/010415.html posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and state manager rise to the top NFS: state manager: check lease failed up vote 0 down vote favorite I've a NFS share mounted on a Linux (3.16.0-4) Server. The NFS service is marketed as "HA" by the service provided. Aug 21 05:50:10 srv01 kernel: [2314509.701050] NFS: state manager: check lease failed on NFSv4 server with error 93. I manually umounted and remounted the share. What went wrong? Any suggestion failed on nfsv4 ? linux nfs share|improve this question asked Aug 23 at 14:25 Jack L. G. 12 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote The error 93 stands for EPROTONOSUPPORT (/usr/include/asm-generic/errno.h) and here is a possible reason for getting that: NFS server host reboots. The rpcbing server started but tare are no entries in it yet. Then nfs service starts and reristers v3 and v4 protocols. There is a short time window, where client will ask rpcbind for v4 port, but will get that nfsv4 protocol is not supported, as there only v3 is registered. Again, this is a possible, but not necessary actual, reason of getting error you have seen. share|improve this answer answered Sep 8 at 12:43 kofemann 1,418817 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged linux nfs or ask your own question. asked 1 month ago viewe

spam Next message: [Bug 293705] Re: expired kerberos credentials cause significant syslog spam Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Launchpad has imported 7 comments from the remote bug at https://bugzilla.novell.com/show_bug.cgi?id=620066. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2010-07-06T12:05:34+00:00 Mika Fischer wrote: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100628 Ubuntu/10.04 (lucid) Firefox/3.6.6 SSH by default deletes Kerberos credentials when a user logs out. If the user left a program running (for instance via screen), and if Kerberos credentials are needed to access the home directories (kerberized NFS), rpc.gssd will fail to obtain Kerberos credentials. The problem is that it generates excessive amounts of warnings in the syslog to this effect (about 1100 wrnings per second), which then quickly fill up the hard drive. Reproducible: Always Steps to Reproduce: 1. Log in (via SSH) to host that mounts home directory via kerberized NFS 2. Start screen with some process accessing the home dir inside 3. Detach screen 4. Close SSH session 5. Wait for rpc.gssd credentials cache to expire Actual Results: When the process still running on the target host tries to access the home directory, rpc.gssd will try and fail to obtain kerberos credentials for the user. It will then spam the syslog with the following warning ---- rpc.gssd[]: WARNING: Failed to create krb5 context for user with uid for server ---- This is repeated ad infinitum until the offending process is killed manually. The logfile otherwise quickly fills up the partition. Expected Results: Maybe one warning or no warning at all should be emitted (the latter is the case for *expired* credentials). See also https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/293705 for the case of expired credentials. A fix fo this should probably also be coordinated with upstream. Reply at: https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/293705/comments/25 ------------------------------------------------------------------------ On 2010-07-29T06:45:48+00:00 Sjayaraman wrote: Thanks for the bug report. This issue has been already fixed in upstream. I have bu

No related pages.