502 Bad Gateway on the /transport/conflicts endpoint on production server (instantaneous failure)

hackoregon / transportation-backend

Transportation backend repo - 2016 and 2017

8 stars 7 forks source link

502 Bad Gateway on the /transport/conflicts endpoint on production server (instantaneous failure) #44

Closed leobender closed 7 years ago

leobender commented 7 years ago

502 appears to be coming from the AWS load balancer.
Cloudwatch is not logging any issues with the transport container
Endpoint is functional but slow when running in a local container

URL: http://hacko-integration-658279555.us-west-2.elb.amazonaws.com/transport/conflicts/

znmeb commented 7 years ago

which endpoint is it? the "transport/features" endpoint takes a couple of minutes to gather all of them! If we're going to use that, can we cache it? Data will not be changing!!!

sanjuroj commented 7 years ago

It's the conflicts endpoint that's not working. The features endpoint will be used with a set of filters that makes it much faster to load.

znmeb commented 7 years ago

would having a PgAdmin4 server in the instance help troubleshoot? I've got a way to do that now.

sanjuroj commented 7 years ago

Tony's looking at the problem, I think he'll let us know if he needs something. Good to know though.

znmeb commented 7 years ago

@sanjuroj @MikeTheCanuck Is this still open?

sanjuroj commented 7 years ago

Nope. It was a memory issue one the server, and they bumped up the memory. I'm have no idea what the deployment looks like now so I'll close this. They can open a new ticket if they have a problem.