Skip to contentSkip to conversation

NFSv4 automount - nss_getpwnam name '[email protected]' does not map into domain 'localdomain'

DISCUSSION Ray Van Dolson 3 participants 5 messages Jan 19, 2011 – Jan 26, 2011

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Am doing a kickstart installation of RHEL 6.0 vanilla (no errata applied).

After reboot, when using the automounter to access NFSv4 shares (running on Fedora 13), we see the following in the logs on the RHEL6 client:

Jan 18 15:56:16 rhel6test rpc.idmapd[1387]: nss_getpwnam: name '[email protected]' does not map into domain 'localdomain'
Jan 18 15:56:16 rhel6test rpc.idmapd[1387]: nss_getpwnam: name '[email protected]' does not map into domain 'localdomain'

As a result, directories are not mapped to the correct users but instead to 'nobody'.

This is odd, because per the idmap man pages, the default domain used by rpc.idmapd should be the same as the system domain minus the hostname. This should be esri.com, and is when I type hostname.

Thinking that perhaps rpc.idmapd was started before the network subsystem, I restarted it. Immediately everything worked fine.

I rebooted the system assuming the problem would return, but it didn't. Maybe there's a cache used by rpc.idmapd (nscd?)? Is there something else maybe I'm missing?

Trying to determine if the "right" thing to do is to leave my configuration as default or if I should be modifying /etc/idmapd.conf to set a default domain.

Thanks,
Ray

#1 lore raw

[email protected] wrote on 01/18/2011 06:29:07 PM:

Quoted 22 lines

Am doing a kickstart installation of RHEL 6.0 vanilla (no errata applied).

After reboot, when using the automounter to access NFSv4 shares (running on Fedora 13), we see the following in the logs on the RHEL6 client:

Jan 18 15:56:16 rhel6test rpc.idmapd[1387]: nss_getpwnam: name
'[email protected]' does not map into domain 'localdomain'
Jan 18 15:56:16 rhel6test rpc.idmapd[1387]: nss_getpwnam: name

'[email protected]' does not map into domain 'localdomain'

As a result, directories are not mapped to the correct users but instead to 'nobody'.

This is odd, because per the idmap man pages, the default domain used by rpc.idmapd should be the same as the system domain minus the hostname. This should be esri.com, and is when I type hostname.

Thinking that perhaps rpc.idmapd was started before the network subsystem, I restarted it. Immediately everything worked fine.

Quoted 7 lines

I rebooted the system assuming the problem would return, but it didn't. Maybe there's a cache used by rpc.idmapd (nscd?)? Is there something else maybe I'm missing?

Trying to determine if the "right" thing to do is to leave my configuration as default or if I should be modifying /etc/idmapd.conf to set a default domain.

shot in the dark... is your real hostname also mapped to localhost.localdomain in /etc/hosts?

#2 lore raw
Quoted 30 lines · On Wed, Jan 19, 2011 at 06:22:35AM -0800, [email protected] wrote:

[email protected] wrote on 01/18/2011 06:29:07 PM:

Quoted 26 lines

Am doing a kickstart installation of RHEL 6.0 vanilla (no errata applied).

After reboot, when using the automounter to access NFSv4 shares (running on Fedora 13), we see the following in the logs on the RHEL6 client:

Jan 18 15:56:16 rhel6test rpc.idmapd[1387]: nss_getpwnam: name
'[email protected]' does not map into domain 'localdomain'
Jan 18 15:56:16 rhel6test rpc.idmapd[1387]: nss_getpwnam: name

'[email protected]' does not map into domain 'localdomain'

As a result, directories are not mapped to the correct users but instead to 'nobody'.

This is odd, because per the idmap man pages, the default domain used by rpc.idmapd should be the same as the system domain minus the hostname. This should be esri.com, and is when I type hostname.

Thinking that perhaps rpc.idmapd was started before the network subsystem, I restarted it. Immediately everything worked fine.

I rebooted the system assuming the problem would return, but it didn't. Maybe there's a cache used by rpc.idmapd (nscd?)? Is there something else maybe I'm missing?

Quoted 6 lines
Quoted 3 lines

Trying to determine if the "right" thing to do is to leave my configuration as default or if I should be modifying /etc/idmapd.conf to set a default domain.

shot in the dark... is your real hostname also mapped to localhost.localdomain in /etc/hosts?

Yes, it is... I'd stumbled across a similar suggestion, but kinda was puzzled that things seemed to start working even without changing the entry in /etc/hosts.

This is what made me think nscd or some caching was involved...

Ray

#3 lore raw

[email protected] wrote on 01/19/2011 09:04:50 AM:

Quoted 15 lines
Quoted 15 lines
Quoted 15 lines

Am doing a kickstart installation of RHEL 6.0 vanilla (no errata applied).

After reboot, when using the automounter to access NFSv4 shares (running on Fedora 13), we see the following in the logs on the RHEL6 client:

Jan 18 15:56:16 rhel6test rpc.idmapd[1387]: nss_getpwnam: name
'[email protected]' does not map into domain 'localdomain'
Jan 18 15:56:16 rhel6test rpc.idmapd[1387]: nss_getpwnam: name

'[email protected]' does not map into domain 'localdomain'

As a result, directories are not mapped to the correct users but instead to 'nobody'.

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

This is odd, because per the idmap man pages, the default domain used by rpc.idmapd should be the same as the system domain minus the hostname. This should be esri.com, and is when I type hostname.

Thinking that perhaps rpc.idmapd was started before the network subsystem, I restarted it. Immediately everything worked fine.

I rebooted the system assuming the problem would return, but it

didn't.

Quoted 7 lines
Quoted 7 lines
Quoted 6 lines

Maybe there's a cache used by rpc.idmapd (nscd?)? Is there something else maybe I'm missing?

Trying to determine if the "right" thing to do is to leave my configuration as default or if I should be modifying /etc/idmapd.conf to set a default domain.

Quoted 8 lines
Quoted 2 lines

shot in the dark... is your real hostname also mapped to localhost.localdomain in /etc/hosts?

Yes, it is... I'd stumbled across a similar suggestion, but kinda was puzzled that things seemed to start working even without changing the entry in /etc/hosts.

This is what made me think nscd or some caching was involved...

well it makes sense to ask. i think the hosts file is exactly the issue though because if its starting before the network it is resolving based on local /etc/hosts entry. However maybe NFS (or underlying dns layer) is smart enough to realize that if there is network access its better to do the hostname lookup against the dns servers.? So once you restarted it after the network is available, it got the right domain and worked.

I personally recommend (normally, not just in this situation) that if your hostname maps to a specific IP, you can still put that mapping in /etc/hosts, but make sure that only localhost and localhost.domain are mapping to 127.0.0.1.

-greg

#4 lore raw

/etc/idmapd.conf is configured the same way on both the NFSv4 Server & Client correct? (I assume this is correct). I've run into this several times and usually a reboot of the "idmapd" service on the client fixes the issue (make sure that the NFS share is not mounted on the client).

Regards,

Dan