818246 – authconfig --update/--updateall restarts rpcbind, which forgets all about registered services.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 818246 - authconfig --update/--updateall restarts rpcbind, which forgets all about registered services.

Summary: authconfig --update/--updateall restarts rpcbind, which forgets all about reg...

Keywords:
Status:	CLOSED CURRENTRELEASE
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	authconfig
Sub Component:
Version:	6.4
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Tomas Mraz
QA Contact:	BaseOS QE - Apps
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2012-05-02 14:52 UTC by Lars Kellogg-Stedman
Modified:	2014-11-05 13:42 UTC (History)
CC List:	0 users
Fixed In Version:	authconfig-6.1.12-19.el6
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2014-11-05 13:42:18 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Lars Kellogg-Stedman 2012-05-02 14:52:38 UTC

Description of problem:

Running "authconfig" with the --update or --updateall flags will, in a NIS environment, restart the "rpcbind" service. This causes rpcbind to forget about all RPC services that have registered with it, which is a particular problem in an NFS environment.  After running authconfig, rpc.statd will no longer be visible to NFS services, so subsequent mount operations will spawn an instance of "rpc.statd --no-notify".

For example, before running authconfig:

  # rpcinfo -p
     program vers proto   port  service
      100000    4   tcp    111  portmapper
      100000    3   tcp    111  portmapper
      100000    2   tcp    111  portmapper
      100000    4   udp    111  portmapper
      100000    3   udp    111  portmapper
      100000    2   udp    111  portmapper
      100007    2   udp    784  ypbind
      100007    1   udp    784  ypbind
      100007    2   tcp    787  ypbind
      100007    1   tcp    787  ypbind
      100024    1   udp    662  status
      100024    1   tcp    662  status

After running authconfig:

  # authconfig --updateall
  Starting rpcbind:                                          [  OK  ]
  Shutting down NIS service:                                 [  OK  ]
  Starting NIS service:                                      [  OK  ]
  Binding NIS service: .                                     [  OK  ]
  # rpcinfo -p
     program vers proto   port  service
      100000    4   tcp    111  portmapper
      100000    3   tcp    111  portmapper
      100000    2   tcp    111  portmapper
      100000    4   udp    111  portmapper
      100000    3   udp    111  portmapper
      100000    2   udp    111  portmapper
      100007    2   udp    880  ypbind
      100007    1   udp    880  ypbind
      100007    2   tcp    883  ypbind
      100007    1   tcp    883  ypbind

At this point, it is necessary to also restart the "nfslock" service in order to re-register rpc.statd with rpcbind:

  # service nfslock restart
  Stopping NFS locking:                                      [  OK  ]
  Stopping NFS statd:                                        [  OK  ]
  Starting NFS statd:                                        [  OK  ]
  # rpcinfo -p
     program vers proto   port  service
      100000    4   tcp    111  portmapper
      100000    3   tcp    111  portmapper
      100000    2   tcp    111  portmapper
      100000    4   udp    111  portmapper
      100000    3   udp    111  portmapper
      100000    2   udp    111  portmapper
      100007    2   udp    880  ypbind
      100007    1   udp    880  ypbind
      100007    2   tcp    883  ypbind
      100007    1   tcp    883  ypbind
      100024    1   udp    662  status
      100024    1   tcp    662  status

Comment 2 Tomas Mraz 2012-05-02 15:48:16 UTC

Can you please report the issue using the regular support channels? http://www.redhat.com/support/

It will help properly prioritizing the fix for the issue.

Comment 3 Lars Kellogg-Stedman 2012-05-02 16:13:17 UTC

I'm not entirely sure what you're asking.  

We've dealt with this problem locally, and I'm not looking for any sort of support.  I'm just trying to be a good citizen, figuring that reporting this bug will prevent it from biting someone else someday.

Comment 4 RHEL Program Management 2012-09-07 05:26:10 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 5 Lars Kellogg-Stedman 2012-10-11 13:04:15 UTC

I'm marking my own report WONTFIX since it's clear RedHat has no interest in this problem.  Sorry for bothering you.

Comment 6 Lars Kellogg-Stedman 2012-10-11 13:04:41 UTC

Hmmm, maybe I can't do that.

Comment 7 RHEL Program Management 2013-10-14 00:40:55 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 8 Tomas Mraz 2014-11-05 13:42:18 UTC

I believe this bug is already fixed in the current authconfig in RHEL-6

Note You need to log in before you can comment on or make changes to this bug.