I am having an issue that is causing me to pull my hair out. I have an vm instance running in GCP and all I basically want to do is move it from the zone USA to EUROPE as it connects to a database in EUROPE remotely.
I have created a snapshot and then spun up a new instance in EUROPE via said snapshot but I can't for the life of me SSH onto it or even ping it! It gives me an intermitant ping every so often which is really strange and even using gcloud to ssh onto it using the
gcloud compute config-ssh
doesn't work. It just times out. There is no firewall on the instance itself and all the relevant ports are open on the GCP firewall. Am I missing something? Is there a setting on the instance itself that is stopping me from replicating it?
I'm a bit puzzled by a strange situation. I'll add that the configuration of openvpn (using EC2 AWS instances) is rather postural according to official guides.
I tried to give different ip by closing instances and running it. Besides that i have also assigns elastic IP to the instance but it doesn't give anything.
I can't get into Twitter. Other sites work very well. Every time i gets Too Many Requests information. What is this and how to get around it ? -my pc home system is ubuntu (without dns leaks)
I am testing the free services from Amazon EC2. I followed the manual and was able to access the server. After one minute inside the server, it crashes and I have to close my console and reboot the instance.
By reading the guides from Amazon, I found that I should set the Route Table, which I was not able to find. Maybe the dashboard has changed.
I've spun up and setup 2 servers now in this AZ and both keep going down shortly after being used. Restarting doesn't fix it and I have to start and stop them.
By going down I mean a timeout error for apache and I can't even SSH. Port 22 is open and I can SSH in once I stop and start the EC2, it doens't run out of memory and only has 2 sites on a t2.medium with the database on RDS.
One of the sites is https://coffeehive.com.au/ if that helps
Any ideas?
Cheers,
Adrian
I booted the DataStax AMI for Amazon EC2, logged in via SSH, but the terminal hangs on "Installation Started":
Cluster started with these options:
--clustername CassandraDev --totalnodes 1 --version enterprise --username **** --password ****
Installation started.
"Installation started" keeps going through suffixes consisting of one, two, and three dots. But nothing happens, I can't quit the installation process, and I can't access any log files to see what might be going on (or I don't know how).
Tried on two separate m3.large instances operating in a VPC subnet, at the us-east-1 region. The exact AMI is datastax_clustering_ami_2.5.1_hvm.manifest.xml (ami-ada2b6c4). On the first instance, I waited about an hour and a half. The second instance I just left online all night, with the same results.
Because this is a VPC, all outbound traffic goes through a NAT server. Security groups allow outbound traffic only on ports 80, 443, and 123. Might there be another outbound port that needs to be opened? Inbound ports do not matter, as the server is not public-facing, but within the subnet I have allowed all traffic on all ports.
Someone else has had a similar issue, but without answers so far: DataStax AMI hangs on
Any help would be appreciated!
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.
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.
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.