i have a cluster in Google Cloud with a static IP set up. This has been working fine more than a year. Recently I noticed that when I start the cluster and try to open JupyterLabs I get a gateway timeout error or "This page isn't working ...dataproc.googleusercontent.com is currently unable to handle this request".
I have scheduled jobs running on this cluster and they run just fine. I have other clusters and when I open those up it's also fine.
I just thinking is there any other fix I could try than just redoing the cluster.
Thanks
Related
I am doing this ECS fargate tutorial. I followed prerequisites and each step but cannot access a webpage in step 4. The chrome browser error msg is like
This site can't be reached
container.public.ip.address took too long to respond.
：
ERR_CONNECTION_TIMED_OUT
I am not sure where I went wrong but it seems web server does not respond properly.
What I did so far is
Increased resource(both cpu and memory)
checked security group settings
checked the service is supported in my region
changed browser to access the webpage
did a little search here and on the internet
but nothing works out.
Additional info: my region is ap-northeast-1.
Cound you give me some tips?
I'm just trying to launch EC2 instance with open litespeed wordpress. Once everything is setup and the instance sayings running, the IP still loading and finally shows timed error. This happens only with the openlitespeed wordpress image.
I don't think this is something we as a community can fix but don't quote me on that, have you tried contacting AWS support and running through troubleshooting? That could fix your issue.
I have a dockerized Node.JS express application that I am migrating to AWS from Google Cloud. I had done this before successfully on the same project before deciding Cloud Run was more cost effective because of their free tier. Now, wanting to switch back to Fargate, but am unable to do it again due what I'm guessing is a crucial step. For minimal setup, I used the following guide: https://docs.docker.com/cloud/ecs-integration/ Essentially, using docker compose up with aws context and project name to deploy to ECS and Fargate.
The Load Balancer gives me a public DNS name in the format: xxxxx.elb.us-west-2.amazonaws.com and I have defined a port of 5002 in my Docker container. I know the issue is not related to exposing port numbers or any code-related issue since I had this successfully running in Google Cloud Run. When I try to hit any of my express endpoints, by sending POST to xxxxx.elb.us-west-2.amazonaws.com:5002/my_endpoint, I end up with Error: Request Timed Out
Note: I have already verified that my inbound security rules have been set to all traffic.
I am very new to AWS, so would love guidance if I am missing a critical step.
Thanks!
EDIT (SOLUTION): Turns out everything was deploying correctly, but after checking CloudWatch Logs, it turns out Fargate can't read environment variables defined inside of docker-compose file. Instead, they need to be defined in .env files, then read in docker-compose through -env-file flag. My code was then trying to listen on a port that was in environment variable but was undefined, so was receiving the below error in CloudWatch.
We have created a Ubuntu-based GCP VM instance which has 2xNvidiaT4 GPU. We have noticed that after a while, it stops responding. However on the GCP console, the status shows as Running; but when we try to access via GCP SSH also it doesn't respond. When we STOP n START, it works fine.
What could be the issue?
I am running Bitnami WordPress on AWS server website working since two days but suddenly it stop showing anything and connection timeout is showing. The instance EC2 is running perfectly fine, and I have also seen IP logs, and nothing suspicious has come up.
Based on the above comments I guess the issue is with the internal web server
Make sure that the web server is running perfectly fine. And I do not mean just checking the EC2 instance state, because it is possible that the EC2 instance is running but the web server is down, causing the issue