Giters

ClusterHQ / flocker

Container data volume manager for your Dockerized application

Home Page:https://clusterhq.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

timed out waiting for dataset to mount

beth2016 opened this issue · comments

commented

I am getting this error message when trying to run the example in rhel7.2:

docker run -v apples:/data --volume-driver flocker busybox sh -c "echo hello > /data/file.txt"
docker: Error response from daemon: Timed out waiting for dataset to mount..

I looked at journalctl to look at the logs, and nothing seemed to stand out. No error messages.
What should I be looking for? please advice. thanks.

commented

Hey @beth2016

You need to check the journalctl logs for all the Flocker processes and the docker process.

Somewhere, there'll be an error message.

  • Docker will be connecting to the flocker-docker-plugin
  • flocker-docker-plugin will be connecting to flocker-control
  • flocker-docker-plugin will be polling the Flocker cluster state from flocker-control
  • flocker-dataset-agent on the server where you ran docker run ... should have received a new Flocker cluster configuration and should be attempting create, attach, format and mount a new volume.

See https://flocker-docs.clusterhq.com/en/latest/administering/debugging.html

-RichardW.

commented

Yeah, i did yesterday. there is no error message.
I followed that same link yesterday ( i see no err messages)

commented

I'm pretty sure there'll be an "error" / "exception" / "failure" message somewhere in the logs.

Or, perhaps the Docker daemon hasn't been able to connect to the flocker-docker-plugin.
Is that process running?

Perhaps the flocker-docker-plugin can't connect to flocker-control.
Is flocker-control running and listening on a TCP port?

Perhaps the flocker-dataset-agent isn't running or isn't connected to the flocker-control service.
Is there a flocker-dataset-agent process running on the server?
Can you see an established connection to port 4454 on the server where flocker-control is running?

Check the list of Flocker volumes reported by the Flocker REST API using curl or using flockerctl.

Try creating a volume through the REST API or using flockerctl.

If you're working on AWS I'd also look at the list of EBS block devices and or check the cloudtrail logs to see what AWS API operations have been performed.

There are lots of moving parts and you have to check that all the components are running and connected.

commented

I am running into the same issue:
Have looked through the logs and cannot find anything.
Using Ubuntu 16.04 with one control node and two worker nodes - followed the instructions for manually installing flocker with docker swarm
flockerctl list shows the volume as detached as was able to create another volume using flockerctl

d031b929-0add-4c9f-a600-cea2a9491b46 75.00G name=apples detached e9870d25 (192.x.x.x)