Docker Community Forums

Share and learn in the Docker community.

Container Update(die) event


(Rishabhishan) #1

On deploying mysql service in my node, I am getting this event in timeline. Why is the service not running as daemon ?

Received event ‘die’ from node 8a94c514-e5fc-4eae-a56a-6bfe475ed4c2.node.dockerapp.io for container mysql-72d1f814-1: Running
Changing container state from ‘Running’ to 'Stopped’
Checking triggers
Container has no triggers


(Marko Ciric) #2

It happens to me as well for couple of services. Would really appreciate if someone knows what could be the common problem!


(Ramsh) #3

Same issue for me too

here is the dockercloud/docker.log result


2016/03/17 19:01:33 http: TLS handshake error from 52.21.89.47:38255: EOF
time=“2016-03-17T19:01:33.540837214Z” level=info msg="GET /v1.21/_ping"
time=“2016-03-17T19:01:33.612754729Z” level=info msg="GET /v1.21/version"
time=“2016-03-17T19:01:33.684736605Z” level=info msg="GET /v1.21/info"
time=“2016-03-17T19:01:33.803867044Z” level=info msg="GET /v1.21/containers/3d281dcb9bddc134686269c73a1ab224316a358f49083302fb31c53049a31b08/logs?timestamps=1&tail=10&follow=0&stderr=1&stdout=1"
time=“2016-03-17T19:01:33.946865310Z” level=info msg="GET /v1.21/containers/3d281dcb9bddc134686269c73a1ab224316a358f49083302fb31c53049a31b08/json"
time=“2016-03-17T19:01:33.997625055Z” level=info msg=“GET /v1.21/containers/3d281dcb9bddc134686269c73a1ab224316a358f49083302fb31c53049a31b08/json”


Here is the timeline result


Received event ‘die’ from node 7659a856-1304-428a-8526-ad1521140392.node.dockerapp.io for container wordpress-cloud-1: Running
Changing container state from ‘Running’ to 'Stopped’
Checking triggers
Container has no triggers


Container Update (die) 00:31 03/18/2016
Finished: 00:31 03/18/2016

Duration:a few seconds

Location:xxxxxxxxx
IP:xxxxxxxx

User agent:events-daemon/1.2

Request:POST /api/agent/v1/monitoring/7659a856-1304-428a-8526-ad1521140392/events/

Request body:
{
“status”: “die”,
“exitcode”: “1”,
“from”: “wordpress:latest”,
“id”: “3d281dcb9bddc134686269c73a1ab224316a358f49083302fb31c53049a31b08”,
“time”: 1458241291479367400
}


(Fernando Mayo) #4

That event in the timeline means that we got notified by the remote docker engine that the container stopped on the node, so we update it on our database. So you will need to investigate why the container stopped by looking at its logs.


(Ramsh) #5

This is what showing in the docker.log (/var/log/dockercloud)


2016/03/18 17:03:18 http: TLS handshake error from 52.2.68.80:36692: EOF
time=“2016-03-18T17:03:18.367125950Z” level=info msg="GET /v1.21/_ping"
time=“2016-03-18T17:03:18.439046397Z” level=info msg="GET /v1.21/version"
time=“2016-03-18T17:03:18.510977122Z” level=info msg="GET /v1.21/info"
time=“2016-03-18T17:03:18.638081185Z” level=info msg="GET /v1.21/containers/555c1db1f9f83912cdf2503c4a19fb73f550a722bbc5693b1fe2a84be2b4bc6c/json"
time=“2016-03-18T17:03:18.721248062Z” level=info msg="POST /v1.21/containers/555c1db1f9f83912cdf2503c4a19fb73f550a722bbc5693b1fe2a84be2b4bc6c/start"
time=“2016-03-18T17:03:18.844616857Z” level=info msg="GET /containers/555c1db1f9f83912cdf2503c4a19fb73f550a722bbc5693b1fe2a84be2b4bc6c/json"
time=“2016-03-18T17:03:18.885411492Z” level=info msg="GET /v1.21/containers/555c1db1f9f83912cdf2503c4a19fb73f550a722bbc5693b1fe2a84be2b4bc6c/json"
time=“2016-03-18T17:03:18.903301275Z” level=info msg="GET /containers/555c1db1f9f83912cdf2503c4a19fb73f550a722bbc5693b1fe2a84be2b4bc6c/json"
time=“2016-03-18T17:03:18.982260714Z” level=info msg="GET /v1.21/containers/555c1db1f9f83912cdf2503c4a19fb73f550a722bbc5693b1fe2a84be2b4bc6c/json"
time=“2016-03-18T17:03:18.987859837Z” level=info msg=“GET /v1.21/containers/555c1db1f9f83912cdf2503c4a19fb73f550a722bbc5693b1fe2a84be2b4bc6c/json”



(Ramsh) #6

Also I can start a new container using the same images through docker run command.
Not sure what is the exact issue. We have enough space. The issue is still exist. I am stuck here


(Minh-Quan Tran) #7

I got this error when there is no disk space left.