Moritz Becker

I am also curious about snapshotting / backing up volumes in general and on AWS specifically. I found a related [proposal ](https://github.com/moby/moby/issues/33782) for adding such a feature directly to docker...

What I also tried now is to restart the EC2-Instance running the manager: no success After that, I restarted the worker EC2-Instance running the nginx container: this resolved the issue...

I executed the commands from within the nginx container. The results are as follows: ``` $curl -iL http:// HTTP/1.1 200 OK Server: nginx/1.13.6 Date: Sun, 19 Nov 2017 16:21:00 GMT...

Ok it just happened again, here are the outputs of the commands in an erroneous state: ``` $curl -iL http:// ``` Runs for minutes and then returns `curl: (52) Empty...

``` OK hostname=ip-172-31-4-42-eu-central-1-compute-internal session=1511295594-hrXIAwGyjlYx4lvk3b9ddaedsSsISe8t OK hostname=ip-172-31-0-232-eu-central-1-compute-internal session=1511295594-hrXIAwGyjlYx4lvk3b9ddaedsSsISe8t Done requesting diagnostics. Your diagnostics session ID is 1511295594-hrXIAwGyjlYx4lvk3b9ddaedsSsISe8t Please provide this session ID to the maintainer debugging your issue. ```

Here is the complete history of worker and manager ASG. Does not look like instances are being replaced. # Worker ASG History   | Status | Description | Start Time |...

Just happened again EDIT: ok, false alarm this time it was a different issue..

@FrenchBen Ok now it just happened again during config rotation on one of my services. I.e. I was running `docker service update --config-rm --config-add ` and the update was successful,...

I will try to retrieve the wanted logs the next time this happens.

@FrenchBen It happened again, this time with a service that does not use deploy mode `global`. I currently have 3 managers (A, B and C) in my swarm and I...