[Bug 1181275] [NEW] RPC failure on NIS operation

Trevor Robinson 1181275 at bugs.launchpad.net
Fri May 17 15:25:54 UTC 2013


Public bug reported:

Starting with 13.04, NIS fails when parsing long group lines (in my
case, 1262 bytes).

On login, errors such as the following are repeated numerous times:

yp_all: clnt_call: RPC: Can't decode result
do_ypcall: clnt_call: RPC: Can't decode result

The root cause can be seen with ypcat, where the first long group line
causes a failure:

$ ypcat group.byname
<shorter lines printed correctly>
yp_all: clnt_call: RPC: Can't decode result
No such map group.byname. Reason: RPC failure on NIS operation

Perhaps this is due to a security fix similar to this one in RHEL, where
YP record parsing was limited to YPMAXRECORD (1024):

https://bugzilla.redhat.com/show_bug.cgi?id=848748

The regression this caused was reported and fixed for Fedora 18:

https://bugzilla.redhat.com/show_bug.cgi?id=892777
https://admin.fedoraproject.org/updates/glibc-2.16-31.fc18
http://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20130429/1008442.html

** Affects: eglibc (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/1181275

Title:
  RPC failure on NIS operation

Status in “eglibc” package in Ubuntu:
  New

Bug description:
  Starting with 13.04, NIS fails when parsing long group lines (in my
  case, 1262 bytes).

  On login, errors such as the following are repeated numerous times:

  yp_all: clnt_call: RPC: Can't decode result
  do_ypcall: clnt_call: RPC: Can't decode result

  The root cause can be seen with ypcat, where the first long group line
  causes a failure:

  $ ypcat group.byname
  <shorter lines printed correctly>
  yp_all: clnt_call: RPC: Can't decode result
  No such map group.byname. Reason: RPC failure on NIS operation

  Perhaps this is due to a security fix similar to this one in RHEL,
  where YP record parsing was limited to YPMAXRECORD (1024):

  https://bugzilla.redhat.com/show_bug.cgi?id=848748

  The regression this caused was reported and fixed for Fedora 18:

  https://bugzilla.redhat.com/show_bug.cgi?id=892777
  https://admin.fedoraproject.org/updates/glibc-2.16-31.fc18
  http://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20130429/1008442.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1181275/+subscriptions




More information about the foundations-bugs mailing list