connect to nfs-Server fails with 2.6.32-33-Kernel

Bug #812166 reported by lygie
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
portmap (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After upgrading to Kernel 2.6.32-33-Server on Ubuntu 10.04, i am not longer able to mount a NFS-device.

When I try to mount the device i get

mount.nfs: access denied by server while mounting

syslog says:

connect from xxx.xxx.xxx.xxx to unset(nlockmgr): request from non-local host
 kernel: [ 924.940350] svc: failed to register lockdv1 RPC service (errno 13).

if i try mount -o nomount, everything is fine.

When I boot the Kernel 2.6.32-32 everything is fine, too. So NFS and Network-configuration seems correct.

Tags: lucid
Revision history for this message
lygie (tobias-eichelbroenner) wrote :

sorry, there was an error in my report:

mount -o nolock

is working. The line above makes no sense.

Revision history for this message
Joe Burgess (joemburgess) wrote :

So the server is on 2.6.32-33-Server correct?

Any when you get that error message it's coming from the nfs client correct? Have you tried different clients?

affects: ubuntu → nfs-utils (Ubuntu)
Revision history for this message
Steve Langasek (vorlon) wrote :

If this changed when upgrading the kernel, this bug should obviously be reported against the kernel, not against nfs-utils.

affects: nfs-utils (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in dianosing the problem. From a terminal window please run:

apport-collect 812166

and then change the status of the bug back to 'New'. If, due to the nature of the issue you have encountered, are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Brad Figg (brad-figg)
tags: added: lucid
Revision history for this message
lygie (tobias-eichelbroenner) wrote :

Hallo Brad Figg,
can you name some specific information you need?

The system is in use and i can not submit data automatically for security policy.

If collected information via apport-collect is necessary, i would have to rebuild the setup in an testing environment. But i won't be able to to this until the day after tomorrow.

Sincerely

Revision history for this message
lygie (tobias-eichelbroenner) wrote :

Sorry, for the delay,

i spend the last days trying to reproduce the problem.
There are some information i have found:

1) the problem has nothing to do with the kernel
2) the problem occurs randomly after i reboot the system. That was the reason i first got the impression, that the kernel version has something to do with this
3) the problem occurs at the time when portmap is checking for valid local hosts. This happens in the good_client function in pmap_check.c if i patch portmap so that it always returns true everything is fine
4) i can reproduce the problem if i bring up and down network devices on a running system
5) stopping portmap and starting it again solves the problem. (restart does not help)

My conclusion is, that there is a Problem while upstarting portmap. This would explain, why rebooting the systems sometimes help, and sometimes it does not.

affects: linux (Ubuntu) → portmap (Ubuntu)
Changed in portmap (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

Joe, this is not a portmap change. Please stop reassigning this bug to the wrong package.

affects: portmap (Ubuntu) → linux (Ubuntu)
Revision history for this message
Steve Langasek (vorlon) wrote :

Sorry, should have read the latest bug log entry more closely. Ok, if it's not tied to a kernel version, then this may indeed be a portmap bug.

affects: linux (Ubuntu) → portmap (Ubuntu)
Revision history for this message
Steve Langasek (vorlon) wrote :

lygie, please attach the /etc/hosts and /etc/nsswitch.conf files from the affected system.

Revision history for this message
lygie (tobias-eichelbroenner) wrote :

here is the nsswitch-File

Revision history for this message
lygie (tobias-eichelbroenner) wrote :

and the hosts

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 812166] Re: connect to nfs-Server fails with 2.6.32-33-Kernel

On Sun, Jul 24, 2011 at 09:57:34AM -0000, lygie wrote:
> and the hosts

This shows the following:

127.0.0.1 localhost
127.0.1.1 web02

What is the hostname of this system, as returned by 'hostname -f'? Is it
'web02' as shown in /etc/hosts, or does it have a domain name attached to
it?

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

Revision history for this message
lygie (tobias-eichelbroenner) wrote :

Hallo Steve,

yes, hostname and entries in /etc/hosts match

Revision history for this message
Steve Langasek (vorlon) wrote :

On Mon, Jul 25, 2011 at 07:30:20AM -0000, lygie wrote:
> yes, hostname and entries in /etc/hosts match

Just to be clear, by "match", you mean that the output of 'hostname -f' is
'web02', with no domain name appended?

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for portmap (Ubuntu) because there has been no activity for 60 days.]

Changed in portmap (Ubuntu):
status: Incomplete → Expired
Changed in portmap (Ubuntu):
status: Expired → New
Steve Langasek (vorlon)
Changed in portmap (Ubuntu):
status: New → Incomplete
Changed in portmap (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.