-
Notifications
You must be signed in to change notification settings - Fork 1.9k
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
11/02/16 12:06:18 PDT Driver Failure fork/exec permission denied #1919
Comments
Are you running nomad as root? |
Yes, I am running nomad as root. |
Is that user defined on the host |
Yes, the user is present. I tried with both, local user and YP user. I don't think the syntax of job is a problem either. WHen I change the user="eifadmin" to user = "root", the job gets scheduled properly. Here is the output of the "nomad status yodanew" command: Recent Events: |
Found the problem. The /var/lib/nomad needs to have permissions 777. Thanks Dadgar to helping me out |
Where Do you have any insight onto why permissions there were an issue? |
/var/lib/nomad is the datadir owned by root:root. It has permissions 755, Changing it to 777 fixed it. Nomad binary is in /etc/nomad/bin Here is the nomad.hcl file for reference. [rkashika@capistrano: ~/bin]cat /etc/nomad/bin/nomad.hcl consul { advertise { client {
|
This has been fixed. It was due to the alloc dir not having the exec bit set! |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Output from
nomad version
v0.4.0Operating system and Environment details
RHEL 6
Issue
Adding 'user = "eifadmin"' in the job spec results in the error permission denied. If username is not defined in the job spec, all works well. I am using raw_exec driver. The binary I am using "/users/eifadmin/automation/scripts/tinywebserver2" is a simple web server in golang which opens 2 ports.
Reproduction steps
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: