I can hardly belief it:  A reboot did the job.

I have had the problem between a fedora17 server and a SL6.3 client.

In the /etc/idmapd.conf files the domain is set to:
  Domain=localdomain
but I can not change it to anything else, because to many hosts are involved. NB: you can freely choose the name. It could be your DNS domain, or anything else (like "localdomain").

So it works now. Let's see what the fix is good for....

Thanks for the help!
Rupert


Jamie Duncan schrieb:
https://bugzilla.redhat.com/show_bug.cgi?id=855417 is the bug that will push this fix into the 6.3 z-stream.

the actual patch (https://bugzilla.redhat.com/attachment.cgi?id=625075&action=diff) looks pretty straight-forward. Should be out pretty soon.

On Fri, Nov 16, 2012 at 11:33 AM, Konstantin Olchanski <[email protected] <mailto:[email protected]>> wrote:

    On Fri, Nov 16, 2012 at 08:35:16AM +0100, Rupert Kolb wrote:
    >
    > there is a bug in nfs-utils:
    > The mapping of user name and group doesn't work: I get nouser and
    > nogroup, which is really annoying,
    >
    > see: https://bugzilla.redhat.com/show_bug.cgi?id=849945
    >
    > Can this be fixed in SL 6.3 shortly?
    >

    If I read the referenced bug correctly, they think it is a problem
    with a FreeBSD NFSv4 server.

    If your servers and clients are SL6, perhaps your problem is
    elsewhere.

    I, too, have seen NFSv4 report "nouser" and "nogroup". This is
    connected to this idmapd
    thing and I remember some gyrations with it through SL6.0->6.1->6.2.

    For a standalone cluster (no NIS), it appears that you have to set
    the "Domain" value
    in idmapd.conf to the same value on all machines. Without that, I
    was seeing
    some machines decide to use Domain=triumf.ca <http://triumf.ca>,
    others Domain=localdomain, etc,
    and obviously uid-name mapping did not work. There were reasonably
    explanatory
    messages in the syslog. Then after changing the Domain= value in
    idmapd.conf
    I remember having to reboot every machine - restarting nfs,
    idmapd, etc was
    not enough - it was remembering the old settings somewhere. This
    is for SL6.1, SL6.2.

    For an NIS cluster, the default value (Domain= commented out in
    /etc/idmapd.conf)
    seems to work in SL6.2. (But I have no idea what "domain name"
    ("realm name"?) it is using,
    it does not seem to report it to the syslog).

    We also have sporadic DHCP problems with domains and hostnames
    changing
    between abc.triumf.ca <http://abc.triumf.ca> and abc.Trumf.CA
    <http://abc.Trumf.CA> (note capital letters), another thing
    to watch for that may trip-up the NFSv4 idmapd.

    Good luck!

    --
    Konstantin Olchanski
    Data Acquisition Systems: The Bytes Must Flow!
    Email: olchansk-at-triumf-dot-ca
    Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3,
    Canada




--
Thanks,

Jamie Duncan
804.571.0458

Reply via email to