nfs-kernel-server fails to start after kernel upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-utils (Ubuntu) |
Won't Fix
|
High
|
Unassigned | ||
Lucid |
Won't Fix
|
High
|
Unassigned |
Bug Description
After updating to kernel 2.6.31-
1. Log in via ssh
2. Stop nfs-kernel-server
3. Stop portmap
4. Start portmap
5. Start nfs-kernel-server
My shares are now available over my network. I have to do this any time the system is rebooted, although restarts are few and far between, there is clearly an issue here with these services. If portmap were started via /etc/init.d I could fix the problem on my own, but I find that I know nothing about upstart.
This is an Ubuntu Karmic 9.10 server with kernel 2.6.31-
Portmap is version 6.0-10ubuntu2.
Nfs-kernel-server is verison 1:1.2.0-2ubuntu8.
Before this kernel version the problem was not present. If you need more information, please feel free to ask me for it.
Changed in nfs-utils (Ubuntu Lucid): | |
assignee: | nobody → Steve Langasek (vorlon) |
Changed in nfs-utils (Ubuntu Lucid): | |
assignee: | Steve Langasek (vorlon) → nobody |
Changed in nfs-utils (Ubuntu): | |
assignee: | Steve Langasek (vorlon) → nobody |
tags: | added: thanks |
Changed in nfs-utils (Ubuntu): | |
status: | Incomplete → Triaged |
Thank you for taking the time to report this bug and help to improve Ubuntu.
What kernel version were you running before this upgrade? None of the (many!) changes in the -20 uploads look very likely to be related, so it may be that there's an underlying race condition that's aggravated by timing differences in the new kernel.
And indeed there is an underlying race condition, because /etc/init/ portmap. conf may run in parallel to /etc/init/ rc-sysinit. conf.
The correct fix is to switch nfs-kernel-server over to upstart for lucid, to eliminate the race condition. As a workaround, you can edit /etc/init/ rc-sysinit. conf on your own system, and add 'and started portmap' to the list of start conditions.