Bug 218036

Summary: glibc won't allow portmap daemon to restart
Product: [Fedora] Fedora Reporter: Paul Dickson <paul>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-01 14:46:06 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 Paul Dickson 2006-12-01 14:39:07 UTC 
Description of problem:
After installing the latest glibc, if the portmap daemon is restarted (or
started) it will fail:
  "Cannot register service: RPC: Unable to receive; errno = Connection refused
   not registered:     100000    2   tcp   111   portmapper"
The above repeats for 25 more services.

Version-Release number of selected component (if applicable):
glibc-2.5.90-8

How reproducible:
Always

Steps to Reproduce:
1. sudo service portmap restart
2.
3.
  
Actual results:
First time will succeed, but each successive run will have a FAIL for shutdown.

Expected results:
OKs for both shutdown and startup.

Additional info:
This must be done for each NFS client and server to get the portmap daemon
running.  On the server, the nfs daemon must be restarted.

Wireshark is reporting checksum errors for each V2 GETPORT Reply.  It works
anyway so this might be a wireshark bug.
Comment 1 Jakub Jelinek 2006-12-01 14:46:06 UTC 

*** This bug has been marked as a duplicate of 217850 ***