RPC failure on NIS operation
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| eglibc (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
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:/
The regression this caused was reported and fixed for Fedora 18:
https:/
https:/
http://
As mentioned in that bug report, NIS entries are technically limited to 1024 characters, but Linux has not historically enforced this. A workaround is to break long group entries into separate lines with slightly different names but the same GID:
| description: | updated |
| Dave Gilbert (ubuntu-treblig) wrote | #1 |
| Changed in eglibc (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Lenin (gagarin) wrote | #2 |
| Michael Meier (michael-meier-rrze) wrote | #3 |
Triaged: Identified discussions elsewhere and apparent fix
Medium: hmm it's fairly importnat but then according to the other links you're breaking spec by going over 1024