-
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
[question] - executor can't create pid #2106
Comments
@OferE These are the logs from the code which scans pids and gets their resource utilization for the raw exec driver. And these are thread ids for which we can't get the resource utilization. We can look into this and find a way to not log them. |
thank u so much! |
Instructions to reproduce: This is the executable i use to run docker in a non isolated way: #!/bin/bash
# handler for the signals sent from nomad to stop the container
my_exit()
{
echo "killing $CID"
docker stop --time=5 $CID # try to stop it gracefully
docker rm -f $CID # remove the stopped container
}
trap 'my_exit; exit' SIGHUP SIGTERM SIGINT
echo `env`
# Building docker run command
CMD="docker run -d --name ${NOMAD_TASK_NAME}-${NOMAD_ALLOC_ID}"
for a in "$@"; do
CMD="$CMD $a"
done
echo docker wrapper: the docker command that will run is: $CMD
echo from here on it is the docker output:
echo
# actually running the command
CID=`$CMD`
# docker logs is printed in the background
docker logs -f $CID &
# allows the process to listen to signals every 3 seconds
while :
do
sleep 1
done This is an example of a job file that creates the problem:
This is the head of the executor log in one of the clients (again the debug message appears thousands of time):
I hope this helps, |
@OferE To be clear there isn't a bug. These are just verbose debug messages. |
I know - the raw_exec works great for me. |
now that v.0.5.1isout ill close it. ill reopen if reproduced. |
Hi - i just verified that this problem is still happening in v0.5.1 as well. |
thank u so much for solving this. highly appreciated! |
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
Nomad v0.5.0
Operating system and Environment details
I am using raw_exec and sucessfully running docker without isolation. I am getting weired logs in the executor
Question
Can some one explain what am i doing wrong/what is the meaning of these lines in the executor logs?
my executor logs are filled with thousands of these:
016/12/14 14:48:39 [DEBUG] executor: unable to create new process with pid: 30390
2016/12/14 14:48:40 [DEBUG] executor: unable to create new process with pid: 30390
2016/12/14 14:48:41 [DEBUG] executor: unable to create new process with pid: 30390
2016/12/14 14:48:42 [DEBUG] executor: unable to create new process with pid: 30390
2016/12/14 14:48:44 [DEBUG] executor: unable to create new process with pid: 30405
2016/12/14 14:48:45 [DEBUG] executor: unable to create new process with pid: 30405
2016/12/14 14:48:46 [DEBUG] executor: unable to create new process with pid: 30405
2016/12/14 14:48:47 [DEBUG] executor: unable to create new process with pid: 30405
Thanks!
The text was updated successfully, but these errors were encountered: