Unable to start task in ecs. Tasks are in PENDING stateECS Stopped Task not Releasing PortCan I use AWS SNS to communicate between ECS Tasks?AWS ECS Cannot start taskAWS ECS: Unable to place taskAWS ECS: Service + autoscaling vs User Data launching TaskCreating a CloudWatch Scheduled Event with arbitrary data in the `detail` fieldHow do AWS ECS Task Definition updates work?ECS task definition versioningDocker labels for ECS containersAWS ECS service time period for checking and placing task in a container instance?
What can I do to find new work while my workplace is closed due to an accidental death?
Should I hide continue button until tasks are completed?
MH370 blackbox - is it still possible to retrieve data from it?
Does the Distant Spell metamagic apply to the Sword Burst cantrip?
Should I tell my insurance company I'm making payments on my new car?
Mount a folder with a space on Linux
Counting occurrence of words in table is slow
How could mana leakage be dangerous to a elf?
What is this particular type of chord progression, common in classical music, called?
How to get cool night-vision without lame drawbacks?
Why would people reject a god's purely beneficial blessing?
Firefox Arm64 available but RapsPi 3B+ still 32 bit
Swapping rooks in a 4x4 board
How can I convince my reader that I will not use a certain trope?
How to append a matrix element by element?
When is it ok to add filler to a story?
Why is the Turkish president's surname spelt in Russian as Эрдоган, with г?
Inverse-quotes-quine
Does the Paladin's Aura of Protection affect only either her or ONE ally in range?
Does Marvel have an equivalent of the Green Lantern?
What do you call the action of someone tackling a stronger person?
Fedora boot screen shows both Fedora logo and Lenovo logo. Why and How?
Going to get married soon, should I do it on Dec 31 or Jan 1?
Impossible darts scores
Unable to start task in ecs. Tasks are in PENDING state
ECS Stopped Task not Releasing PortCan I use AWS SNS to communicate between ECS Tasks?AWS ECS Cannot start taskAWS ECS: Unable to place taskAWS ECS: Service + autoscaling vs User Data launching TaskCreating a CloudWatch Scheduled Event with arbitrary data in the `detail` fieldHow do AWS ECS Task Definition updates work?ECS task definition versioningDocker labels for ECS containersAWS ECS service time period for checking and placing task in a container instance?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
My tasks are in PENDING status
That's what I can see in the events
There is not many information in the service events.
Here is the task definition in json
"requiresAttributes": [
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.17",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.18",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.ecr-auth",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.task-iam-role",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.logging-driver.awslogs",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.task-iam-role-network-host",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.19",
"targetId": null,
"targetType": null
],
"taskDefinitionArn": "arn:aws:ecs:ap-southeast-2:1234567890:task-definition/SQ1-queuetest:1",
"networkMode": "host",
"status": "ACTIVE",
"revision": 1,
"taskRoleArn": "arn:aws:iam::1234567890:role/play-ecs",
"containerDefinitions": [
"volumesFrom": [],
"memory": 256,
"extraHosts": null,
"dnsServers": null,
"disableNetworking": null,
"dnsSearchDomains": null,
"portMappings": [],
"hostname": null,
"essential": true,
"entryPoint": null,
"mountPoints": [],
"name": "sq1",
"ulimits": null,
"dockerSecurityOptions": null,
"environment": [
"name": "ENV",
"value": "test"
],
"links": null,
"workingDirectory": "/app/src/",
"readonlyRootFilesystem": null,
"image": "1234567890.dkr.ecr.ap-southeast-2.amazonaws.com/simplequeue:latest",
"command": [
"python /app/src/main.py"
],
"user": null,
"dockerLabels": null,
"logConfiguration":
"logDriver": "awslogs",
"options":
"awslogs-group": "simplequeue",
"awslogs-region": "ap-southeast-2",
"awslogs-stream-prefix": "sq1"
,
"cpu": 512,
"privileged": null,
"memoryReservation": null
],
"placementConstraints": [],
"volumes": [],
"family": "SQ1-queuetest"
How can I find out more why the task is failing to start?
amazon-cloudwatch amazon-ecs
add a comment |
My tasks are in PENDING status
That's what I can see in the events
There is not many information in the service events.
Here is the task definition in json
"requiresAttributes": [
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.17",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.18",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.ecr-auth",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.task-iam-role",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.logging-driver.awslogs",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.task-iam-role-network-host",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.19",
"targetId": null,
"targetType": null
],
"taskDefinitionArn": "arn:aws:ecs:ap-southeast-2:1234567890:task-definition/SQ1-queuetest:1",
"networkMode": "host",
"status": "ACTIVE",
"revision": 1,
"taskRoleArn": "arn:aws:iam::1234567890:role/play-ecs",
"containerDefinitions": [
"volumesFrom": [],
"memory": 256,
"extraHosts": null,
"dnsServers": null,
"disableNetworking": null,
"dnsSearchDomains": null,
"portMappings": [],
"hostname": null,
"essential": true,
"entryPoint": null,
"mountPoints": [],
"name": "sq1",
"ulimits": null,
"dockerSecurityOptions": null,
"environment": [
"name": "ENV",
"value": "test"
],
"links": null,
"workingDirectory": "/app/src/",
"readonlyRootFilesystem": null,
"image": "1234567890.dkr.ecr.ap-southeast-2.amazonaws.com/simplequeue:latest",
"command": [
"python /app/src/main.py"
],
"user": null,
"dockerLabels": null,
"logConfiguration":
"logDriver": "awslogs",
"options":
"awslogs-group": "simplequeue",
"awslogs-region": "ap-southeast-2",
"awslogs-stream-prefix": "sq1"
,
"cpu": 512,
"privileged": null,
"memoryReservation": null
],
"placementConstraints": [],
"volumes": [],
"family": "SQ1-queuetest"
How can I find out more why the task is failing to start?
amazon-cloudwatch amazon-ecs
add a comment |
My tasks are in PENDING status
That's what I can see in the events
There is not many information in the service events.
Here is the task definition in json
"requiresAttributes": [
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.17",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.18",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.ecr-auth",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.task-iam-role",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.logging-driver.awslogs",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.task-iam-role-network-host",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.19",
"targetId": null,
"targetType": null
],
"taskDefinitionArn": "arn:aws:ecs:ap-southeast-2:1234567890:task-definition/SQ1-queuetest:1",
"networkMode": "host",
"status": "ACTIVE",
"revision": 1,
"taskRoleArn": "arn:aws:iam::1234567890:role/play-ecs",
"containerDefinitions": [
"volumesFrom": [],
"memory": 256,
"extraHosts": null,
"dnsServers": null,
"disableNetworking": null,
"dnsSearchDomains": null,
"portMappings": [],
"hostname": null,
"essential": true,
"entryPoint": null,
"mountPoints": [],
"name": "sq1",
"ulimits": null,
"dockerSecurityOptions": null,
"environment": [
"name": "ENV",
"value": "test"
],
"links": null,
"workingDirectory": "/app/src/",
"readonlyRootFilesystem": null,
"image": "1234567890.dkr.ecr.ap-southeast-2.amazonaws.com/simplequeue:latest",
"command": [
"python /app/src/main.py"
],
"user": null,
"dockerLabels": null,
"logConfiguration":
"logDriver": "awslogs",
"options":
"awslogs-group": "simplequeue",
"awslogs-region": "ap-southeast-2",
"awslogs-stream-prefix": "sq1"
,
"cpu": 512,
"privileged": null,
"memoryReservation": null
],
"placementConstraints": [],
"volumes": [],
"family": "SQ1-queuetest"
How can I find out more why the task is failing to start?
amazon-cloudwatch amazon-ecs
My tasks are in PENDING status
That's what I can see in the events
There is not many information in the service events.
Here is the task definition in json
"requiresAttributes": [
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.17",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.18",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.ecr-auth",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.task-iam-role",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.logging-driver.awslogs",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.task-iam-role-network-host",
"targetId": null,
"targetType": null
,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.19",
"targetId": null,
"targetType": null
],
"taskDefinitionArn": "arn:aws:ecs:ap-southeast-2:1234567890:task-definition/SQ1-queuetest:1",
"networkMode": "host",
"status": "ACTIVE",
"revision": 1,
"taskRoleArn": "arn:aws:iam::1234567890:role/play-ecs",
"containerDefinitions": [
"volumesFrom": [],
"memory": 256,
"extraHosts": null,
"dnsServers": null,
"disableNetworking": null,
"dnsSearchDomains": null,
"portMappings": [],
"hostname": null,
"essential": true,
"entryPoint": null,
"mountPoints": [],
"name": "sq1",
"ulimits": null,
"dockerSecurityOptions": null,
"environment": [
"name": "ENV",
"value": "test"
],
"links": null,
"workingDirectory": "/app/src/",
"readonlyRootFilesystem": null,
"image": "1234567890.dkr.ecr.ap-southeast-2.amazonaws.com/simplequeue:latest",
"command": [
"python /app/src/main.py"
],
"user": null,
"dockerLabels": null,
"logConfiguration":
"logDriver": "awslogs",
"options":
"awslogs-group": "simplequeue",
"awslogs-region": "ap-southeast-2",
"awslogs-stream-prefix": "sq1"
,
"cpu": 512,
"privileged": null,
"memoryReservation": null
],
"placementConstraints": [],
"volumes": [],
"family": "SQ1-queuetest"
How can I find out more why the task is failing to start?
amazon-cloudwatch amazon-ecs
amazon-cloudwatch amazon-ecs
edited Jun 14 '17 at 8:44
Anthony Kong
asked Jun 14 '17 at 8:30
Anthony KongAnthony Kong
9651 gold badge18 silver badges47 bronze badges
9651 gold badge18 silver badges47 bronze badges
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It seems to be due to the lack of policy AmazonEC2ContainerServiceforEC2Role
.
After I assigned this policy to the role, I get a different error message now:
service SQ1-test was unable to place a task because no container
instance met all of its requirements. The closest matching
container-instance efea641c-6204-4a68-a69f-cb1b07e3529a encountered
error "AGENT". For more information, see the Troubleshooting section.
It turns out the above error is caused by an inadvertent removal of the role ecsInstanceRole
which was created when a cluster was being created.
Now I can see the status is turned to 'PENDING'
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f855687%2funable-to-start-task-in-ecs-tasks-are-in-pending-state%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It seems to be due to the lack of policy AmazonEC2ContainerServiceforEC2Role
.
After I assigned this policy to the role, I get a different error message now:
service SQ1-test was unable to place a task because no container
instance met all of its requirements. The closest matching
container-instance efea641c-6204-4a68-a69f-cb1b07e3529a encountered
error "AGENT". For more information, see the Troubleshooting section.
It turns out the above error is caused by an inadvertent removal of the role ecsInstanceRole
which was created when a cluster was being created.
Now I can see the status is turned to 'PENDING'
add a comment |
It seems to be due to the lack of policy AmazonEC2ContainerServiceforEC2Role
.
After I assigned this policy to the role, I get a different error message now:
service SQ1-test was unable to place a task because no container
instance met all of its requirements. The closest matching
container-instance efea641c-6204-4a68-a69f-cb1b07e3529a encountered
error "AGENT". For more information, see the Troubleshooting section.
It turns out the above error is caused by an inadvertent removal of the role ecsInstanceRole
which was created when a cluster was being created.
Now I can see the status is turned to 'PENDING'
add a comment |
It seems to be due to the lack of policy AmazonEC2ContainerServiceforEC2Role
.
After I assigned this policy to the role, I get a different error message now:
service SQ1-test was unable to place a task because no container
instance met all of its requirements. The closest matching
container-instance efea641c-6204-4a68-a69f-cb1b07e3529a encountered
error "AGENT". For more information, see the Troubleshooting section.
It turns out the above error is caused by an inadvertent removal of the role ecsInstanceRole
which was created when a cluster was being created.
Now I can see the status is turned to 'PENDING'
It seems to be due to the lack of policy AmazonEC2ContainerServiceforEC2Role
.
After I assigned this policy to the role, I get a different error message now:
service SQ1-test was unable to place a task because no container
instance met all of its requirements. The closest matching
container-instance efea641c-6204-4a68-a69f-cb1b07e3529a encountered
error "AGENT". For more information, see the Troubleshooting section.
It turns out the above error is caused by an inadvertent removal of the role ecsInstanceRole
which was created when a cluster was being created.
Now I can see the status is turned to 'PENDING'
edited Jun 14 '17 at 11:43
answered Jun 14 '17 at 11:01
Anthony KongAnthony Kong
9651 gold badge18 silver badges47 bronze badges
9651 gold badge18 silver badges47 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f855687%2funable-to-start-task-in-ecs-tasks-are-in-pending-state%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown