nscd reports: rpc: failed to open /etc/netconfig

When I run journalctl --reverse, I get messages like these:

Nov 24 21:10:20 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:20 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:20 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:20 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:20 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:14 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:14 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:14 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:14 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:14 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:09 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:09 falcor nscd[1326]: rpc: failed to open /etc/netconfig
Nov 24 21:10:09 falcor nscd[1326]: rpc: failed to open /etc/netconfig

The file exists and ls -l shows the following:

-rw-r–r-- 1 root root 767 Oct 13 05:07 /etc/netconfig

If I su the nscd account, I can open the file.

Usual suspect is apparmor. Anything unusual in logs?

All that are posted are errors… Which is too late (the error is already happening).
You need to look at the dozen or more entries just prior to the first instances of the error occurs to see what had just completed and what is being attempted.

You can do an Internet search on the error “rpc: failed to open /etc/netconfig”, you’ll return various possible causes like netconfig missing altogether, resource exhaustion related to things like “too many files open” and network shares mounting.

Basically, the name server cache daemon(nscd) is what provides network name resolution on the local machine.
<Something> needs name resolution for some task. An rpc (remote procedure call) is a common way for applications to talk to each other.

TSU