AWS上运行Deis, register不能正常工作,求解?


本人刚刚在AWS上5台m3.large上部署了deis. 使用deisctl启动了deis,但注册新用户时报如下错误,求高人指点:
core@ip-10-21-2-136 ~ $ ./deis register http://deis.scloud.org
username: deis
password: 
password (confirm): 
email: 
Couldn't connect to the Deis Controller:
('Connection aborted.', error(110, 'Connection timed out'))
Make sure that the Controller URI is correct and the server is running.

其它命令工具正常:
deisctl list
UNIT                MACHINE         LOAD    ACTIVE  SUB
deis-builder.service        860a1cd3.../10.21.2.137 loaded  active  running
deis-cache.service      a6b009f5.../10.21.2.138 loaded  active  running
deis-controller.service     ad04b506.../10.21.2.136 loaded  active  running
deis-database.service       f2fc4fb0.../10.21.1.152 loaded  active  running
deis-logger.service     860a1cd3.../10.21.2.137 loaded  active  running
deis-logspout.service       7aa4377f.../10.21.1.151 loaded  active  running
deis-logspout.service       860a1cd3.../10.21.2.137 loaded  active  running
deis-logspout.service       a6b009f5.../10.21.2.138 loaded  active  running
deis-logspout.service       ad04b506.../10.21.2.136 loaded  active  running
deis-logspout.service       f2fc4fb0.../10.21.1.152 loaded  active  running
deis-publisher.service      7aa4377f.../10.21.1.151 loaded  active  running
deis-publisher.service      860a1cd3.../10.21.2.137 loaded  active  running
deis-publisher.service      a6b009f5.../10.21.2.138 loaded  active  running
deis-publisher.service      ad04b506.../10.21.2.136 loaded  active  running
deis-publisher.service      f2fc4fb0.../10.21.1.152 loaded  active  running
deis-registry@1.service     7aa4377f.../10.21.1.151 loaded  active  running
deis-router.service     7aa4377f.../10.21.1.151 loaded  active  running
deis-router@1.service       a6b009f5.../10.21.2.138 loaded  active  running
deis-router@2.service       ad04b506.../10.21.2.136 loaded  active  running
deis-router@3.service       f2fc4fb0.../10.21.1.152 loaded  active  running
deis-store-daemon.service   7aa4377f.../10.21.1.151 loaded  active  running
deis-store-daemon.service   860a1cd3.../10.21.2.137 loaded  active  running
deis-store-daemon.service   a6b009f5.../10.21.2.138 loaded  active  running
deis-store-daemon.service   ad04b506.../10.21.2.136 loaded  active  running
deis-store-daemon.service   f2fc4fb0.../10.21.1.152 loaded  active  running
deis-store-gateway.service  7aa4377f.../10.21.1.151 loaded  active  running
deis-store-metadata.service 7aa4377f.../10.21.1.151 loaded  active  running
deis-store-metadata.service 860a1cd3.../10.21.2.137 loaded  active  running
deis-store-metadata.service a6b009f5.../10.21.2.138 loaded  active  running
deis-store-metadata.service ad04b506.../10.21.2.136 loaded  active  running
deis-store-metadata.service f2fc4fb0.../10.21.1.152 loaded  active  running
deis-store-monitor.service  7aa4377f.../10.21.1.151 loaded  active  running
deis-store-monitor.service  860a1cd3.../10.21.2.137 loaded  active  running
deis-store-monitor.service  a6b009f5.../10.21.2.138 loaded  active  running
deis-store-monitor.service  ad04b506.../10.21.2.136 loaded  active  running
deis-store-monitor.service  f2fc4fb0.../10.21.1.152 loaded  active  running
deis-store-volume.service   7aa4377f.../10.21.1.151 loaded  active  running
deis-store-volume.service   860a1cd3.../10.21.2.137 loaded  active  running
deis-store-volume.service   a6b009f5.../10.21.2.138 loaded  active  running
deis-store-volume.service   ad04b506.../10.21.2.136 loaded  active  running
deis-store-volume.service   f2fc4fb0.../10.21.1.152 loaded  active  running

deisctl journal controller
-- Logs begin at Thu 2015-01-15 02:34:53 UTC. --
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: Installed 0 object(s) from 0 fixture(s)
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: Running migrations for api:
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: - Nothing to migrate.
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: - Loading initial data for api.
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: Installed 0 object(s) from 0 fixture(s)
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: Running migrations for guardian:
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: - Nothing to migrate.
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: - Loading initial data for guardian.
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: Installed 0 object(s) from 0 fixture(s)
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: Synced:
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > django.contrib.admin
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > django.contrib.auth
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > django.contrib.contenttypes
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > django.contrib.humanize
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > django.contrib.messages
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > django.contrib.sessions
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > django.contrib.sites
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > django.contrib.staticfiles
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > django_fsm
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > json_field
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > rest_framework
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > south
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > corsheaders
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: > web
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: Migrated:
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: - rest_framework.authtoken
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: - api
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: - guardian
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh: deis-controller running...
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh:    Starting gunicorn 19.1.1
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh:    Listening at: http://0.0.0.0:8000 (91)
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh:    Using worker: sync
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh:    Booting worker with pid: 97
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh:    Booting worker with pid: 98
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh:    Booting worker with pid: 99
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh:    Booting worker with pid: 100
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh:    Booting worker with pid: 101
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh:    Booting worker with pid: 102
Jan 15 06:58:04 ip-10-21-2-136.ap-southeast-1.compute.internal sh:    Booting worker with pid: 103

root@ec2-54-80-18-142:/opt/deis/deisctl# deisctl restart controller
deis-controller.service: inactive/dead                                 
deis-controller.service: active/running  
已邀请:

zhen - PMP, AWS Certified Solution Architect

赞同来自:


已解决,打开端口限制即可。

zhen - PMP, AWS Certified Solution Architect

赞同来自: DockOne allengaller


在AWS上安装 Deis 笔记已共享:
<ol><li>Installing Deis on AWS (http://www.dockerone.com/article/144 )</li><li>Deis 使用( Using Deis) (http://www.dockerone.com/article/145 )</li><li>管理Deis, 请等待</li></ol>

itone - 找docker教材一本

赞同来自:


用AWS的是不是挺多的?

zhen - PMP, AWS Certified Solution Architect

赞同来自:


不是很清楚数量,我用了快4年了

要回复问题请先登录注册