Bug 166918
Summary: | ypserv and mountd sometimes fails to start during boot up | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | cfeist, roth, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | FC5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-19 10:37:49 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
Alexandre Oliva
2005-08-27 18:55:33 UTC
This morning, nfs mountd failed to come up, for identical reasons. He's what the logs have to say: Sep 2 06:39:43 emilia rpc.mountd: unable to register (mountd, 1, udp). Sep 2 06:39:43 emilia portmap[17839]: connect from 127.0.0.1 to set(mountd): request from unprivileged port I doubt this is a problem in portmap. Could it be something wrong in glibc's privileged port binding request, or in the client side of portmap registration or something like that? Are a large number of NFS mounts happen at the same time? Certainly not at the time ypserv is started. Not sure whether you mean client or server mounts, so I'll answer both. This is an NIS and NFS server used by about a dozen other boxes, so when NFS starts up, it is possible that other boxes are attempting to NFS mount from it, or to restore NFS mounts from before the server's reboot. It doesn't have any NFS mounts specified in /etc/fstab, and it shouldn't need any external NFS servers to boot up, even though autofs will mount from external servers on demand. But that's after ypserv has successfully started, since all external autofs mounts are specified in NIS maps. Currently, I would say that rpc.mountd fails to start 90% of the time now for me. This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks. I think this was an SELinux issue that was fixed at least in FC5+. |