SLES 16 – Common Problem 144 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Files on NFSv4 mounts appear as `nobody:nobody` despite valid UIDs on the server.

Environment & Reproduction

Common on SLES 16 clients newly joined to NFSv4 servers using ID mapping.

Root Cause Analysis

`rpc.idmapd` domain mismatch between client and server defaults to `nobody`.

Quick Triage

Compare `Domain =` in `/etc/idmapd.conf` on both ends.

Step-by-Step Diagnosis

Run `nfsidmap -c && nfsidmap -d` and re-list a sample directory.

Solution – Primary Fix

Set `Domain = example.com` in `/etc/idmapd.conf`, then `systemctl restart nfs-idmapd`.

Solution – Alternative Approaches

Switch the export to `sec=sys` and rely on numeric UIDs for short-term relief.

Verification & Acceptance Criteria

`ls -l` shows correct usernames and `nfsidmap -l` returns active mappings.

Rollback Plan

Revert idmapd configuration via snapper if changes break access.

Prevention & Hardening

Standardise on a single ID mapping domain across all NFSv4 clients/servers.

Related Errors & Cross-Refs

Pairs with Kerberos `KRB5_AP_ERR_TKT_NYV` if sec=krb5 is enabled.

Related tutorial: View the step-by-step tutorial for sles-16.

View all sles-16 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

SUSE NFSv4 administration documentation.