Hello Yi,
503 is a back-end error, and a little too general to be useful. You mention
that you have recently changed your app's business logic. This might have
impacted your back-end behavior, and thus result in these 503 errors. The
recommended practice, in such cases, is to implement
Did this issue get resolved? I see a lot of 502 Bad Gateway errors since my
last components upgrade ~ 2weeks.
On Friday, July 6, 2018 at 9:31:50 AM UTC-7, yi he wrote:
>
> Hello,
> I met a issue.
> Everything works fine at the begin of this week. In the middle of the
> week, user reported can
Also how to debug the failure? Is the error related?
INFO: Error body: RPC Error: /StubbyService.Send to (unknown) : APP_ERROR(2)
On Friday, July 6, 2018 at 12:41:41 PM UTC-5, yi he wrote:
>
> Yes. It is flexible environment. In fact, I deployed again last night and
> it worked. But I found
Yes. It is flexible environment. In fact, I deployed again last night and
it worked. But I found it broken again this morning.
The same code worked very well last week. I didn't change any config file
and only change business logic code.
On Friday, July 6, 2018 at 12:32:53 PM UTC-5, Giuliano
It's on Flex, right ?
As the Flex requires an answer on the default port, have you sure your app
is running at least on the local development env ?
On Friday, July 6, 2018 at 6:30:00 PM UTC+1, yi he wrote:
>
> Thanks Giuliano,
>
> I saw some failures.
>
> A INFO: End of request or previous
Thanks Giuliano,
I saw some failures.
A INFO: End of request or previous flush has not yet completed, blocking.
A Jul 06, 2018 5:14:44 PM com.google.apphosting.vmruntime.VmApiProxyDelegate
runSyncCall
A INFO: Error body: RPC Error: /StubbyService.Send to (unknown) : APP_ERROR(2)
Hi Yi,
do you took a look on StackDrive logging? Any issues on the instances
startup?
On Friday, July 6, 2018 at 5:31:50 PM UTC+1, yi he wrote:
>
> Hello,
> I met a issue.
> Everything works fine at the begin of this week. In the middle of the
> week, user reported can not access the
