Bug 218036 - glibc won't allow portmap daemon to restart
Summary: glibc won't allow portmap daemon to restart
Keywords:
Status: CLOSED DUPLICATE of bug 217850
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-01 14:39 UTC by Paul Dickson
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-12-01 14:46:06 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.