Bug 8807 - Regression: NFS problems. request-key.conf need call to nfsidmap.
Summary: Regression: NFS problems. request-key.conf need call to nfsidmap.
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
Keywords: Triaged
Depends on:
Reported: 2013-01-25 00:09 CET by Morgan Leijström
Modified: 2013-11-23 16:13 CET (History)
3 users (show)

See Also:
Source RPM: keyutils
Status comment:


Description Morgan Leijström 2013-01-25 00:09:07 CET
After update to kernel 3.4.24-desktop-3.mga2 my computers sometimes in the logging Ctrl-AltF12 terminal spit out the following line, several per minute
(and I can also see them using
 # tail -f /var/log/auth.log )

request-key: Cannot find command to construct key 97741564

( The number at the end changes every the time )

And NFS sometimes just stop a while; Browsing an NFS share i sometimes have to wait over 10 seconds for it to list directory.

This happen on both 32 and 64 bit mga2

The NFS server is mga1. 

(on one computer i also have experienced other apps on desktop becomes unresponsive when browsing NFS with Dolphin and it pauses despite CPU usage is low.)

Googled a bit and found on arch linux https://bugs.archlinux.org/task/30442 :  The rpc.idmapd trouble is gone with keyutils 1.5.5-3. The previous versions caused a lot of error logs like "request-key: Cannot find command to construct key 994854967" which is an indicator for an unstable NFS4.

We have mga2 latest keyutils 1.5.5-1.mga2
Comment 1 Morgan Leijström 2013-01-25 01:24:19 CET
Booting elder kernel 3.3.8-desktop-2.mga2 avoids issues on both 32 and 64 bit.
Manuel Hiebel 2013-01-25 23:56:55 CET

CC: (none) => guillomovitch, tmb
Source RPM: (none) => keyutils

Comment 2 Morgan Leijström 2013-03-27 01:16:52 CET
I again have tried the latest mageia kernels, and still experience the problem.
It also manifest itself in the computer not shutting down.
I then realised it fail to umount the networkdrives
I can not even df; it never comes back.

The computers can be used for a couple days, sleeping in RAM, then restarting, but after a random number of few cycles the issue hits.

kernel 3.3.8 = no problem.
Comment 3 Morgan Leijström 2013-03-27 01:17:53 CET
( by the latest i meant the latest *mga2*  kernels )
Comment 4 Guillaume Rousse 2013-03-27 19:17:42 CET
We already have latest keyutils version (1.5.5) in mageia 2. The -3 final part is just the arch-specific package release number.

According to the gmane thread, the fix is just to edit keyutils configuration following instructions from nfsidmap man page:
       The   file   /etc/request-key.conf   will   need   to  be  modified  so
       /sbin/request-key can properly direct the upcall.  The  following  line
       should be added before a call to keyctl negate:

       create    id_resolver    *    *    /usr/sbin/nfsidmap -t 600 %k %d

Can you try this solution ?


Comment 5 Morgan Leijström 2013-04-06 12:03:53 CEST
Thanks. Works on 64 bit :)
-but give "unsupported macro" on 32 bit systems !? 

I added the line

create    id_resolver    *    *    /usr/sbin/nfsidmap -t 600 %k %d

right before the line having "keyctl negate" in /etc/request-key.conf

Seem to work on mga2 64 bit, but on the two mga2 32 bit machines I instead get in the authentication log: 
     request-key:/etc/request-key.conf:41:Unsupported macro
41 is the line number of my added line.

"Macro"?  I checked /usr/sbin/nfsidmap exist on both 32 and 64 bit systems, and from same version nfs-utils-clients, all systems are up to date.
And i have checked three times i entered the lines correctly.

( BTW, the part -t 600 may be omitted, it sets the key timeout to 600 seconds, which also is the default with that omitted. )
Morgan Leijström 2013-04-06 12:05:57 CEST

Summary: Regression: NFS problems. I guess keyutils need upgrading => Regression: NFS problems. request-key.conf need call to nfsidmap.

Comment 6 Samuel Verschelde 2013-08-28 22:18:24 CEST
Assigning to Guillaume Rousse who set the bug status to ASSIGNED

Keywords: (none) => Triaged
CC: (none) => stormi

Comment 7 Guillaume Rousse 2013-09-05 23:45:51 CEST
Macros here are the %k and %d tokens. I don't see anything wrong in the code, tough, so excepted an unlikely compiler bug, I have no clue what is going wrong here.
Comment 8 Manuel Hiebel 2013-10-22 12:10:14 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

The Mageia Bugsquad
Comment 9 Manuel Hiebel 2013-11-23 16:13:49 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

The Mageia Bugsquad

Resolution: (none) => OLD

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