Bug 454286
Summary: | problems bringing up lockd after it has been taken down | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Jeff Layton <jlayton> |
Component: | kernel | Assignee: | Jeff Layton <jlayton> |
Status: | CLOSED NOTABUG | QA Contact: | Martin Jenner <mjenner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | CC: | ram_kesavan, staubach, steved |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-09-29 12:02:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jeff Layton
2008-07-07 14:52:16 UTC
Actually, this doesn't appear to be a regression. When I do the same test on -8.el5, then I get these messages: lockd_up: makesock failed, error=-98 lockd_up: no pid, 2 users?? lockd_up: no pid, 3 users?? lockd_up: no pid, 4 users?? lockd_up: no pid, 5 users?? lockd_up: no pid, 6 users?? lockd_up: no pid, 7 users?? lockd_up: no pid, 8 users?? ...and lockd isn't started. Since no one has complained about this, I'll put this on 5.4 proposed for now. If the fix turns out to be simple I may move it to 5.3... This problem has strangely "fixed itself". Yesterday, I could reliably reproduce this. Today, I can't make it happen. The host where I saw this was a RHEL5 FV xen guest. It looked like the power blinked at the office and the xen dom0 rebooted. I brought my RHEL5 image back up and now this isn't happening anymore. It seems unlikely, but maybe this is something to do with being a guest on a long running dom0? I'll leave this open for now in case it happens again... Closing this out. I've not seen this problem since, though it still worries me that I saw it at all. I'll reopen it if it returns. I am not sure if this is important, but you will get this error if the portmapper is not running, start portmapper /etc/init.d/portmapper and try the mount and it will work properly. |