| Previous | Next |
| ENOMEM | EFAULT |
EACCES
Permission checks happen along the whole path
EACCES is commonly displayed as an access refusal, but the final object is not the only place that matters. To resolve a path, the process needs search permission on each directory it must traverse. Creating a file additionally requires permission to modify the parent directory. Execution can fail because the file, script interpreter, or filesystem execution policy does not permit the request.
This makes EACCES different from a simple file-mode mistake. A readable file can still be unreachable through one private directory; a writable target name can still fail because the containing directory is not writable; and a container or service may be using an unexpected user or group.
How to investigate
- Inspect every component of the path, including directory execute/search permission, ownership, ACLs, mount options, and the parent directory.
- Confirm the effective user and groups of the actual service process, not the administrator’s interactive shell.
- For creation and replacement, check parent-directory policy and sticky-bit rules.
- Grant the narrowest required permission and avoid using broad permissions merely to suppress the symptom.
References
Looking for a different code? Search another status or error code.