Hi Ton,

"docker --help" command works ok, but
[fedora@sw-d7cum4a5z5a-0-dx4eksy72u4q-swarm-node-3d7bwzm7fso7 ~]$ sudo
/usr/bin/docker -d -H fd:// -H tcp://0.0.0.0:2375 --tlsverify
--tlscacert="/etc/docker/ca.crt" --tlskey="/etc/docker/server.key"
--tlscert="/etc/docker/server.crt" --selinux-enabled --storage-driver
devicemapper --storage-opt dm.fs=xfs --storage-opt
dm.datadev=/dev/mapper/atomicos-docker--data --storage-opt
dm.metadatadev=/dev/mapper/atomicos-docker--meta
Warning: '-d' is deprecated, it will be removed soon. See usage.
WARN[0000] please use 'docker daemon' instead.
ERRO[0000] ServeAPI error: No sockets found
WARN[0001] --storage-opt dm.thinpooldev is preferred over --storage-opt
dm.datadev or dm.metadatadev

[fedora@sw-d7cum4a5z5a-0-dx4eksy72u4q-swarm-node-3d7bwzm7fso7 ~]$ sudo
/usr/bin/docker daemon -H fd:// -H tcp://0.0.0.0:2375 --tlsverify
--tlscacert="/etc/docker/ca.crt" --tlskey="/etc/docker/server.key"
--tlscert="/etc/docker/server.crt" --selinux-enabled --storage-driver
devicemapper --storage-opt dm.fs=xfs --storage-opt
dm.thinpooldev=/dev/mapper/atomicos-docker--data --storage-opt
dm.metadatadev=/dev/mapper/atomicos-docker--meta
ERRO[0000] ServeAPI error: No sockets found
FATA[0001] Error starting daemon: error initializing graphdriver: EOF

[fedora@sw-d7cum4a5z5a-0-dx4eksy72u4q-swarm-node-3d7bwzm7fso7 ~]$ sudo
systemctl status docker.socket
● docker.socket - Docker Socket for the API
   Loaded: loaded (/etc/systemd/system/docker.socket; enabled)
   Active: active (listening) since Fri 2015-10-16 05:55:04 UTC; 2 days ago
   Listen: /var/run/docker.sock (Stream)

Oct 16 05:55:04
sw-d7cum4a5z5a-0-dx4eksy72u4q-swarm-node-3d7bwzm7fso7.novalocal systemd[1]:
Listening on Docker Socket for the API.

this is strange, log into the swarm node, cannot also start the docker
service manually.


Thanks & Best regards !
Mars Ma

On Mon, Oct 19, 2015 at 1:11 PM, Mars Ma <wenc...@gmail.com> wrote:

> Hi Hongbin,
>
> I can ssh into the swarm node, and curl cmd works ok:
> [fedora@sw-d7cum4a5z5a-0-dx4eksy72u4q-swarm-node-3d7bwzm7fso7 ~]$ curl
> openstack.org
> <html>
> <head><title>301 Moved Permanently</title></head>
> <body bgcolor="white">
> <center><h1>301 Moved Permanently</h1></center>
> <hr><center>nginx</center>
> </body>
> </html>
>
> On Fri, Oct 16, 2015 at 2:36 PM, Mars Ma <wenc...@gmail.com> wrote:
>
>> Hi,
>>
>> I used image fedora-21-atomic-5-d181.qcow2 to create swarm bay , but the
>> bay went to failed status with status reason: Resource CREATE failed:
>> WaitConditionFailure:
>> resources.swarm_nodes.resources[0].resources.node_agent_wait_condition:
>> swarm-agent service failed to start.
>> debug inside swarm node, found that docker failed to start, lead to
>> swarm-agent and swarm-manager services failed to start.
>> [fedora@sw-d7cum4a5z5a-0-dx4eksy72u4q-swarm-node-3d7bwzm7fso7 ~]$ docker
>> -v
>> Docker version 1.8.1.fc21, build 32b8b25/1.8.1
>>
>> detailed debug log, I pasted here :
>> http://paste.openstack.org/show/476450/
>>
>>
>>
>>
>> Thanks & Best regards !
>> Mars Ma
>>
>
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to