DataStax AMI挂起 [英] DataStax AMI hangs on

问题描述

我在亚马逊AWS使用本教程安装卡桑德拉的http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installAMILaunch.html

I am installing Cassandra on Amazon AWS using this tutorial http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installAMILaunch.html

到目前为止，我只用一个节点AMI-7f33cd08型M3-大放于子网。从AWS角度实例启动，但是当我登录，我得到马上

So far I am using just one node ami-7f33cd08 of type m3-large put in subnet. From the AWS perspective the instance launches, but when I log in I get straight away

Cluster started with these options:
--clustername myDSCcluster --totalnodes 1 --version community
Installation started..

和安装开始。的只是不断有新行插入每隔几秒钟。

And Installation started. just keeps there with newline being inserted every few seconds.

任何人都穿过这件事情来了？任何解决方案

Anyone came across this thing? Any solutions

推荐答案

由于有少数票，最近想出了周围同样的问题，却仿佛什么最近AMI供应侧内EC2更改，或该特定从未被使用过的VPC配置，这似乎有点不太可能。

Since there were a few tickets that came up recently around the same issue, it seems as though something recently changed within the AMI provisioning side in EC2, or this specific configuration of VPCs had never been used before, which seems a bit unlikely.

目前的解决办法是增加一个额外的进入的/ etc /主机名来摆脱每个sudo命令后发生的stderr输出的。这反过来又不会被标记为对供应方的错误。

The current fix is to add an additional entry into /etc/hostname to get rid of the stderr output that occurs after each sudo command. This in turn doesn't get flagged as an error on the provisioning side.

这已得到修复和修补的记录在这张票： https://github.com/riptano/ComboAMI/issues/51 。

This has been fixed and patched as documented on this ticket: https://github.com/riptano/ComboAMI/issues/51.

如果你发现任何其他问题，请随时创建另一票那里。

If you spot any additional issues, feel free to create another ticket there.

展望未来，只要启动另一套实例使用相同的用户数据，你应该启动和运行。

Going forward, just launch another set of instances using the same user-data and you should be up and running.

这篇关于DataStax AMI挂起的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！