20 hours after created a ticket support and post in issuetracker, the issue has been solved, still no explanation though.
Not to mention that I cannot upgrade my support plan for about 20 hours earlier until I need to call support team and hours laters I finally can upgrade support plan. My frustration is it took so long and so hard to convince your engineers that it's problem on your end, not to mention how long it've been solve. And yeah, google cloud status shown all green. It took about 36 hours before P1 issue get fixed, really unacceptable. On Saturday, March 24, 2018 at 3:44:21 AM UTC+7, Navi Aujla (Google Cloud Support) wrote: > > Hello Anu > > As mentioned in my last message there are multiple factors which may cause > this error. However, If you believe this to an issue with the GCP load > balancer, I would suggest you to open a private issue report using this > link > <https://issuetracker.google.com/issues/new?component=187164&template=803901>[1] > > providing the relevant detailed information for the investigation. > > > On Friday, March 23, 2018 at 3:24:30 PM UTC-4, Anu V wrote: >> >> Backends are healthy, I found this 502 errors across my few projects >> using AppEngine. >> >> All instances are able to access and work normally, I've tested using >> curl to send a request directly to instance's private ip and it works all >> the time. >> >> >> On Saturday, March 24, 2018 at 2:07:30 AM UTC+7, Navi Aujla (Google Cloud >> Support) wrote: >>> >>> Hello Anu, >>> >>> The "*failed_to_connect_to_backend" *error message indicates that load >>> balancer is failing to connect to backends. There could be many possible >>> reasons for it. For example: Unhealthy instance if reported by health >>> check, incorrect URL mapping >>> <https://cloud.google.com/compute/docs/load-balancing/http/url-map>, >>> high backend utilization causing backend not to respond to the load >>> balancer requests. You can refer to this thread >>> <https://groups.google.com/forum/#!topic/gce-discussion/mXmnB-Ab5Z4>for >>> more information and check instance system/error and access logs. >>> >>> On Friday, March 23, 2018 at 9:06:00 AM UTC-4, Anu V wrote: >>>> >>>> I'am experiencing too many 502 errors from Load Balance and the >>>> instances are working fine. ( >>>> >>>> >>>> @type: " >>>> type.googleapis.com/google.cloud.loadbalancing.type.LoadBalancerLogEntry" >>>> >>>> statusDetails: "failed_to_connect_to_backend" >>>> >>>> I've also found that this happen on my few projects starting about 12 >>>> hours ago, I've checked https://status.cloud.google.com/ and it said >>>> all working fine. >>>> I cannot upgrade support level to create the ticket, so I am posting it >>>> here to ask if anyone having the same problem as I am? >>>> >>>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0f4ee81e-b724-4c7a-8240-f5a2514e751b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
