Q: A user complains they cannot execute a script (`./script.sh`), getting a "Permission denied" error. They own the file and have `rwx` permissions. What else could cause this?
Even if the file has chmod +x and the user owns it, execution can be blocked by:
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: Filesystem mount options, SELinux/AppArmor, shell interpretation.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Even if the file has chmod +x and the user owns it, execution can be blocked by:
- Mount options: The filesystem where the script resides might be mounted with the
noexecflag (often used for/tmpor/var/tmpfor security). You can check this by runningmount | grep noexec. - Interpreter path: The script's shebang (
#!/bin/bash) might point to a missing interpreter, or the interpreter itself lacks execute permissions. - SELinux/AppArmor: Mandatory Access Control policies might block the execution. Checking
dmesgor/var/log/audit/audit.logwill reveal SELinux denials.
Remediation & Permanent Safeguards
- Improper ACLs: Extended ACLs (checked via
getfacl script.sh) might have a deny rule superseding standard POSIX permissions.
- Mount options: The filesystem where the script resides might be mounted with the noexec flag (oft...
- Interpreter path: The script's shebang (#!/bin/bash) might point to a missing interpreter, or the...
- SELinux/AppArmor: Mandatory Access Control policies might block the execution. Checking dmesg or ...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring user complains execute SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring user complains execute
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring user complains execute Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring user complains execute
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).