[google-appengine] Re: Google App Engine Front Controller removes Cookies from Response Header

['barrado' via Google App Engine]

Hi,

According to the App Engine Standard documentation 

 some 
headers are ignored and removed from the request response. Also headers 
with non-ASCII characters in either the name or value are removed. I am not 
sure if this applies to your case but you might want to look at that 
documentation and see if this is your case.

On Tuesday, March 15, 2022 at 11:35:54 AM UTC+1 ajithof...@gmail.com wrote:

> Google App Engine's Front Controller removes the cookies from the response 
> header set by my Laravel Framework 8.83.4 / PHP 7.4 application.
>
> Cookie's are being set properly when hosted locally. But, they are not set 
> when I hosted it on Google's App Engine. So, Users can't persist the login 
> session.
>
> *curl -i http://localhost:8000/login *
>
>
>
>
>
>
>
>
>
>
> *HTTP/1.1 200 OKHost: localhost:8000Date: Tue, 15 Mar 2022 02:58:10 
> GMTConnection: closeX-Powered-By: PHP/7.4.13Content-Type: text/html; 
> charset=UTF-8Cache-Control: no-cache, privateDate: Tue, 15 Mar 2022 
> 02:58:09 GMTSet-Cookie: XSRF-TOKEN=eyjIiwidGFnIjoiIn0%3D; 
> expires=Tue, 15-Mar-2022 04:58:09 GMT; Max-Age=7199; path=/; 
> samesite=laxSet-Cookie: laravel_session=ey Hash>0IiwidGFnIjoiIn0%3D; expires=Tue, 15-Mar-2022 04:58:09 GMT; 
> Max-Age=7199; path=/; httponly; samesite=lax*
>
> *curl -i < App Engine Hosted application URL >*
>
>
>
>
>
>
>
> *HTTP/1.1 200 OKContent-Type: text/html; charset=UTF-8Vary: 
> Accept-EncodingX-Cloud-Trace-Context: 
> 059b8f86bf1606e70b01890a017f1b61;o=1Date: Tue, 15 Mar 2022 02:56:57 
> GMTServer: Google FrontendContent-Length: 10005Alt-Svc: h3=":443"; 
> ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; 
> ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; 
> ma=2592000,quic=":443"; ma=2592000; v="46,43"*
>
> Here is the snip of *index.php*. I tried dumping the response (Commented 
> below). My application is properly adding cookie to the response header. 
> But, front controller removes it I think.
>
> *Index.php*
>
>
>
>
>
>
>
>
>
>
>
>
> *$app = require_once __DIR__.'/../bootstrap/app.php';$kernel = 
> $app->make(Kernel::class);$response = $kernel->handle($request = 
> Request::capture());// dd($response); // Response contains cookie. Headers 
> are similar to the locally hosted app.$response->send(); // Response 
> doesn't contain cookie. Front controller is removing the cookie I 
> think.$kernel->terminate($request, $response);*
>
>
> Some people have discussed to set the cookie at the top of each and every 
> HTML page. But, that is not convenient and scalable for us.
>
> If using our own php server instead of Google App Engine's Front 
> Controller is the solution, Let me know the correct way to set 
> *entrypoint* in *app.yaml*
>
> Please guide me to the correct way to resolve this issue. Thanks.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7bd248d3-c905-45a4-a6b1-67c1fcfcbe02n%40googlegroups.com.

Re: [google-appengine] Re: Google App Engine Unstable

['Lluis Munoz Ladron de Guevara' via Google App Engine]

Hello,

I would like to address Hung's question. 

Currently there are a few ways you can look for help to solve an issue even 
if you don't have a support plan. Which one you use mainly depends on where 
you think the root cause of your issue is. 

If you think the root cause is on our side we encourage you to report it 
using Google Issue Tracker. When creating one you will be presented with a 
template on some fields that will help us understand the issue. More 
information about this can be found here 
. 

On the other hand, if you think the root cause can be on your side, I would 
recommend using the Logs Explorer to check what error code you are 
getting.  Once you know the error code you can search for it in our 
documentation, which often explains what the root cause is and some 
guidelines on how to solve them.  However if you can't find a solution in 
our documentation or this is not detailed enough you can create a question 
in Stackoverflow. 

Additionally, if you would like to discuss any GCP related matter with the 
community we encourage you to use Groups. 

More information about the Community support can be found here 
. 


On Tuesday 14 December 2021 at 16:51:23 UTC+1 ime...@gmail.com wrote:

> I pay support and have reported it today. I'll let you know their answer.
>
> On Tue, Dec 14, 2021 at 9:37 AM Hung Nguyen  wrote:
>
>> I got this problem on with my app  twice on Friday Dec10 too. And it's 
>> happening again now at this moment ( 10:20am,  Dec14).
>>
>> Being a startup business, we can't afford buying a Google support plan 
>> yet. Is there anyway we can report the problem to the right team and have 
>> its investigated 
>> or someone can point us to resources that we can investigate on our side 
>> if the root cause is potentially on our side?
>>
>> We have never experienced this problem for our app.
>>
>> Thanks!
>>
>> -Hung
>>
>>
>> On Friday, December 10, 2021 at 5:29:50 PM UTC-5 ad...@worshipextreme.com 
>> wrote:
>>
>>> I'm experiencing issues with Google App Engine this morning too.  
>>> Requests are spinning for 5+ mins, then the next request goes through 
>>> fine.  Please investigate.
>>>
>>> On Friday, December 10, 2021 at 2:00:25 PM UTC-5 Elliott (Cloud Platform 
>>> Support) wrote:
>>>
 Hello,

 I understand that you would like to report downtime and instability in 
 your App Engine application. Please note that you may follow all outages 
 or 
 infrastructure issues using the Google Cloud Dashboard 
 [1]. Looking at it briefly, I am 
 unable to find issues related to App Engine for Friday.

 Google Groups is meant for general discussions and opinions about 
 Google products. In this case, I would suggest reaching out to our regular 
 support channel [2] to report 
 instabilities related to your App Engine instance.

 If you would like to report a general issue related to our products, I 
 encourage you to use Google Issue Tracker 
 [3], which we 
 will investigate.

 [1] https://status.cloud.google.com/

 [2] https://cloud.google.com/support/docs
 [3] https://cloud.google.com/support/docs/issue-trackers

 On Friday, December 10, 2021 at 11:20:48 AM UTC-5 ime...@gmail.com 
 wrote:

> Hi, has anyone experienced downtimes and instability of their app 
> engines web applications and endpoints, this Friday morning? I haven't 
> had 
> and issue since July 2nd 2019.
>
 -- 
>> 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 google-appengi...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/358e0a27-82dd-4993-b280-b3eb9b665fe0n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ba9e900a-e13b-44f8-b341-5dcee696f801n%40googlegroups.com.

Re: [google-appengine] Re: Google App Engine Unstable

[Isaac Meany]

I pay support and have reported it today. I'll let you know their answer.

On Tue, Dec 14, 2021 at 9:37 AM Hung Nguyen  wrote:

> I got this problem on with my app  twice on Friday Dec10 too. And it's
> happening again now at this moment ( 10:20am,  Dec14).
>
> Being a startup business, we can't afford buying a Google support plan
> yet. Is there anyway we can report the problem to the right team and have
> its investigated
> or someone can point us to resources that we can investigate on our side
> if the root cause is potentially on our side?
>
> We have never experienced this problem for our app.
>
> Thanks!
>
> -Hung
>
>
> On Friday, December 10, 2021 at 5:29:50 PM UTC-5 ad...@worshipextreme.com
> wrote:
>
>> I'm experiencing issues with Google App Engine this morning too.
>> Requests are spinning for 5+ mins, then the next request goes through
>> fine.  Please investigate.
>>
>> On Friday, December 10, 2021 at 2:00:25 PM UTC-5 Elliott (Cloud Platform
>> Support) wrote:
>>
>>> Hello,
>>>
>>> I understand that you would like to report downtime and instability in
>>> your App Engine application. Please note that you may follow all outages or
>>> infrastructure issues using the Google Cloud Dashboard
>>> [1]. Looking at it briefly, I am
>>> unable to find issues related to App Engine for Friday.
>>>
>>> Google Groups is meant for general discussions and opinions about Google
>>> products. In this case, I would suggest reaching out to our regular
>>> support channel [2] to report
>>> instabilities related to your App Engine instance.
>>>
>>> If you would like to report a general issue related to our products, I
>>> encourage you to use Google Issue Tracker
>>> [3], which we
>>> will investigate.
>>>
>>> [1] https://status.cloud.google.com/
>>>
>>> [2] https://cloud.google.com/support/docs
>>> [3] https://cloud.google.com/support/docs/issue-trackers
>>>
>>> On Friday, December 10, 2021 at 11:20:48 AM UTC-5 ime...@gmail.com
>>> wrote:
>>>
 Hi, has anyone experienced downtimes and instability of their app
 engines web applications and endpoints, this Friday morning? I haven't had
 and issue since July 2nd 2019.

>>> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/358e0a27-82dd-4993-b280-b3eb9b665fe0n%40googlegroups.com
> 
> .
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAJtQXJ70aMfjSxdA%2BW%3DWYN-PgpXfVoxjrYi%3DaVamjYNbdfQnyg%40mail.gmail.com.

[google-appengine] Re: Google App Engine Unstable

[Hung Nguyen]

I got this problem on with my app  twice on Friday Dec10 too. And it's 
happening again now at this moment ( 10:20am,  Dec14).

Being a startup business, we can't afford buying a Google support plan yet. 
Is there anyway we can report the problem to the right team and have its 
investigated 
or someone can point us to resources that we can investigate on our side if 
the root cause is potentially on our side?

We have never experienced this problem for our app.

Thanks!

-Hung


On Friday, December 10, 2021 at 5:29:50 PM UTC-5 ad...@worshipextreme.com 
wrote:

> I'm experiencing issues with Google App Engine this morning too.  Requests 
> are spinning for 5+ mins, then the next request goes through fine.  Please 
> investigate.
>
> On Friday, December 10, 2021 at 2:00:25 PM UTC-5 Elliott (Cloud Platform 
> Support) wrote:
>
>> Hello,
>>
>> I understand that you would like to report downtime and instability in 
>> your App Engine application. Please note that you may follow all outages or 
>> infrastructure issues using the Google Cloud Dashboard 
>> [1]. Looking at it briefly, I am 
>> unable to find issues related to App Engine for Friday.
>>
>> Google Groups is meant for general discussions and opinions about Google 
>> products. In this case, I would suggest reaching out to our regular 
>> support channel [2] to report 
>> instabilities related to your App Engine instance.
>>
>> If you would like to report a general issue related to our products, I 
>> encourage you to use Google Issue Tracker 
>> [3], which we will 
>> investigate.
>>
>> [1] https://status.cloud.google.com/
>>
>> [2] https://cloud.google.com/support/docs
>> [3] https://cloud.google.com/support/docs/issue-trackers
>>
>> On Friday, December 10, 2021 at 11:20:48 AM UTC-5 ime...@gmail.com wrote:
>>
>>> Hi, has anyone experienced downtimes and instability of their app 
>>> engines web applications and endpoints, this Friday morning? I haven't had 
>>> and issue since July 2nd 2019.
>>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/358e0a27-82dd-4993-b280-b3eb9b665fe0n%40googlegroups.com.

[google-appengine] Re: Google App Engine Unstable

['Lluis Munoz Ladron de Guevara' via Google App Engine]

Hello,

Thank you for reporting this issue.

I would like to add to Elliott's message saying that some isolated issues 
might not report to the Status Dashboard  if 
those only affect a limited number of users, more information about his can 
be found here 

. 

Additionally, I would like to reiterate what Elliott said, if you suspect 
that the root cause of an issue you are experiencing might be caused by an 
issue on our side please file a support case 
 or report it using Google Issue 
Tracker . 



On Friday 10 December 2021 at 23:29:50 UTC+1 ad...@worshipextreme.com wrote:

> I'm experiencing issues with Google App Engine this morning too.  Requests 
> are spinning for 5+ mins, then the next request goes through fine.  Please 
> investigate.
>
> On Friday, December 10, 2021 at 2:00:25 PM UTC-5 Elliott (Cloud Platform 
> Support) wrote:
>
>> Hello,
>>
>> I understand that you would like to report downtime and instability in 
>> your App Engine application. Please note that you may follow all outages or 
>> infrastructure issues using the Google Cloud Dashboard 
>> [1]. Looking at it briefly, I am 
>> unable to find issues related to App Engine for Friday.
>>
>> Google Groups is meant for general discussions and opinions about Google 
>> products. In this case, I would suggest reaching out to our regular 
>> support channel [2] to report 
>> instabilities related to your App Engine instance.
>>
>> If you would like to report a general issue related to our products, I 
>> encourage you to use Google Issue Tracker 
>> [3], which we will 
>> investigate.
>>
>> [1] https://status.cloud.google.com/
>>
>> [2] https://cloud.google.com/support/docs
>> [3] https://cloud.google.com/support/docs/issue-trackers
>>
>> On Friday, December 10, 2021 at 11:20:48 AM UTC-5 ime...@gmail.com wrote:
>>
>>> Hi, has anyone experienced downtimes and instability of their app 
>>> engines web applications and endpoints, this Friday morning? I haven't had 
>>> and issue since July 2nd 2019.
>>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/53e88fd2-159a-4896-adb3-eadad1956838n%40googlegroups.com.

[google-appengine] Re: Google App Engine Unstable

['Adam Meyer' via Google App Engine]

I'm experiencing issues with Google App Engine this morning too.  Requests 
are spinning for 5+ mins, then the next request goes through fine.  Please 
investigate.

On Friday, December 10, 2021 at 2:00:25 PM UTC-5 Elliott (Cloud Platform 
Support) wrote:

> Hello,
>
> I understand that you would like to report downtime and instability in 
> your App Engine application. Please note that you may follow all outages or 
> infrastructure issues using the Google Cloud Dashboard 
> [1]. Looking at it briefly, I am unable 
> to find issues related to App Engine for Friday.
>
> Google Groups is meant for general discussions and opinions about Google 
> products. In this case, I would suggest reaching out to our regular 
> support channel [2] to report 
> instabilities related to your App Engine instance.
>
> If you would like to report a general issue related to our products, I 
> encourage you to use Google Issue Tracker 
> [3], which we will 
> investigate.
>
> [1] https://status.cloud.google.com/
>
> [2] https://cloud.google.com/support/docs
> [3] https://cloud.google.com/support/docs/issue-trackers
>
> On Friday, December 10, 2021 at 11:20:48 AM UTC-5 ime...@gmail.com wrote:
>
>> Hi, has anyone experienced downtimes and instability of their app engines 
>> web applications and endpoints, this Friday morning? I haven't had and 
>> issue since July 2nd 2019.
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/fcdf0770-b39d-4942-a843-d1c2f49859d1n%40googlegroups.com.

[google-appengine] Re: Google App Engine Unstable

['Elliott (Cloud Platform Support)' via Google App Engine]

Hello,

I understand that you would like to report downtime and instability in your 
App Engine application. Please note that you may follow all outages or 
infrastructure issues using the Google Cloud Dashboard 
[1]. Looking at it briefly, I am unable 
to find issues related to App Engine for Friday.

Google Groups is meant for general discussions and opinions about Google 
products. In this case, I would suggest reaching out to our regular support 
channel [2] to report instabilities 
related to your App Engine instance.

If you would like to report a general issue related to our products, I 
encourage you to use Google Issue Tracker 
[3], which we will 
investigate.

[1] https://status.cloud.google.com/

[2] https://cloud.google.com/support/docs
[3] https://cloud.google.com/support/docs/issue-trackers

On Friday, December 10, 2021 at 11:20:48 AM UTC-5 ime...@gmail.com wrote:

> Hi, has anyone experienced downtimes and instability of their app engines 
> web applications and endpoints, this Friday morning? I haven't had and 
> issue since July 2nd 2019.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d36dd9c7-65ad-4439-8e10-64cee5eaaecbn%40googlegroups.com.

[google-appengine] Re: Google App Engine Hello world program using Python 3 Problem Reg.,

[NoCommandLine]

Hi,

It looks like you are running dev_appserver.py on a Windows environment. 
Per Google Documentation 
,
 
this is not supported for Python 3
.. *The dev_appserver tool does not support development of Python 3 
apps on Windows*..


*.* NoCommandLine *..*
 https://nocommandline.com

*A GUI for Google App Engine*

On Monday, September 27, 2021 at 11:34:04 AM UTC-7 sathish...@gmail.com 
wrote:

> i tried to create Google App Engine Hello world program using Python 3. 
> But i am getting same error message lot of times. i am using python 
> standard environment. herewith i have attached the error message screenshot 
> to you. kindly rectify that
>
> Thank you
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a481d5a8-2ed0-4174-a9f0-49c3750c875an%40googlegroups.com.

[google-appengine] Re: google app engine connect to external database

[Pablo Lopez]

Try this:

Go into the iam-admin for the project  you want to give access to the DB 
and look for the service account it would be something like 
[project_id]@appspot.gserviceaccount.com, copy it, then in the same page, 
change the project to the one that hast the MySQL instance and clic Add+ 
and give the service account the Cloud SQL Client role. 

Cheers

On Monday, August 2, 2021 at 7:44:23 AM UTC-6 luciano...@gmail.com wrote:

> Hello people. I have two Java projects running on AppEngine, one of the 
> projects has a MySQL instance and is already connected to AppEngine. I 
> would like both projects to connect to the same database. I've already 
> activated the Cloud SQL APIs, Cloud SQL Admin even so it didn't work, I'm 
> getting the following error:
>
> {
>  "code": 403,
>  "errors": [
>  {
>  "domain": "global",
>  "message": "The client is not authorized to make this 
> request.",
>  "reason": "notAuthorized"
>  }
>  ],
>  "message": "The client is not authorized to make this request."
> }
>
> can you help me?
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1713b303-54c7-4ced-8a51-fb97b74d1908n%40googlegroups.com.

Re: [google-appengine] Re: Google App Engine - Split Traffic and promote

['Jordi (Google Cloud Platform Support)' via Google App Engine]

Hello, 

To move from one version to another gradually you should take a look at 
Traffic migration. [1]
Note that this is not supported in the App Engine flexible environment.

[1] 
https://cloud.google.com/appengine/docs/admin-api/migrating-splitting-traffic

On Wednesday, June 16, 2021 at 7:34:23 PM UTC+2 bha...@gmail.com wrote:

> Oh thanks George!
>
> Either I use two services of the same code base one for prod and one for 
> staging. Or opt for two projects, one for prod and the other for staging?
>
> Then, traffic splitting works against a single service (without the 
> version specified in the URL). In other words, traffic is split among the 
> versions of the service and not among two different services.
>
> Is there a way to automate moving from one version to another gradually?
>
> On Wed, Jun 16, 2021 at 7:46 PM 'George (Cloud Platform Support)' via 
> Google App Engine  wrote:
>
>> Hello, 
>>
>> You are right, you can use traffic splitting to specify a percentage 
>> distribution of traffic across two or more of the versions within a 
>> service, as detailed on the "Split Traffic" page 
>> . 
>> Deploying with --promote would attract all traffic to the deployed version. 
>> However, by contrast, traffic splitting is applied to URLs that do not 
>> explicitly target a version. In other words, you'll need 2 separate 
>> services, one for your prod environment, the other for staging. Two 
>> versions would not work for traffic splitting. 
>>
>> You can access different versions by version URLs at any time. 
>>
>> On Tuesday, 15 June 2021 at 08:28:05 UTC-4 bha...@gmail.com wrote:
>>
>>>
>>> Hi,
>>> I would like to understand the relation between --promote (--no-promote) 
>>> and split traffic.
>>>
>>> - When I make a version deployment (--promote), it means it takes 100% 
>>> of the traffic
>>> - When I make a version deployment (--no-promote), it won't take any 
>>> traffic percentage. 
>>> *However, would I be able to visit this version by URL? Would this 
>>> version be stopped or active?*
>>> - Split Traffic it works sort of against (--promote). We use it when we 
>>> want to split the traffic among versions instead of promoting a single 
>>> version.
>>>
>>> I am planning to have two versions of my app. One is prod and another 
>>> staging.
>>>
>>> Only prod should serve clients. While staging should only be used 
>>> internally for testing, etc.
>>>
>>> Shall I use *--promote* with the prod environment and *--no-promote* 
>>> with the staging one?
>>>
>>> Thanks
>>> Bill
>>>
>> -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "Google App Engine" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-appengine/kJO6TBILzxI/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-appengi...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/9d2dbb80-b62e-4f84-b372-5567ac7af1b6n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/24726306-f85e-4c24-89f8-a618bbe3ab94n%40googlegroups.com.

Re: [google-appengine] Re: Google App Engine - Split Traffic and promote

[Bilal Haidar]

Oh thanks George!

Either I use two services of the same code base one for prod and one for
staging. Or opt for two projects, one for prod and the other for staging?

Then, traffic splitting works against a single service (without the version
specified in the URL). In other words, traffic is split among the versions
of the service and not among two different services.

Is there a way to automate moving from one version to another gradually?

On Wed, Jun 16, 2021 at 7:46 PM 'George (Cloud Platform Support)' via
Google App Engine  wrote:

> Hello,
>
> You are right, you can use traffic splitting to specify a percentage
> distribution of traffic across two or more of the versions within a
> service, as detailed on the "Split Traffic" page
> .
> Deploying with --promote would attract all traffic to the deployed version.
> However, by contrast, traffic splitting is applied to URLs that do not
> explicitly target a version. In other words, you'll need 2 separate
> services, one for your prod environment, the other for staging. Two
> versions would not work for traffic splitting.
>
> You can access different versions by version URLs at any time.
>
> On Tuesday, 15 June 2021 at 08:28:05 UTC-4 bha...@gmail.com wrote:
>
>>
>> Hi,
>> I would like to understand the relation between --promote (--no-promote)
>> and split traffic.
>>
>> - When I make a version deployment (--promote), it means it takes 100% of
>> the traffic
>> - When I make a version deployment (--no-promote), it won't take any
>> traffic percentage.
>> *However, would I be able to visit this version by URL? Would this
>> version be stopped or active?*
>> - Split Traffic it works sort of against (--promote). We use it when we
>> want to split the traffic among versions instead of promoting a single
>> version.
>>
>> I am planning to have two versions of my app. One is prod and another
>> staging.
>>
>> Only prod should serve clients. While staging should only be used
>> internally for testing, etc.
>>
>> Shall I use *--promote* with the prod environment and *--no-promote*
>> with the staging one?
>>
>> Thanks
>> Bill
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/kJO6TBILzxI/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/9d2dbb80-b62e-4f84-b372-5567ac7af1b6n%40googlegroups.com
> 
> .
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAFDSF-3bdd9kMuheJ%2B%3DXZY7vCKYJdfjQwOp95cPQRn_ivS1Gjw%40mail.gmail.com.

[google-appengine] Re: Google App Engine - Split Traffic and promote

['George (Cloud Platform Support)' via Google App Engine]

Hello, 

You are right, you can use traffic splitting to specify a percentage 
distribution of traffic across two or more of the versions within a 
service, as detailed on the "Split Traffic" page 
. 
Deploying with --promote would attract all traffic to the deployed version. 
However, by contrast, traffic splitting is applied to URLs that do not 
explicitly target a version. In other words, you'll need 2 separate 
services, one for your prod environment, the other for staging. Two 
versions would not work for traffic splitting. 

You can access different versions by version URLs at any time. 

On Tuesday, 15 June 2021 at 08:28:05 UTC-4 bha...@gmail.com wrote:

>
> Hi,
> I would like to understand the relation between --promote (--no-promote) 
> and split traffic.
>
> - When I make a version deployment (--promote), it means it takes 100% of 
> the traffic
> - When I make a version deployment (--no-promote), it won't take any 
> traffic percentage. 
> *However, would I be able to visit this version by URL? Would this version 
> be stopped or active?*
> - Split Traffic it works sort of against (--promote). We use it when we 
> want to split the traffic among versions instead of promoting a single 
> version.
>
> I am planning to have two versions of my app. One is prod and another 
> staging.
>
> Only prod should serve clients. While staging should only be used 
> internally for testing, etc.
>
> Shall I use *--promote* with the prod environment and *--no-promote* with 
> the staging one?
>
> Thanks
> Bill
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9d2dbb80-b62e-4f84-b372-5567ac7af1b6n%40googlegroups.com.

Re: [google-appengine] Re: Google App Engine TCP Connections

[Bradley Barrows]

Hi,
I found the issue and the solution.

I thought that GCP was killing off the VM/container running the App Engine 
server as the logging and request handling would just STOP right when this 
larger query was made. I was sure it had something to do with the limit on 
the amount of data that an App Engine service could request from another 
service though. However, this is a TCP connection to the MongoDB. And as 
HTTP has a 32MB limit, TCP supposedly as no limit. So for a while we just 
modified the query to return a much smaller result while I continued to 
search for an answer.

The weirdest part was that this HTTP route/App Engine service would work 
most of the time, handling very large queries without issues. The issue 
though is that it needs to run on a cron/Cloud Scheduler at midnight. With 
consistency, working every time. But it was failing some nights for some 
unknown reason. And I couldn't find any exceptions in the logs from the 
code. The issue is that I had somehow missed an error message, probably due 
to our over zealous logging, from Google App Engine itself letting me know 
about memory constraints.

So yesterday we had the same issue. 

Searching through the logs I find that the HTTP request that we were making 
to this App Engine service which does this large query was failing. It was 
scheduled in Scheduler so I could see there in the logs that it errored out.

Looking through the logs I found this gem of a log message:

"Exceeded soft memory limit of 256 MB with 269 MB after servicing 0 
requests total. Consider setting a larger instance class in app.yaml."

It turns out that the VM/container (whatever is being used to host an 
AppEngine service) has a maximum memory limit of 256MB by default. And some 
nights our site would not get many requests or a fresh AppEngine server 
would be spun up and handle the expensive query request on it's own. Free 
to use all 256 MB of memory. Otherwise it was sharing memory with all the 
other "normal" requests that were coming through our service.

So to solve this I just created a Dockerfile, basically the template 
provided by the documentation, created the image, uploaded to the Container 
Registry and created a Cloud Run instance. So now we have routing to a 
service dedicated to handling requests for these expensive requests (memory 
wise) and we can even configure easily what the memory limit is on the 
different Cloud Run services.

So the issue it turns out was that we ran out of RAM in a shared 
environment and the solution was to move the service off to it's own 
hosting solution, Cloud Run. So we could route these expensive requests and 
only these requests to these new Cloud Run instances dedicated to being 
able to handle the load of the query.

Thank you so much for you time, any one who tried to help!

Thanks and hope this is helpful for anyone else,
Brad Barrows

On Wednesday, June 9, 2021 at 8:59:38 AM UTC-7 Bradley Barrows wrote:

> I thought that the original post did not actually send. My browser quit 
> right after hitting send so I re wrote it.
>
> I also found no acknowledgement that the original was received so had no 
> way of verifying if I needed to re type it or not.
>
> Sorry about that.
>
> Thanks
> Brad
>
> On Wed, Jun 9, 2021 at 3:01 AM 'Angel (Google Cloud Platform Support)' via 
> Google App Engine  wrote:
>
>> Hello Brad,
>>
>> I believe this is a similar, if not the same question that has already 
>> been answered here [1]. Please let me know if this is the case or if I 
>> misunderstood your question.
>>
>> Kind regards.
>> __
>> [1] - 
>> https://groups.google.com/g/google-appengine/c/Lj6qaT2lC90/m/TvhGSteRAwAJ
>>
>> On Tuesday, June 8, 2021 at 9:05:27 AM UTC+2 bradeba...@gmail.com wrote:
>>
>>> Hi
>>>
>>> I have a NodeJS App Engine server which is awaiting a MongoDB query 
>>> which, when reaching a certain size, never returns. There is no exception 
>>> thrown from App Engine either. It is as if the process is just killed 
>>> because execution flow and therefore logging from the process making the 
>>> MongoDB query stops.
>>>
>>> If this were a request to a HTTP server I could look at the limits and 
>>> quotas page and see that a maximum of 32MB requests and response size is 
>>> allowed.
>>>
>>> I am unable to find any limits or quotas for TCP connections from an App 
>>> Engine server.
>>>
>>> We temporarily solved the issue by using a limit or projection to 
>>> decrease the amount of data returned by the MongoDB query. When less data 
>>> is sent back to the App Engine server execution continues and the server 
>>> runs as expected.
>>>
>>> I was wondering if it was possible if at some point if TCP data usage 
>>> reaches a limit will the App Engine process be killed? Without any logging? 
>>> Why would the execution of the process handling the response that fires off 
>>> the MongoDB query stop and no exception or anything further be logged?
>>>
>>> Thank you
>>> Brad
>>
>> 

Re: [google-appengine] Re: Google App Engine TCP Connections

[Bradley Barrows]

I thought that the original post did not actually send. My browser quit
right after hitting send so I re wrote it.

I also found no acknowledgement that the original was received so had no
way of verifying if I needed to re type it or not.

Sorry about that.

Thanks
Brad

On Wed, Jun 9, 2021 at 3:01 AM 'Angel (Google Cloud Platform Support)' via
Google App Engine  wrote:

> Hello Brad,
>
> I believe this is a similar, if not the same question that has already
> been answered here [1]. Please let me know if this is the case or if I
> misunderstood your question.
>
> Kind regards.
> __
> [1] -
> https://groups.google.com/g/google-appengine/c/Lj6qaT2lC90/m/TvhGSteRAwAJ
>
> On Tuesday, June 8, 2021 at 9:05:27 AM UTC+2 bradeba...@gmail.com wrote:
>
>> Hi
>>
>> I have a NodeJS App Engine server which is awaiting a MongoDB query
>> which, when reaching a certain size, never returns. There is no exception
>> thrown from App Engine either. It is as if the process is just killed
>> because execution flow and therefore logging from the process making the
>> MongoDB query stops.
>>
>> If this were a request to a HTTP server I could look at the limits and
>> quotas page and see that a maximum of 32MB requests and response size is
>> allowed.
>>
>> I am unable to find any limits or quotas for TCP connections from an App
>> Engine server.
>>
>> We temporarily solved the issue by using a limit or projection to
>> decrease the amount of data returned by the MongoDB query. When less data
>> is sent back to the App Engine server execution continues and the server
>> runs as expected.
>>
>> I was wondering if it was possible if at some point if TCP data usage
>> reaches a limit will the App Engine process be killed? Without any logging?
>> Why would the execution of the process handling the response that fires off
>> the MongoDB query stop and no exception or anything further be logged?
>>
>> Thank you
>> Brad
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/qQSy-QQLZjM/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/7e3c5f5b-cc3b-4460-965f-00a20896feb0n%40googlegroups.com
> 
> .
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAGJGpkrX_X8dfT77JxgvH6jE2G-3efx-pcPObc%2Bgc3cDsTD%3Dkw%40mail.gmail.com.

[google-appengine] Re: Google App Engine TCP Connections

['Angel (Google Cloud Platform Support)' via Google App Engine]

Hello Brad,

I believe this is a similar, if not the same question that has already been 
answered here [1]. Please let me know if this is the case or if I 
misunderstood your question.

Kind regards.
__
[1] 
- https://groups.google.com/g/google-appengine/c/Lj6qaT2lC90/m/TvhGSteRAwAJ

On Tuesday, June 8, 2021 at 9:05:27 AM UTC+2 bradeba...@gmail.com wrote:

> Hi
>
> I have a NodeJS App Engine server which is awaiting a MongoDB query which, 
> when reaching a certain size, never returns. There is no exception thrown 
> from App Engine either. It is as if the process is just killed because 
> execution flow and therefore logging from the process making the MongoDB 
> query stops.
>
> If this were a request to a HTTP server I could look at the limits and 
> quotas page and see that a maximum of 32MB requests and response size is 
> allowed.
>
> I am unable to find any limits or quotas for TCP connections from an App 
> Engine server.
>
> We temporarily solved the issue by using a limit or projection to decrease 
> the amount of data returned by the MongoDB query. When less data is sent 
> back to the App Engine server execution continues and the server runs as 
> expected.
>
> I was wondering if it was possible if at some point if TCP data usage 
> reaches a limit will the App Engine process be killed? Without any logging? 
> Why would the execution of the process handling the response that fires off 
> the MongoDB query stop and no exception or anything further be logged?
>
> Thank you
> Brad

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7e3c5f5b-cc3b-4460-965f-00a20896feb0n%40googlegroups.com.

[google-appengine] Re: Google App Engine: Request was aborted after waiting too long

['wokmou' via Google App Engine]

You might be experiencing latency from reloading instances. This can result 
in loading requests and additional latency as explain here[1].

You can also visit this link to know more about instance life cycle[2].

[1]https://cloud.google.com/appengine/docs/standard/java/how-instances-are-managed
[2]https://cloud.google.com/compute/docs/instances/instance-life-cycle

On Thursday, March 11, 2021 at 11:32:25 AM UTC-5 nem...@cacotec.com wrote:

> I have a small NodeJS application backend running in a standard GAE 
> environment which has no real world load - it only serves my personal 
> requests when I am testing stuff.
>
> So I was clicking through the app last night and this error message popped 
> up:
> ```
> Request was aborted after waiting too long to attempt to service your 
> request.
> ```
>
> These are my logs:
> ```
> 2021-03-11 06:30:06.228 CET GET /l/data 200
> Api call succeeded. Returning data.
>
> 2021-03-11 06:30:52.859 CET
> [start] 2021/03/11 05:30:52.858446 Quitting on terminated signal
>
> 2021-03-11 06:31:25.997 CET OPTIONS /l/orders 500
> Request was aborted after waiting too long to attempt to service your 
> request.
>
> 2021-03-11 06:31:41.132 CET OPTIONS /l/orders 500
> Request was aborted after waiting too long to attempt to service your 
> request.
>
> 2021-03-11 06:31:46.629 CET OPTIONS /l/orders 500
> Request was aborted after waiting too long to attempt to service your 
> request.
>
> 2021-03-11 06:34:44.566 CET GET /l/users 200
> 2021-03-11 06:34:44.736 CET
> [start] 2021/03/11 05:34:44.735240 No entrypoint specified, using default 
> entrypoint: /serve
> [start] 2021/03/11 05:34:44.736120 Starting app
> ```
>
> From the logs I see that my previous instance was stopped prior to the 
> requests that triggered the error and that for the new OPTIONS requests GAE 
> did not even attempt to start an instance. Next start was triggered almost 
> 3 minutes later.
>
> I am still not sure what happened here and would like to understand it 
> because I have some production services running on GAE and this makes me a 
> bit worried.
>
> Thanks in advance!
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ce624825-700f-4bca-88fe-dd7e43b4ede1n%40googlegroups.com.

[google-appengine] Re: Google app engine not distributing requests properly

['wokmou' via Google App Engine]

>From what I understand , your instance is overloaded during spikes. My 
suggestion is to set target_concurrent_requests [1] parameter to limit the 
number of concurrent requests per instance. This will trigger the creation 
of a new instance as soon as the limit is reached.

There is also the max_concurrent_requests [2] use to specify when a new 
instance is started due to concurrent requests.

[1]
https://cloud.google.com/appengine/docs/flexible/python/reference/app-yaml?hl=en#automatic_scaling

[2]https://cloud.google.com/appengine/docs/standard/nodejs/config/appref#scaling_elements


On Friday, February 19, 2021 at 2:06:13 PM UTC-5 
she...@digitalmediasolutions.com.au wrote:

> Hello!
> We have a dockized PHP Nginx application running on google app engine 
> flex. 
> We have automatic scaling and minimum 1 instance is always running. 
> As soon as traffic spikes, users receive 50x gateway errors for some time. 
> The autoscaler works as intended but after checking the logs,  all errors 
> originate from the idle instance due to app engine sending most of the 
> requests received to the first instance overloading it.
>
> Why is app engine not distributing requests evenly? What can we do to make 
> sure the service is available during high traffic bursts?
>
> Thank you for your time!
>
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8414c627-7ffb-4d50-81fb-a910bbe2eb7en%40googlegroups.com.

[google-appengine] Re: Google App Engine with Postgres & Go - Unable to connect to DB

['David (Cloud Platform Support)' via Google App Engine]

Hello,

Please note that Google Groups is reserved for conceptual discussions that 
don’t involve debugging. I understand you may know this already but just 
ran out of options to get additional assistance other than Stack Overflow. 
In order for you to get proper assistance, I would recommend you to check 
out Google Cloud Platform Support.  If 
you happen to be on a free trial, you may be eligible for free support 
(click on free trial) .

Also, please take a look at this working example of gae/go and postgresql 

 
which also uses pgx as it may be helpful. This is part of the Cloud SQL 
quick start so should work almost out of the box (I say almost because you 
still need to add your own cloud sql instance information).

On Friday, February 19, 2021 at 2:06:13 PM UTC-5 brycech...@gmail.com wrote:

> Hello,
>
> I am having a lot of trouble deploying my project to GAE and connecting to 
> Postgres Cloud SQL. I tried Stack Overflow but no such luck.
>
> postgresql - Go API on Google App Engine with Postgres - Stack Overflow 
> 
>  
>
> My Go program MWE can connect to postgres on my local machine but it 
> cannot connect when deployed. I have provided a rather robust description 
> of my Code and errors on SO. I don't know where else to go to ask for help. 
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2c8015fa-d0f7-4b63-a6e7-7d489916fb64n%40googlegroups.com.

[google-appengine] Re: Google App Engine Cost

['Mohammad I (Cloud Platform Support)' via Google App Engine]

Hello,

To get a better understanding on costs for App Engine or for full solution 
with Cloud SQL, Storage & Firebase etc. you can select Google Cloud 
Platform Sales  and select "I want to 
talk to sales" and write down your queries and a Google Cloud Platform 
Sales representative will get back to you. There are also option for chat 
and phone call to talk with Cloud Platform Sales representative. Hope it 
will resolve your concern. 

On Monday, December 7, 2020 at 6:07:20 PM UTC-5 stesc...@gmail.com wrote:

> I am looking into the Google AppEngine for deploying one application. The 
> price calculator is painting a very scary picture, so I decided to ask this 
> here.
>
> My question is from all of you who have deployed their applications onto 
> the AppEngine and have load from moderate to heavy and the instances run 
> 24/7. 
>
> What is your average cost per month :
>
>1. Only AppEngine
>2. Full solution with Cloud SQL, Storage & Firebase etc.
>
> I would highly appreciate your help.
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/240ecfa0-5d83-42d7-a8ed-72bb4b3ce5ffn%40googlegroups.com.

[google-appengine] Re: Google App Engine Mailjet gives 500 error

['yananc' via Google App Engine]

The ‘500’ error and no logs found in the Cloud Console might suggest that 
requests did not even reach your app. Do you use App Engine Standard or 
Flexible environment? Are you able to deploy the app successfully? Do you 
mean that the variables ‘MAILJET_API_KEY’ and ’MAILJET_SECRET_KEY’ work in 
App Engine or on your own server? Please also provide more description on 
the file structure / path of your app. Such information could be helpful to 
troubleshoot the issue. Thank you.

On Sunday, October 25, 2020 at 6:19:13 PM UTC-4 jukka.ha...@gmail.com wrote:

>
> When trying to use mailjet with php 7 Google App engine, 
> the request to that file gives 500-error and I cannot see any details of 
> the error anywhere in developer console!
>
> - runtime: php72
> -mailjet/mailjet-apiv3-php": "^1.5"
> -This file works 100% on my own server.
>
> - I have narrowed the cause of error to the line
> $mj = new \Mailjet\Client(MAILJET_API_KEY, MAILJET_SECRET_KEY, 
> true,['version' => 'v3.1']);
> but it's from the docs and nothing weird about it, and these api keys of 
> course also works.
>
> Put perhaps the path or something is different in my gae than in my apache 
> ?
> the row that i have is use \Mailjet\Resources; and it's working in my own 
> server ok.
>
>
> Do I need some custom php.ini settings to make this work ? 
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/12bf58d0-7d62-4721-9072-08ddd77f078bn%40googlegroups.com.

[google-appengine] Re: Google App Engine - Read JSON file from application code

['Sergio Llopis' via Google App Engine]

Hello, 

I understand that you are trying to read a JSON file from a Go application 
that is hosted on App Engine.

The error message [1] that you are seeing can be due mainly to two reasons:

1 - The file does not exist in the filesystem.
2 - The file exists in the filesystem but the given path is wrong.

Please note that the App Engine documentation [2] states that static files 
are uploaded and handled separately from application files. 

This means that if you have a file which you want to read from your Go 
code, the file must not match any static file pattern and cannot be in a 
folder defined as a static directory, or else the file will be considered 
to be a static file and will not be deployed along with your application 
code. 

I can see that the Stackoverflow question [3] has already an answer that 
was upvoted a by a community user. Please let me know if the answer 
correctly addresses your issue and whether it helps you. 

Thank you!

[1]: error loading config file: open go-config.json: no such file or 
directory
[2]: 
https://cloud.google.com/appengine/docs/standard/go/config/appref#handlers_element
[3]: 
https://stackoverflow.com/questions/64455222/google-app-engine-read-json-file-from-application-code
On Wednesday, October 21, 2020 at 4:28:39 AM UTC+2 
law...@euterpesolutions.com wrote:

> Can anyone help me with this problem?
>
>
> https://stackoverflow.com/questions/64455222/google-app-engine-read-json-file-from-application-code

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/398b01ac-cab7-40e2-b112-f396472d6a5en%40googlegroups.com.

[google-appengine] Re: Google App engine 301 redirect or Move project to another

['Mohammad I (Cloud Platform Support)' via Google App Engine]

I have come across this StackOverflow thread 
 which appears to be 
discussing your issue. In addition to that another workaround can be to 
deploy a version of the app that just serves the HTTP redirect and set it 
to be the default version. 

However it is not clear to me what you have meant by some search engines 
not seeing the app that you have created using Python script. 

If still the issue is not resolved or If you have any technical queries or 
think your issue is related to code, you can post at the Stack Overflow 
 or Server Fault  and 
a community of developers will assist you.

In case there are any technical issues or you would like to request any 
feature you can report it at the Public Issues by selecting the right 
component here 
. If 
you need to select any project specific information please select the 
private component of the Public Issue so that the information is not 
visible to the public. After that a Google Cloud Platform support agent 
would assist you. 

Please also note that Google Groups forum is meant for general discussion 
of the platform, not specific technical issues. You can find more info 
about Community Support Overview on Google Groups here 
.


On Monday, October 12, 2020 at 9:53:26 AM UTC-4 n.vikt...@gmail.com wrote:

> Hi everyone.
>
> Right now we have an issue with move from one domain to another.
> We want to configure 301 redirect from domain test.appspot.com to another 
> domain test2.appspot.com
>
> We created an app using Python script but some search engine systems are 
> not see it.
>
> Maybe there is some possibility at the settings level to indicate the 
> relocation of the project?
>
> Best regards, Nick.
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e4b09bc8-7671-419e-bfae-e86c8975ab49n%40googlegroups.com.

[google-appengine] Re: Google App Engine: versioning with custom sub domains

['Alex Fox' via Google App Engine]

Hey Alexander,

This sounds like the functionality I want. Perhaps I need to experiment 
with a wild card certificate and avoid using the sub domains. 

Thanks,
Alex

On Tuesday, July 14, 2020 at 4:04:38 PM UTC+1 a.not...@gmail.com wrote:

> Alex,
>
> We are doing just what you describe, although we do it under the naked 
> domain.
>
> we have app.io pointing to appengine, which has a wildcard certificate 
> mapped.
> My appengine settings for custom domain are like this:
>
> custom domain name | cert | record type | data | alias
> *.app.io  | wildcard-certificate |  cname |  ghs.googlehosted.com. |   *
> app.io  | wildcard-certificate |  A |  xx.xx.xx.xx |  (none)
>
>
> all requests for app.io go to the default version.  We also have a 
> release candidate version deployed, named 'rc'
> Without any configuring all request for rc.app.io go automagically to the 
> rc version.
>
> This only works when you have the wildcard certifcate in place.  Just 
> adding custom domain mappings for each version will not work.
>
>
>
> Alexander
>
> On Friday, 10 July 2020 20:20:15 UTC+2, Alex Fox wrote:
>>
>> I'm trying to setup GAE with a custom sub domain and a specific version 
>> url.
>>
>> For example I have an app running with the following setup
>> *VERSION_ID: 1234*
>> *SERVICE_ID: my-app*
>> *PROJECT_ID: my-project*
>>
>> The provided url *https://1234-dot-my-app-dot-my-project.ew.r.appspot.com 
>> * works fine. 
>> But I can't get to work with my custom domain + sub domain. Googles 
>> documentation states the following urls are the same:
>>
>> *https://VERSION_ID-dot-default-dot-PROJECT_ID.REGION_ID.r.appspot.com 
>> *
>> *https://VERSION_ID.CUSTOM_DOMAIN *
>>
>> But when visiting *1234.api.mycustomdomain.com 
>> * it does not work. However 
>> *api.mycustomdomain.com 
>> * works, pointing to the latest running 
>> version of *my-app*
>>
>> What am I missing?
>> Thanks.
>>  
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9f7011b7-f5bf-45e6-b98f-13e246d9561fn%40googlegroups.com.

[google-appengine] Re: Google App Engine: versioning with custom sub domains

[alexander noteboom]

Alex,

We are doing just what you describe, although we do it under the naked 
domain.

we have app.io pointing to appengine, which has a wildcard certificate 
mapped.
My appengine settings for custom domain are like this:

custom domain name | cert | record type | data | alias
*.app.io  | wildcard-certificate |  cname |  ghs.googlehosted.com. |   *
app.io  | wildcard-certificate |  A |  xx.xx.xx.xx |  (none)


all requests for app.io go to the default version.  We also have a release 
candidate version deployed, named 'rc'
Without any configuring all request for rc.app.io go automagically to the 
rc version.

This only works when you have the wildcard certifcate in place.  Just 
adding custom domain mappings for each version will not work.



Alexander

On Friday, 10 July 2020 20:20:15 UTC+2, Alex Fox wrote:
>
> I'm trying to setup GAE with a custom sub domain and a specific version 
> url.
>
> For example I have an app running with the following setup
> *VERSION_ID: 1234*
> *SERVICE_ID: my-app*
> *PROJECT_ID: my-project*
>
> The provided url *https://1234-dot-my-app-dot-my-project.ew.r.appspot.com 
> * works fine. 
> But I can't get to work with my custom domain + sub domain. Googles 
> documentation states the following urls are the same:
>
> *https://VERSION_ID-dot-default-dot-PROJECT_ID.REGION_ID.r.appspot.com 
> *
> *https://VERSION_ID.CUSTOM_DOMAIN *
>
> But when visiting *1234.api.mycustomdomain.com 
> * it does not work. However 
> *api.mycustomdomain.com 
> * works, pointing to the latest running 
> version of *my-app*
>
> What am I missing?
> Thanks.
>  
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f572053e-e3f9-4466-b7c3-5c57c737ade2o%40googlegroups.com.

[google-appengine] Re: Google App Engine: versioning with custom sub domains

['Olu' via Google App Engine]

Hello, Alex

While I think I understand your request, I require a clarification. You 
mentioned that the Google documentation states using the Version ID with 
your Custom Domain is the same as using your Version ID with the 
appspot.com domain. Do you have the link to this Google documentation you 
refer?

I see a similar request as this posted on Stackoverflow[1], which I think 
you should check out. The answer on that post indicates that using the 
Version ID with the Custom Domain may not be possible as you cannot select 
a certain version of a service in the custom domain settings screen.

Please provide the link you refer for clarification. 

[1]https://stackoverflow.com/questions/55272201/google-app-engine-custom-subdomain-mapping-for-a-specific-version

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/bd0b4345-4486-49b1-9252-81b506275bd6o%40googlegroups.com.

[google-appengine] Re: Google App Engine Java 8 Lifetime (LTS)

['Elliott (Cloud Platform Support)' via Google App Engine]

Hello Carl,

Thank you for your question. I cannot find public documentation that 
definitely answers your question but you may use this general link 
 for product news, which is updated 
regularly.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/efc1a8d6-55ab-4617-afcd-291acfc8bac1%40googlegroups.com.

[google-appengine] Re: Google app engine issue when deploying it

['Olu' via Google App Engine]

There are a number of reasons this type of error may be obtained. As the 
error message indicates, it seems there is a missing or insufficient 
permission and this may be due to a number of reasons. For example, on this 
Stackoverflow link[1], the issue was caused by missing App Engine default 
service account. The issue also may be caused by the App Engine service 
account missing the appropriate role or permission required to read and 
write to Datastore and Firestore databases in your Google Cloud project.

For better troubleshooting of the issue, which may involve reviewing 
configurations on your Project, I recommend you contact the GCP Support 
Engineers[2] or if you think this issue is a bug, then please open an issue 
using this link[3].

[1]https://stackoverflow.com/questions/59210059/datastoreexception-missing-or-insufficient-permissions-on-superseded-cloud-da#answer-59216570
[2]https://cloud.google.com/support-hub
[3]https://developers.google.com/issue-tracker/#public_users

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c30e2859-6268-4a35-9edf-ee2093479682%40googlegroups.com.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Olu' via Google App Engine]

I understand your concern about the Deployment time. These are on-going 
efforts and changes that sadly have no ETA at this time as the team is 
constantly looking into ways to get better deployment time for all App 
Engine environments. There are similar reports on these issue links[1][2] 
that the Internal GCLB engineers are aware of. I recommend you read the 
details shared and track the issue links for regular updates, particularly 
when the fixes are completed. At this time, however, recommendations 
offered on this thread are still what are viable. 

[1]https://issuetracker.google.com/67840
[2]https://issuetracker.google.com/118605189



On Wednesday, April 22, 2020 at 8:12:18 AM UTC-4, Magnus Markling wrote:
>
> Hey Nick!
>
> How are these devoted efforts coming along? I just started a brand new GAE 
> project with a simple Node application. Deployment takes 8-10 mins, the 
> major part of which is still spent waiting for "Updating service". I'm not 
> particularly impressed.
>
> Cheers,
> Magnus
>
> Den torsdag 6 april 2017 kl. 01:28:11 UTC+2 skrev Nick (Cloud Platform 
> Support):
>>
>> We're devoting a lot of energy to decreasing GCLB configuration push 
>> times, so rest assured that our efforts in that direction should pay off 
>> going forward.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Tuesday, March 21, 2017 at 6:41:52 PM UTC-4, Stanislas Marion wrote:
>>>
>>> Great, thank you so much for your help, I'll be very interested in the 
>>> details you'll get from your investigation.
>>>
>>> On Tue, Mar 21, 2017 at 9:22 PM 'Nick (Cloud Platform Support)' via 
>>> Google App Engine  wrote:
>>>
 Hey Stanislas,

 The exact explanation speculated on in my last post shouldn't be taken 
 as any description of what's necessarily going on, however it was an 
 estimate of what might be happening based on the logs observed. I'm 
 corresponding with experts in this area to get a more clear answer at the 
 moment. 

 You could look into deploying on Container Engine 
 , which would mean that 
 the front-end management done by the App Engine Flexible Environment 
 infrastructure wouldn't be happening, rather it would be the 
 responsibility 
 of the resources you deploy on Container Engine (a managed service based 
 pretty transparently on Kubernetes ). Surely 
 deploying new container images to your pool of instances in a cluster (or 
 multiple clusters) would be quite fast, since the master sitting in front 
 of your clusters and the nodes in the cluster are not as massively 
 distributed as the App Engine Flexible Environment serving infrastructure, 
 hence updating their routing rules would be relatively fast. This is 
 something to look into and experiment with if you don't want to wait on 
 the 
 more detailed word from experts, but don't rush to that if you're not all 
 that curious.

 I'll get back to this thread with more details when they're forthcoming 
 in our investigation.


 Cheers,

 Nick
 Cloud Platform Community Support 

 On Tuesday, March 21, 2017 at 3:50:34 PM UTC-4, Stanislas Marion wrote:
>
> Hi Nick,
> Thanks a lot for the lengthy explanation. 
> In this light, is there anything I can do to speed things up? Like for 
> instance take care of the load-balancer myself? Indeed I don't see a 
> reason 
> why it should need to be changed. Could I do this with GAE or would I 
> have 
> to move to G Container/Compute E?
> Cheers,
>
> On Tue, Mar 21, 2017 at 8:42 PM 'Nick (Cloud Platform Support)' via 
> Google App Engine  wrote:
>
>> Hey Stanislas,
>>
>> My initial hunch was that the issue was the deployment of other 
>> resources necessary to support the containers running. My analysis of 
>> deployment-related logs appears to confirm this:
>>
>> I created a simple NodeJS app using your dockerfile and default.yaml. 
>> I then pushed the docker image to gcr.io and ran "gcloud app deploy 
>> --image-url ..."
>>
>> After about 1 minute of waiting, all resources associated with the 
>> deployment had apparently completed, but the command had not returned 
>> yet:
>>
>> ```
>> $ gcloud deployment-manager resources list --deployment 
>> aef-default-20170321t185300
>>
>> NAME   TYPE   
>>   STATE  ERRORS  INTENT
>> aef-default-20170321t185300-00 
>> compute.beta.regionInstanceGroupManager  COMPLETED  []
>> aef-default-20170321t185300-00ahs  compute.v1.httpsHealthCheck   
>>COMPLETED  []
>> aef-default-20170321t185300-00it   compute.v1.instanceTemplate   
>>COMPLETED  []
>> aef-default-20170321t185300-bs 

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Magnus Markling]

Hey Nick!

How are these devoted efforts coming along? I just started a brand new GAE 
project with a simple Node application. Deployment takes 8-10 mins, the 
major part of which is still spent waiting for "Updating service". I'm not 
particularly impressed.

Cheers,
Magnus

Den torsdag 6 april 2017 kl. 01:28:11 UTC+2 skrev Nick (Cloud Platform 
Support):
>
> We're devoting a lot of energy to decreasing GCLB configuration push 
> times, so rest assured that our efforts in that direction should pay off 
> going forward.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, March 21, 2017 at 6:41:52 PM UTC-4, Stanislas Marion wrote:
>>
>> Great, thank you so much for your help, I'll be very interested in the 
>> details you'll get from your investigation.
>>
>> On Tue, Mar 21, 2017 at 9:22 PM 'Nick (Cloud Platform Support)' via 
>> Google App Engine > wrote:
>>
>>> Hey Stanislas,
>>>
>>> The exact explanation speculated on in my last post shouldn't be taken 
>>> as any description of what's necessarily going on, however it was an 
>>> estimate of what might be happening based on the logs observed. I'm 
>>> corresponding with experts in this area to get a more clear answer at the 
>>> moment. 
>>>
>>> You could look into deploying on Container Engine 
>>> , which would mean that the 
>>> front-end management done by the App Engine Flexible Environment 
>>> infrastructure wouldn't be happening, rather it would be the responsibility 
>>> of the resources you deploy on Container Engine (a managed service based 
>>> pretty transparently on Kubernetes ). Surely 
>>> deploying new container images to your pool of instances in a cluster (or 
>>> multiple clusters) would be quite fast, since the master sitting in front 
>>> of your clusters and the nodes in the cluster are not as massively 
>>> distributed as the App Engine Flexible Environment serving infrastructure, 
>>> hence updating their routing rules would be relatively fast. This is 
>>> something to look into and experiment with if you don't want to wait on the 
>>> more detailed word from experts, but don't rush to that if you're not all 
>>> that curious.
>>>
>>> I'll get back to this thread with more details when they're forthcoming 
>>> in our investigation.
>>>
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support 
>>>
>>> On Tuesday, March 21, 2017 at 3:50:34 PM UTC-4, Stanislas Marion wrote:

 Hi Nick,
 Thanks a lot for the lengthy explanation. 
 In this light, is there anything I can do to speed things up? Like for 
 instance take care of the load-balancer myself? Indeed I don't see a 
 reason 
 why it should need to be changed. Could I do this with GAE or would I have 
 to move to G Container/Compute E?
 Cheers,

 On Tue, Mar 21, 2017 at 8:42 PM 'Nick (Cloud Platform Support)' via 
 Google App Engine > wrote:

> Hey Stanislas,
>
> My initial hunch was that the issue was the deployment of other 
> resources necessary to support the containers running. My analysis of 
> deployment-related logs appears to confirm this:
>
> I created a simple NodeJS app using your dockerfile and default.yaml. 
> I then pushed the docker image to gcr.io and ran "gcloud app deploy 
> --image-url ..."
>
> After about 1 minute of waiting, all resources associated with the 
> deployment had apparently completed, but the command had not returned yet:
>
> ```
> $ gcloud deployment-manager resources list --deployment 
> aef-default-20170321t185300
>
> NAME   TYPE   
>   STATE  ERRORS  INTENT
> aef-default-20170321t185300-00 
> compute.beta.regionInstanceGroupManager  COMPLETED  []
> aef-default-20170321t185300-00ahs  compute.v1.httpsHealthCheck 
>  COMPLETED  []
> aef-default-20170321t185300-00it   compute.v1.instanceTemplate 
>  COMPLETED  []
> aef-default-20170321t185300-bs compute.v1.backendService   
>  COMPLETED  []
> aef-default-20170321t185300-hcfw   compute.v1.firewall 
>  COMPLETED  []
> aef-default-20170321t185300-hcscompute.v1.httpsHealthCheck 
>  COMPLETED  []
> ```
>
> At around the same time that the last of the above completed, I see 
> the following in the Console logs when selecting the "Deployment" logs 
> source:
>
> ```
> {
>  protoPayload: {…}
>  insertId: "54B422B11D921.AE9070D.A80D9821"
>  resource: {
>   type: "deployment"
>   labels: {
>project_id: ""
>name: "-gclb"
>   }
>  }
>  timestamp: "2017-03-21T18:54:05.999Z"
>  severity: "ERROR"
>  logName: "projects//logs/cloudaudit.googleapis.com
> %2Factivity"
> }
> ```
>
> I haven't 

[google-appengine] Re: Google App engine deploy python project 502 bad gateway error

[Aaron Butler]

you're my hero!

Following the current guide cloud sql works via cloud_sql_proxy running the 
django app local.
Ideally this would be enough to feel like you could deply. 
 
Cloud deployment instructions appear to be missing something. 

On Thursday, February 6, 2020 at 3:58:51 PM UTC+11, Mohammad I (Cloud 
Platform Support) wrote:
>
> Hello Aaron, 
>
> Thank you for your message. I have created an internal issue with App 
> Engine Engineering team to update the document 
>  and 
> notified them about your concern. 
>
> On Wednesday, February 5, 2020 at 8:41:00 AM UTC-5, Aaron Butler wrote:
>>
>> Hi Jordan, 
>>
>> I would recommend that the quickstart is revisited + updated as the 502 
>> is a common issue caused by your user guide.
>> In fact there is even medium articles 
>> https://medium.com/@BennettGarner/deploying-a-django-application-to-google-app-engine-f9c91a30bd35
>>  where 
>> people have attempted to use your product via the guide and also arrive at 
>> the 502.
>> If a large facet of your customer base are hitting this dead end while 
>> trying to use your product following your documentation then the fault lays 
>> with the product not the developer. 
>>
>>
>> On Tuesday, October 24, 2017 at 4:39:51 AM UTC+11, Jordan (Cloud Platform 
>> Support) wrote:
>>>
>>> Google Groups is meant for general product discussions and not for 
>>> technical support. The correct place 
>>>  to seek technical 
>>> support is indeed Stack Overflow as you have already done 
>>> 
>>> . 
>>>
>>> Note that '502 Bad Gateway' is returned when your application does not 
>>> respond to nginx on port 8080. It is recommended to follow the Quickstart 
>>> tutorial 
>>>  to 
>>> setup your application handlers correctly in order to properly accept and 
>>> respond to incoming requests. 
>>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5953dd07-9ebb-49d9-b4b8-acd9b7c54fa2%40googlegroups.com.

[google-appengine] Re: Google App engine deploy python project 502 bad gateway error

['Mohammad I (Cloud Platform Support)' via Google App Engine]

Hello Aaron, 

Thank you for your message. I have created an internal issue with App 
Engine Engineering team to update the document 
 and 
notified them about your concern. 

On Wednesday, February 5, 2020 at 8:41:00 AM UTC-5, Aaron Butler wrote:
>
> Hi Jordan, 
>
> I would recommend that the quickstart is revisited + updated as the 502 is 
> a common issue caused by your user guide.
> In fact there is even medium articles 
> https://medium.com/@BennettGarner/deploying-a-django-application-to-google-app-engine-f9c91a30bd35
>  where 
> people have attempted to use your product via the guide and also arrive at 
> the 502.
> If a large facet of your customer base are hitting this dead end while 
> trying to use your product following your documentation then the fault lays 
> with the product not the developer. 
>
>
> On Tuesday, October 24, 2017 at 4:39:51 AM UTC+11, Jordan (Cloud Platform 
> Support) wrote:
>>
>> Google Groups is meant for general product discussions and not for 
>> technical support. The correct place 
>>  to seek technical 
>> support is indeed Stack Overflow as you have already done 
>> 
>> . 
>>
>> Note that '502 Bad Gateway' is returned when your application does not 
>> respond to nginx on port 8080. It is recommended to follow the Quickstart 
>> tutorial 
>>  to 
>> setup your application handlers correctly in order to properly accept and 
>> respond to incoming requests. 
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9a3773fd-0f80-4c96-802e-96945b7bc58d%40googlegroups.com.

[google-appengine] Re: Google App engine deploy python project 502 bad gateway error

[Aaron Butler]

Hi Jordan, 

I would recommend that the quickstart is revisited + updated as the 502 is 
a common issue caused by your user guide.
In fact there is even medium articles 
https://medium.com/@BennettGarner/deploying-a-django-application-to-google-app-engine-f9c91a30bd35
 where 
people have attempted to use your product via the guide and also arrive at 
the 502.
If a large facet of your customer base are hitting this dead end while 
trying to use your product following your documentation then the fault lays 
with the product not the developer. 


On Tuesday, October 24, 2017 at 4:39:51 AM UTC+11, Jordan (Cloud Platform 
Support) wrote:
>
> Google Groups is meant for general product discussions and not for 
> technical support. The correct place 
>  to seek technical 
> support is indeed Stack Overflow as you have already done 
> 
> . 
>
> Note that '502 Bad Gateway' is returned when your application does not 
> respond to nginx on port 8080. It is recommended to follow the Quickstart 
> tutorial 
>  to 
> setup your application handlers correctly in order to properly accept and 
> respond to incoming requests. 
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/845bfa55-3b15-4071-a1a9-065344c7cae2%40googlegroups.com.

[google-appengine] Re: google app engine and big file generating

['Aref Amiri (Cloud Platform Support)' via Google App Engine]

You may want to consider using Cloud Tasks 
, as it is mainly used 
to manage the execution of a large number of distributed tasks. It allows 
you to execute tasks asynchronously and control those requests to better 
manage the load on your services. 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b6291b53-8c9c-48ca-a605-1ecdae1c4fd7%40googlegroups.com.

[google-appengine] Re: Google App Engine Search stopped working

['Elliott (Cloud Platform Support)' via Google App Engine]

Hello Liu,

Please use this link here 
 to 
open an issue with Google Issue Tracker for App Engine. You will need a 
Google Account to access it.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c392c0c6-2d43-4fd7-844b-611809285cfa%40googlegroups.com.

[google-appengine] Re: Google App Engine Search stopped working

[Liu Adoo]

I tried to create issue, but it says "You do not have permission to create 
issues in this component.", I chose Public Trackers.

On Wednesday, November 20, 2019 at 2:31:51 AM UTC+8, George (Cloud Platform 
Support) wrote:
>
> Hello Liu, 
>
> The error may have various origins. You should try including the app 
> engine dependency in your pom.xml. 
>
> This discussion group is oriented more towards general opinions, trends, 
> and issues of general nature touching App Engine. For coding in Java, and 
> software architecture, as well as registering dependencies, you may be 
> better served in dedicated forums such as stackoverflow, where experienced 
> programmers are within reach and ready to help. If you think this a Cloud 
> Platform related problem, you are encouraged to open a private issue in the 
> Public Issue Tracker, where private information, such as project names, can 
> be securely exchanged. 
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/90cd1c59-ff5a-4622-9ed0-18cbd0d55d81%40googlegroups.com.

[google-appengine] Re: Google App Engine Search stopped working

['George (Cloud Platform Support)' via Google App Engine]

Hello Liu, 

The error may have various origins. You should try including the app engine 
dependency in your pom.xml. 

This discussion group is oriented more towards general opinions, trends, 
and issues of general nature touching App Engine. For coding in Java, and 
software architecture, as well as registering dependencies, you may be 
better served in dedicated forums such as stackoverflow, where experienced 
programmers are within reach and ready to help. If you think this a Cloud 
Platform related problem, you are encouraged to open a private issue in the 
Public Issue Tracker, where private information, such as project names, can 
be securely exchanged. 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b1c4577e-d202-4bf9-a349-4d4fc060ce43%40googlegroups.com.

[google-appengine] Re: google app engine deploy error from gitlab runner

['George (Cloud Platform Support)' via Google App Engine]

Hello Bilal, 

Local development environment is different from App Engine runtime after 
deployment, in particular here your local environment is able to run the 
binary: GitLab Runner is designed to run on the GNU/Linux, macOS, and 
Windows operating systems. Other operating systems will probably work as 
long as you can compile a Go binary on them. In other words, you local 
environment offers the advantage of running GitLab Runner, which explains 
why your deployment on the local server runs as expected. 

As an alternative to GitLab Runner, you may consider Cloud Source 
Repositories . 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6c6fb311-8ffb-4cc0-8e46-0f0a47f5bd12%40googlegroups.com.

[google-appengine] Re: Google App Engine Instance is abruptly shutting down on Standard Environment

[vidhi thakrar]

Thank you George for the response. 

In our case, There is a single endpoint which reads a large file from 
amazon s3 line by line and then ingests a batch of 50 lines as 50 documents 
on cloud firestore. It roughly takes around 1.5 hours to insert all the 
data from a file to cloud firestore. Given that instance uptime is not 
guaranteed, is compute engine a good solution to perform long running task? 
Or is there any other option you can recommend?

On the flex environment, we tried to first download the whole file on a 
disk and then start reading line by line from it which has worked for us 
and not observed abrupt termination. But wanted to know an opinion around 
what should be the best option to perform long running task on google cloud 
platform.


On Friday, August 9, 2019 at 11:39:00 PM UTC+5:30, George (Cloud Platform 
Support) wrote:
>
> Instance re-starting is normal in the present case, and your application 
> should take this into consideration. Hardware and software failures that 
> cause early termination or frequent restarts can occur without prior 
> warning and can take considerable time to resolve; thus, you should 
> construct your application in a way that tolerates these failures. You may 
> find related detail on the "How Instances are Managed" documentation page 
> .
>   
> Some good strategies for avoiding downtime are listed on that page. You may 
> also consider changing your app.yaml with line basic_scaling: instances: 2, 
> or more than 1. 
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/76d363ed-91cd-40d8-a54d-56c33e6899df%40googlegroups.com.

[google-appengine] Re: Google App Engine Instance is abruptly shutting down on Standard Environment

['George (Cloud Platform Support)' via Google App Engine]

Instance re-starting is normal in the present case, and your application 
should take this into consideration. Hardware and software failures that 
cause early termination or frequent restarts can occur without prior 
warning and can take considerable time to resolve; thus, you should 
construct your application in a way that tolerates these failures. You may 
find related detail on the "How Instances are Managed" documentation page 
.
  
Some good strategies for avoiding downtime are listed on that page. You may 
also consider changing your app.yaml with line basic_scaling: instances: 2, 
or more than 1. 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3dbf2e3e-9706-464b-8dac-8a356a2600a7%40googlegroups.com.

[google-appengine] Re: Google App Engine Flex Environment -- WebSocket server error

['Harmit Rishi (Cloud Platform Support)' via Google App Engine]

Hi, 

Thank you for using Google Groups!

It seems like you have reached out about this issue on our Issue Tracker 
thread here  
for this issue as well. As suggested by the support agent on that thread 
, you may file 
a issue via the support-hub here  with 
additional details of this issue. 

Cheers

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b07864e7-bd70-42f1-9388-91c4bdce634d%40googlegroups.com.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Andreas Virkus]

I feel it necessary to echo this. Zeit, Heroku, AWS, [you-name-it] all 
deliver these micro-updates under a minute.
In todays world of rapid development/delivery/iteration, it's odd to see a 
company of Google's magnitude be contempt with being 10+ times slower than 
their competition.

I guess GAE at its current state is either still immature or simply meant 
to serve people with different needs. Hope GKE proves to be a better 
experience.

On Friday, January 18, 2019 at 10:15:29 PM UTC+2, Karolis Krulis wrote:
>
> That's not really a solution. If I deploy the same exact file to AWS it 
> takes ~15s on a slow network. I spent 10 minutes deploying on google. 
>
> On Monday, October 3, 2016 at 4:39:50 PM UTC-4, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Kevin,
>>
>> The speed of deployment can be changed by limiting the size of the 
>> uploaded app, limiting the complexity of the build necessary in the 
>> Dockerfile, if present, and by ensuring a fast and reliable internet 
>> connection. Other than these variables, it's hard to comment on what 
>> specifically might be making deployment exhibit the timing that it does on 
>> your system. 
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0b64b850-45c0-43cc-a482-52689579b650%40googlegroups.com.

[google-appengine] Re: Google App Engine SSL Auto-Renewal

[diogoalmeida via Google App Engine]

Hello James.

Note that the Google Groups thread is not the best channel to post this 
type of issues [1]. For technical questions you can use StackOverflow. 
However, it looks like to resolve this issue you will need to file a case 
with the GCP support team [2] (Free trial [3]).

[1] https://cloud.google.com/support/docs/community
[2] https://cloud.google.com/support/
[3] https://support.google.com/cloud/contact/free_trial_support


On Wednesday, April 24, 2019 at 10:15:11 PM UTC-4, James Terry wrote:
>
> Hi all,
>
> I'm am trying to set up SSL Renewal on my domain name in Google App 
> Engine. In Settings > Custom Domains, I select my domain and then click on 
> Enable Managed Security. It prompts me with the following: 
>
> domain.com is currently using certificate '$(certificateName)'. This 
>> certificate will continue to be used until the Google-managed certificate 
>> is activated. Are you sure you want to proceed?
>
>
> I click ok and then get prompted with "Failed to activate certificate". 
> Naturally, I tried to remove the previous SSL certificate but even after 
> selecting it under the SSL certificates tab, the delete button is greyed 
> out. When I hover over it, it says that, "To delete a certificate, it must 
> not be in use by any domain across any project". I'm guessing that this 
> means I have to stop the domain before I uninstall the certificate. I then 
> disabled the domain and tried again and still, I got the same message. I've 
> tried searching how to remove a certificate from being used but I get no 
> good results.
>
> Not stopping there, I tried working with the cloud console. According to 
> https://cloud.google.com/appengine/docs/standard/python/securing-custom-domains-with-ssl,
>  
> I tried the following command, 
>
> gcloud app domain-mappings update DOMAIN --certificate-management='AUTOMATIC'
>
>
> This instead gave me an error saying the operation failed. This is the 
> error.
>
> ERROR: (gcloud.app.domain-mappings.update) Error Response: [7] Caller is 
> not authorized to administer the domain 'www.domain.com'. If you own '
> www.domain.com', you can ob
> tain authorization by verifying ownership of the domain, or any of its 
> parent domains, via the Webmaster Central portal: 
> https://www.google.com/webmasters/verification/verification?d
> omain=www.domain.com. We reccomend verifying ownership of the largest 
> scope you wish to use with subdomains (eg. verify 'example.com' if you 
> wish to map 'subdomain.example.com'
> ).
>
> Then, I click on the link provided which sent me to a page explaining 
> domain verification. At the top of the page however, it says I'm already 
> the verified owner of my domain. Now I'm confused as there doesn't seem to 
> be any other logical progression to solving this problem. Could anyone help 
> me out with this?
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/4df456f2-5066-4ee6-b512-4d633a455ac0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine High Availbility

[diogoalmeida via Google App Engine]

Hello.

App Engine is regional [1] 
 and the app should be 
available across all zones within the region you choose. However, it is not 
possible to change the app region after you set it.

App Engine does not have the same high availability mechanism present in 
Cloud SQL, so, you would need to build your application with that in mind. 
That said, I recommend that you review the following topics which will help 
you decide the best approach to deploying an application on the Google 
Cloud Platform.

-- Take into account the App Engine SLA, especially the downtime period [2] 
. If the SLA is still not 
appropriate for your use case, it might be necessary to change the strategy 
and use Compute Engine instead. That would allow you to create cross-region 
load balancers and forward the traffic to instances in two different 
regions in case of a region downtime [3] 

[4] 
.

-- As per this document [5], instead of using microservices, where all 
services are deployed within the same application in one single region, you 
could deploy multiple services in different App Engine project. However, 
check the benefits and drawbacks of this strategy here [5] 

.

-- I also recommend to review how instances are managed on App Engine 
Standard [6] 

 
and Flexible environment [7] 

.




On Wednesday, March 13, 2019 at 4:19:01 PM UTC-4, Eduardo Moreira wrote:
>
>
> Hello Everyone
>
> I have a question about High Availability within Google App Engine. It is 
> possible with VM Instances to have High-Availability in case whatever 
> happens in the region where you have your instance, but this does not seem 
> to be the case with Google App Engine, do you guys know the infraestructure 
> behind GAE? How safe it is against eventual unexpected issues?
>
> I know it can be done in SQL which is the database for the app, but I am 
> interested on the actual GAE app itself.
>
> Thank you
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/67e30220-0b7e-4f93-b500-f5dcf6b07b32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine not show domains registered

['Harmit Rishi (Cloud Platform Support)' via Google App Engine]

Hello, 

Thank you for using Google groups. I understand you would like to map a 
custom domain to your App-Engine app. 

Based on the documentation provided by Google for mapping custom domains, I 
believe you have to verify if you are the owner of the domain before you 
can map it. This is also mentioned by step 2 here 
[1],
 
where it is advised that only verified domains will be displayed. 

It would be my recommendation to try mapping your domain once more by 
following the guide provided here 
.
 


Hope it helps!


[1]Mapping Custom Domains: 
https://cloud.google.com/appengine/docs/standard/python/mapping-custom-domains 

 
On Friday, February 8, 2019 at 8:49:35 PM UTC-5, Victor Viana wrote:
>
> Hi Folks,
>
> I'm having trouble trying to map a custom domain to my App Engine 
> application, I'm registering for example some properties in the Webmaster 
> Central so that it appears to me on the App Engine add-on domain screen, 
> but it's not showing up. 
> Anyone have any idea what that might be?
>
> Thank you for your help.
>
> *Google App Engine*
>
> [image: Screen Shot 2019-02-08 at 16.43.11.png]
>
>
> *Google Central Webmaster*
>
> [image: Screen Shot 2019-02-08 at 16.45.39.png]
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/e6c613f1-887c-49b9-bf14-fe0f74ce18aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Matt Haff]

Thanks Mohammad, I have created an issue there as well.

On Thursday, January 24, 2019 at 12:01:28 AM UTC-5, Mohammad I (Cloud 
Platform Support) wrote:
>
> Hello Matt, 
>
>
> As the issue is related to user’s deployment failure sometimes which is an 
> indicator that this issue shouldn't be reported on Google Groups as this 
> forum is meant for general discussion of the platform, not specific 
> technical issues. 
>
>
> What's needed for anybody who would want to report a technical issue, is 
> to use the issue tracker 
>  rather than google 
> groups so that we can properly involve the engineering team and further 
> investigate this deployment issue in the public issue tracker. If it is 
> required to share any private or project specific information please choose 
> the “Private” component so that the information are not visible to the 
> public. 
>
>
> I wish you the best of luck in proceeding to either open a proper issue 
> report in the public issue tracker. 
>
>
> I would also encourage you to share the public issue tracker link in this 
> thread if you keep that public so that other users can go to the link for 
> resolution or they can see the updates on the issue. 
>
>
>
> On Friday, January 18, 2019 at 3:25:29 PM UTC-5, Matt Haff wrote:
>>
>> I'm having the same issue, I posted a separate question here per Nick's 
>> request - 
>> https://groups.google.com/forum/?utm_medium=email_source=footer#!topic/google-appengine/NJMzqz5JqZQ
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/54fee8ad-c95e-433c-84a0-bfba1a15364d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Mohammad I (Cloud Platform Support)' via Google App Engine]

Hello Matt, 


As the issue is related to user’s deployment failure sometimes which is an 
indicator that this issue shouldn't be reported on Google Groups as this 
forum is meant for general discussion of the platform, not specific 
technical issues. 


What's needed for anybody who would want to report a technical issue, is to 
use the issue tracker  
rather than google groups so that we can properly involve the engineering 
team and further investigate this deployment issue in the public issue 
tracker. If it is required to share any private or project specific 
information please choose the “Private” component so that the information 
are not visible to the public. 


I wish you the best of luck in proceeding to either open a proper issue 
report in the public issue tracker. 


I would also encourage you to share the public issue tracker link in this 
thread if you keep that public so that other users can go to the link for 
resolution or they can see the updates on the issue. 



On Friday, January 18, 2019 at 3:25:29 PM UTC-5, Matt Haff wrote:
>
> I'm having the same issue, I posted a separate question here per Nick's 
> request - 
> https://groups.google.com/forum/?utm_medium=email_source=footer#!topic/google-appengine/NJMzqz5JqZQ
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/7e695132-6a2a-4202-b8db-bccea1ca86bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Seach Java not working since this morning: com.google.appengine.api.search.SearchException: Error constructing stub for app

['George (Cloud Platform Support)' via Google App Engine]

You may follow issue 123192346  
to monitor progress and eventual fixes. No estimated time to resolution has 
been set. Engineering is already working towards a fix.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/d18a43b5-7d2e-4f6e-a4d2-3b3fa21f68b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Seach Java not working since this morning: com.google.appengine.api.search.SearchException: Error constructing stub for app

['George (Cloud Platform Support)' via Google App Engine]

Hi Bruno, 

We need your project ID, to investigate this specific error further. You 
should not write private information such as project IDs in public forums, 
but you can reply to me privately using the drop-down menu of the top-right 
reply button, and choosing "reply privately to author". Your help is much 
appreciated. 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/cf0c0b72-80cb-4f4f-96ca-6870e90e5e74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Seach Java not working since this morning: com.google.appengine.api.search.SearchException: Error constructing stub for app

[davidcharles via Google App Engine]

Hello Bruno and Akash,

Since Google Groups is meant for conceptual discussions and this is a 
report about an issue with the platform, please create a Google Issue 
Tracker  and include 
all the relevant information since Issue Tracker is the right place to 
report issues about the Google Cloud platform.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/bf717203-9958-4e88-a4e2-cb8b2ec788b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Seach Java not working since this morning: com.google.appengine.api.search.SearchException: Error constructing stub for app

[Akash Eldo]

Hi Bruno,

I've had the exact same problem. My application was working until 
yesterday(1/19) when I tried adding some documents to the index. I got this 
error:
 PutException: Error constructing stub for app

I then tried to use my search endpoint to search documents already in the 
index and I got the same SearchException you did.

On Friday, January 18, 2019 at 3:13:44 PM UTC-5, Bruno Schuermans wrote:
>
> Hello
>
> My application was running fine in app engine. spec: Java8 standard.
> Than since this morning I get this exception when I try to use the 
> SearchService: com.google.appengine.api.search.SearchException: Error 
> constructing stub for app
>
> I have noted that Java7 is not supported from today but I am using Java8 
> Standard environment.
>
> Anybody has encontered the same problem?
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/caef66af-c5ff-40de-92e4-4bb4ee86ac72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Matt Haff]

I'm having the same issue, I posted a separate question here per Nick's 
request 
- 
https://groups.google.com/forum/?utm_medium=email_source=footer#!topic/google-appengine/NJMzqz5JqZQ

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/6398e906-869f-45d5-a8e9-d6227b4afd49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Karolis Krulis]

That's not really a solution. If I deploy the same exact file to AWS it 
takes ~15s on a slow network. I spent 10 minutes deploying on google. 

On Monday, October 3, 2016 at 4:39:50 PM UTC-4, Nick (Cloud Platform 
Support) wrote:
>
> Hey Kevin,
>
> The speed of deployment can be changed by limiting the size of the 
> uploaded app, limiting the complexity of the build necessary in the 
> Dockerfile, if present, and by ensuring a fast and reliable internet 
> connection. Other than these variables, it's hard to comment on what 
> specifically might be making deployment exhibit the timing that it does on 
> your system. 
>
> I hope this is helpful - let me know if you have any further questions! 
> I'll be happy to help!
>
> Cheers,
>
> Nick
> Cloud Platform Community Suppor
>
> On Thursday, September 29, 2016 at 3:48:26 PM UTC-4, Kevin Lau wrote:
>>
>>
>> Is there a faster way to deploy an app? Google App Engine is slow to 
>> deploy, hangs on "Updating service [someproject]..." I am using a flexible 
>> environment with PHP.
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/805201b6-f726-4f5d-a2d5-eb5918d486f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine

['George (Cloud Platform Support)' via Google App Engine]

Hello Siva, 

You seem to refer to the "Get API Key" documentation page 
, or 
another App Engine documentation page. What is the use of referring to 
documentation without describing the problem you are faced with? Your link 
points to a Java course. If you offer such courses, this group is not the 
right place to promote these courses.  

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/20c0a131-8f74-409b-965d-3cc00efda8da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Edgar (Google Cloud Platform Support)' via Google App Engine]

As DeWitt mentioned, currently our median deployment time for production 
goes around 6 minutes as it is working as intended on the flexible 
environment. There has been some additional work and testing done for 
faster deployment for development purposes. 

The updated workflow("in-place version updates") to provide faster 
deployment when developing an application for the Flexible environment is 
described in the comment of 2/12/18 from DeWitt. For ease of reading here 
is the transcript of the workflow:

"To perform an in-place update, please pass the --version flag to the 
deploy command and specify the version you would like to deploy over. 
Additionally, you’ll likely want to prevent that version from becoming the 
default, so be sure to include the --no-promote flag. For example:

$ gcloud app deploy --version  --no-promote 

We recommend you use this flow only for development purposes, and continue 
to deploy full versions for any production traffic."

- Should you like to go further into the GCLB deployment speed, I invite 
you to open another Groups 
 discussion with 
your details regarding the GCLB and reference this thread, as it will be 
easier to follow through the new one as the previous comment here mostly 
pertains to the slow deployment on the flexible environment for developing 
purposes and has been addressed here as explained above.

You would also be able to file a Feature Request 
 
as well directly should you want to see the current deployment speed 
improved. Providing the use case and the details for the slow deployment in 
the feature request will be needed for the engineering team to review for 
implementation. 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/60d22c21-2aa8-496b-9b03-713513af8d70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Shiva Wu]

So I guess no update on the load balancer update speed, huh? It has been 
more than a year...

On Wednesday, 5 April 2017 16:28:11 UTC-7, Nick (Cloud Platform Support) 
wrote:
>
> Hey Stanislas,
>
> So, I can confirm that my prior investigation and intuitions were on the 
> right track. I can confirm that a majority of deployment lag comes from 
> programming the Google Cloud Load Balancers (GCLB). This is what we've seen 
> in this case. Updates have to go out across the entire infrastructure while 
> still respecting certain locks used to keep configurations consistent. 
> These Load Balancers are not visible to users in the Console and not 
> user-configurable as they're infrastructural and meant to be exactly as 
> they are, else users may try to modify or accidentally delete them, which 
> would cause a lot of issues.
>
> We're devoting a lot of energy to decreasing GCLB configuration push 
> times, so rest assured that our efforts in that direction should pay off 
> going forward.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, March 21, 2017 at 6:41:52 PM UTC-4, Stanislas Marion wrote:
>>
>> Great, thank you so much for your help, I'll be very interested in the 
>> details you'll get from your investigation.
>>
>> On Tue, Mar 21, 2017 at 9:22 PM 'Nick (Cloud Platform Support)' via 
>> Google App Engine > wrote:
>>
>>> Hey Stanislas,
>>>
>>> The exact explanation speculated on in my last post shouldn't be taken 
>>> as any description of what's necessarily going on, however it was an 
>>> estimate of what might be happening based on the logs observed. I'm 
>>> corresponding with experts in this area to get a more clear answer at the 
>>> moment. 
>>>
>>> You could look into deploying on Container Engine 
>>> , which would mean that the 
>>> front-end management done by the App Engine Flexible Environment 
>>> infrastructure wouldn't be happening, rather it would be the responsibility 
>>> of the resources you deploy on Container Engine (a managed service based 
>>> pretty transparently on Kubernetes ). Surely 
>>> deploying new container images to your pool of instances in a cluster (or 
>>> multiple clusters) would be quite fast, since the master sitting in front 
>>> of your clusters and the nodes in the cluster are not as massively 
>>> distributed as the App Engine Flexible Environment serving infrastructure, 
>>> hence updating their routing rules would be relatively fast. This is 
>>> something to look into and experiment with if you don't want to wait on the 
>>> more detailed word from experts, but don't rush to that if you're not all 
>>> that curious.
>>>
>>> I'll get back to this thread with more details when they're forthcoming 
>>> in our investigation.
>>>
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support 
>>>
>>> On Tuesday, March 21, 2017 at 3:50:34 PM UTC-4, Stanislas Marion wrote:

 Hi Nick,
 Thanks a lot for the lengthy explanation. 
 In this light, is there anything I can do to speed things up? Like for 
 instance take care of the load-balancer myself? Indeed I don't see a 
 reason 
 why it should need to be changed. Could I do this with GAE or would I have 
 to move to G Container/Compute E?
 Cheers,

 On Tue, Mar 21, 2017 at 8:42 PM 'Nick (Cloud Platform Support)' via 
 Google App Engine > wrote:

> Hey Stanislas,
>
> My initial hunch was that the issue was the deployment of other 
> resources necessary to support the containers running. My analysis of 
> deployment-related logs appears to confirm this:
>
> I created a simple NodeJS app using your dockerfile and default.yaml. 
> I then pushed the docker image to gcr.io and ran "gcloud app deploy 
> --image-url ..."
>
> After about 1 minute of waiting, all resources associated with the 
> deployment had apparently completed, but the command had not returned yet:
>
> ```
> $ gcloud deployment-manager resources list --deployment 
> aef-default-20170321t185300
>
> NAME   TYPE   
>   STATE  ERRORS  INTENT
> aef-default-20170321t185300-00 
> compute.beta.regionInstanceGroupManager  COMPLETED  []
> aef-default-20170321t185300-00ahs  compute.v1.httpsHealthCheck 
>  COMPLETED  []
> aef-default-20170321t185300-00it   compute.v1.instanceTemplate 
>  COMPLETED  []
> aef-default-20170321t185300-bs compute.v1.backendService   
>  COMPLETED  []
> aef-default-20170321t185300-hcfw   compute.v1.firewall 
>  COMPLETED  []
> aef-default-20170321t185300-hcscompute.v1.httpsHealthCheck 
>  COMPLETED  []
> ```
>
> At around the same time that the last of the above completed, I see 
> the following in the Console 

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Shiva Wu]

So I guess no update on the GCLB deployment speed, huh? It has been more 
than a year...

On Wednesday, 5 April 2017 16:28:11 UTC-7, Nick (Cloud Platform Support) 
wrote:
>
> Hey Stanislas,
>
> So, I can confirm that my prior investigation and intuitions were on the 
> right track. I can confirm that a majority of deployment lag comes from 
> programming the Google Cloud Load Balancers (GCLB). This is what we've seen 
> in this case. Updates have to go out across the entire infrastructure while 
> still respecting certain locks used to keep configurations consistent. 
> These Load Balancers are not visible to users in the Console and not 
> user-configurable as they're infrastructural and meant to be exactly as 
> they are, else users may try to modify or accidentally delete them, which 
> would cause a lot of issues.
>
> We're devoting a lot of energy to decreasing GCLB configuration push 
> times, so rest assured that our efforts in that direction should pay off 
> going forward.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, March 21, 2017 at 6:41:52 PM UTC-4, Stanislas Marion wrote:
>>
>> Great, thank you so much for your help, I'll be very interested in the 
>> details you'll get from your investigation.
>>
>> On Tue, Mar 21, 2017 at 9:22 PM 'Nick (Cloud Platform Support)' via 
>> Google App Engine > wrote:
>>
>>> Hey Stanislas,
>>>
>>> The exact explanation speculated on in my last post shouldn't be taken 
>>> as any description of what's necessarily going on, however it was an 
>>> estimate of what might be happening based on the logs observed. I'm 
>>> corresponding with experts in this area to get a more clear answer at the 
>>> moment. 
>>>
>>> You could look into deploying on Container Engine 
>>> , which would mean that the 
>>> front-end management done by the App Engine Flexible Environment 
>>> infrastructure wouldn't be happening, rather it would be the responsibility 
>>> of the resources you deploy on Container Engine (a managed service based 
>>> pretty transparently on Kubernetes ). Surely 
>>> deploying new container images to your pool of instances in a cluster (or 
>>> multiple clusters) would be quite fast, since the master sitting in front 
>>> of your clusters and the nodes in the cluster are not as massively 
>>> distributed as the App Engine Flexible Environment serving infrastructure, 
>>> hence updating their routing rules would be relatively fast. This is 
>>> something to look into and experiment with if you don't want to wait on the 
>>> more detailed word from experts, but don't rush to that if you're not all 
>>> that curious.
>>>
>>> I'll get back to this thread with more details when they're forthcoming 
>>> in our investigation.
>>>
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support 
>>>
>>> On Tuesday, March 21, 2017 at 3:50:34 PM UTC-4, Stanislas Marion wrote:

 Hi Nick,
 Thanks a lot for the lengthy explanation. 
 In this light, is there anything I can do to speed things up? Like for 
 instance take care of the load-balancer myself? Indeed I don't see a 
 reason 
 why it should need to be changed. Could I do this with GAE or would I have 
 to move to G Container/Compute E?
 Cheers,

 On Tue, Mar 21, 2017 at 8:42 PM 'Nick (Cloud Platform Support)' via 
 Google App Engine > wrote:

> Hey Stanislas,
>
> My initial hunch was that the issue was the deployment of other 
> resources necessary to support the containers running. My analysis of 
> deployment-related logs appears to confirm this:
>
> I created a simple NodeJS app using your dockerfile and default.yaml. 
> I then pushed the docker image to gcr.io and ran "gcloud app deploy 
> --image-url ..."
>
> After about 1 minute of waiting, all resources associated with the 
> deployment had apparently completed, but the command had not returned yet:
>
> ```
> $ gcloud deployment-manager resources list --deployment 
> aef-default-20170321t185300
>
> NAME   TYPE   
>   STATE  ERRORS  INTENT
> aef-default-20170321t185300-00 
> compute.beta.regionInstanceGroupManager  COMPLETED  []
> aef-default-20170321t185300-00ahs  compute.v1.httpsHealthCheck 
>  COMPLETED  []
> aef-default-20170321t185300-00it   compute.v1.instanceTemplate 
>  COMPLETED  []
> aef-default-20170321t185300-bs compute.v1.backendService   
>  COMPLETED  []
> aef-default-20170321t185300-hcfw   compute.v1.firewall 
>  COMPLETED  []
> aef-default-20170321t185300-hcscompute.v1.httpsHealthCheck 
>  COMPLETED  []
> ```
>
> At around the same time that the last of the above completed, I see 
> the following in the Console logs 

[google-appengine] Re: Google App Engine Issue

['Katayoon (Cloud Platform Support)' via Google App Engine]

Hi,

I see you have created a duplicate thread on the same question in Stack 
Overflow 
.
 
In order to avoid duplicating efforts we will let you work with the thread 
in Stack Overflow since Google Groups are reserved for general discussions 
about Google Cloud Platform-end products and not for technical questions. 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/148787e5-83f7-4e84-b725-a7fd567d5137%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Nodejs flex, does it utilise all cores of the instances, or do I have to manually create processes?

['George (Cloud Platform Support)' via Google App Engine]

You are right about all cores, it is not appropriate to think otherwise. 
One should also keep in mind that these are virtual machines. My point, in 
the reply above, is that you have control over threading by way of your 
app's node.js code. 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/b43f124f-e63f-445c-8ded-1aa51d74b940%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Nodejs flex, does it utilise all cores of the instances, or do I have to manually create processes?

[Sudhanshu Gaur]

So Ap Engine Flex by default utilises all cores of the VM to run my NodeJS 
processes?

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/ff7026b3-8d0d-4357-8c61-3a84fe91359a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Standard Environment With node-js

['Olu' via Google App Engine]

Clicking on the Link, https://excellent-appguard.appspot.com/ works for me. 
I see the Header of the Application "Content About RoboSystems goes here". 
So, I cannot reproduce the error being reported. However, if it is an issue 
that sparingly occurs, I recommend that you review the Stackdriver logs 
 of the App Engine Version to determine 
what exactly is causing the error.

"Error: Server Error. The server encountered an error and could not 
complete your request. Please try again in 30 seconds." is just a User 
Interface error, which cannot be used to determine the root cause of the 
error. 

If you can get the specific backend error in the Logs, you can post the 
detail here for better advise on the issue. 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/c545c12d-4e69-41b5-ba47-3e46292a6f1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[samiislam via Google App Engine]

Yes, you are right. In order to connect to the Redis instance, App Engine 
applications must be in the same region as the Redis Instance and on the 
same network to be authorized. Please check the following article 
 
for reference.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/11ebd719-efc0-4284-9ceb-e04ec3ce69d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Prashanth Acharya]

Hi Katayoon,
   The app tries to connect to redis on startup.
I realised that redis was in a different region hence unable to 
connect. 
Would that be the cause of long delays during deployment?


On Monday, October 8, 2018 at 11:47:30 PM UTC+5:30, Katayoon (Cloud 
Platform Support) wrote:
>
> Hi Prashanth,
>
> As DeWitt mentioned, having a delay around 6 minutes median (50th 
> percentile) for a new version of App Engine Flex. deployment is the 
> expected behavior since when you deploy your first application to the 
> flexible environment, your virtual machine (VM) and other infrastructure 
> are set up. 
>
> In your case, 45 minutes is too long and it seems something is 
> misconfigured. So, I recommend to double check if you deploy each service 
> with a separate app.yaml file 
> 
>  
> and if the issue persists, you may report the issue to the Issue Tracker 
>  and provide us 
> with the redacted output of the deploy command you are using (with the 
> --verbosity tag set to debug) along with the output of the “gcloud info 
> --anonymize” command so that we would be able investigate the root cause of 
> the issue.
>
>
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/f34023fe-7631-4b69-a983-f4f3cdad9c55%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Nodejs flex, does it utilise all cores of the instances, or do I have to manually create processes?

['George (Cloud Platform Support)' via Google App Engine]

Hello Sudhanshu, 

Load is efficiently dealt within Flexible Environment, there is no reason 
to assume otherwise. You do have control over thread creation. To this 
purpose, you typically do not need to use anything other than your 
language’s built-in threading or multiprocessing tools. You may check 
node.js documentation  related 
to threading. 

Related to the above: you can configure resources 

 
in the app.yaml configuration file, with statements similar to: 

resources:
  cpu: 1
  memory_gb: 0.5
  disk_size_gb: 10

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/568fdab5-ae80-475d-9ae8-690c6a83ca06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Katayoon (Cloud Platform Support)' via Google App Engine]

Hi Prashanth,

As DeWitt mentioned, having a delay around 6 minutes median (50th 
percentile) for a new version of App Engine Flex. deployment is the 
expected behavior since when you deploy your first application to the 
flexible environment, your virtual machine (VM) and other infrastructure 
are set up. 

In your case, 45 minutes is too long and it seems something is 
misconfigured. So, I recommend to double check if you deploy each service 
with a separate app.yaml file 

 
and if the issue persists, you may report the issue to the Issue Tracker 
 and provide us with 
the redacted output of the deploy command you are using (with the 
--verbosity tag set to debug) along with the output of the “gcloud info 
--anonymize” command so that we would be able investigate the root cause of 
the issue.



-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/9f47b5f3-5fdf-41b8-bfce-a843ac0b3bb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Prashanth Acharya]

Is there any updated. I have Rails flex instances timeout after 45mins( 2 
services).

On Tuesday, December 12, 2017 at 11:07:43 PM UTC+5:30, DeWitt Clinton wrote:
>
> Hi all,
>
> I’m on the App Engine team and I agree, flexible deployments are currently 
> too slow. The observations in this thread generally match our own: 
> Deploying a new version of an app takes around six minutes median (50th 
> percentile), with tail spikes several times that (99th percentile). 
> Language choice or app size isn’t a factor, as these setup costs are 
> independent of the runtime or code being deployed. 
>
> For many apps, where production versions are pushed via long-running, 
> asynchronous CI/CD pipelines, the exact timing may not matter so much. But 
> for everyone who depends on app deployments for development purposes, this 
> is too much.
>
> For those cases, we are testing an improved deployment flow that will let 
> you update an existing version in-place in around 150 seconds median. We 
> hope to release the fast in-place updates for everyone next month, but if 
> you’d like to help us test it out a little sooner please tell me your 
> project id here 
> 
>  
> and I’ll whitelist it.
>
> If you miss this signup, don’t worry, we plan to turn faster in-place 
> updates on for all projects by default in the new year.
>
> Thanks!
>
> -DeWitt
>
>
> On Tuesday, November 21, 2017 at 12:46:32 PM UTC-8, Gunar Cassiano Gessner 
> wrote:
>>
>> Speaking from experience here.
>> Just move on.
>> Google App Engine (esp. Flexible Engine) is not worthy of your time.
>>
>> Take care,
>> @gunar
>>
>> On Tue, Nov 21, 2017 at 1:24 AM, Vijay M  wrote:
>>
>>> I have been struggling with the same issue. I tried deploying a very 
>>> simple app and waited for several minutes before the process timed out. I 
>>> even ran into the same timeout issue with Google's own samples from  
>>>
>>> https://github.com/GoogleCloudPlatform/python-docs-samples/
>>> appengine/flexible/hello_world
>>>
>>> Coming from AWS, it has been very frustrating working with GCP. One more 
>>> day of this and I am going back to AWS. 
>>>
>>> On Thursday, September 29, 2016 at 12:48:26 PM UTC-7, Kevin Lau wrote:


 Is there a faster way to deploy an app? Google App Engine is slow to 
 deploy, hangs on "Updating service [someproject]..." I am using a flexible 
 environment with PHP.

>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Google App Engine" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/google-appengine/hZMEkmmObDU/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> google-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@googlegroups.com.
>>> 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/0c5f7fed-3551-4426-88e4-1383b4151084%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/a5aa631d-0c5f-43ce-ae71-54b3080c49dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Flexible Cron Tasks Fail with SSL Redirection

[Chad Paulson]

Thank you both for the heads up!

I completely forgot about the application-level redirect I put in place and 
was able to solve this quite easily by adding exceptions.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/ff79cf48-ea47-4904-bfdc-d1026b225a86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Flexible Cron Tasks Fail with SSL Redirection

['Amit (Google Cloud Support)' via Google App Engine]

Hi Chad

I went through a couple of posts that could related to this error. I 
believe this is the cause of the issue - cron accesses target URLs over 
http, and so when the handler tries to redirect to https it's throwing the 
301 'Moved permanently' response. It seems like cron jobs are triggered by 
the App Engine Cron Service over http. If you're forcing https redirection, 
consider adding another handler [3] just for the Cron jobs without any 
redirection. Also you can check this [4] link to enable retrying all failed 
cron jobs. I hope it helps. If the solutions mentioned in given links 
doesn’t work for you and convinced it might be a bug, you can report this 
in issue tracker .

[1] https://groups.google.com/forum/#!topic/google-appengine/PsOGESDKiGk

[2] 
https://stackoverflow.com/questions/15667681/can-app-engine-cron-jobs-use-https-ssl

[3] 
https://cloud.google.com/appengine/docs/standard/python/config/cron#securing_urls_for_cron

[4] 
https://cloud.google.com/appengine/docs/standard/python/config/cron#retrying_cron_jobs_that_fail


On Saturday, September 22, 2018 at 12:51:17 PM UTC-4, Chad Paulson wrote:
>
> Hello,
>
> I am having an issue getting cron tasks to work and I'm not sure there is 
> currently a remedy due to the limited nature of SSL support for GAE 
> flexible and the lack of handler support.
>
> Currently all of the tasks are failing because they are returning a 301 
> HTTP response code.  While this seems like an edge case, it also seems like 
> a bit of an infrastructure oversight and I would greatly appreciate any 
> assistance on this matter.
>
> Thanks,
> Chad
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/56f4c717-ac29-427e-bdcf-5282174da2cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Logs not showing in the console?

['Katayoon (Cloud Platform Support)' via Google App Engine]

I tried to reproduce the issue by following the quickstarts for Node.js on App 
Engine Standard 

 
and App Engine Flexible 
,
 
but it works fine for me and I can see the logs via Stackdriver Log Viewer. 

I recommend that you post your full detailed question 
 to Stack Overflow 
, using the supported 
Cloud tags since Google Groups are reserved for general Google Cloud 
Platform-end product discussions and not for technical questions.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/5feda401-474c-4be2-bef1-6c4fe68bb1bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Logs not showing in the console?

[Sudhanshu Gaur]

Also, I am using the same code on compute engine but there logs all logs 
are getting printed, but in App Engine for some cases, they are missing 
eveytime?

On Wednesday, August 29, 2018 at 1:14:58 AM UTC+5:30, Sudhanshu Gaur wrote:
>
> Google App Engine many Logs are skipping, and not getting shown in the 
> Logging console, and it is happening always, the Logs I am showing using 
> console.log() are getting skipped but mongoosequery logs are getting 
> printed.
>
> Can anyone please tell me why is this happening?
>
> Thank You
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/4a095919-a025-449c-8921-c2523e308eab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Logs not showing in the console?

[Sudhanshu Gaur]

Please help me, I am facing this issue from 3 days and haven't found any 
solution, my app is in production and I cannot debug the issues, I never 
expected these kinds of vulnerabilities from Google Cloud Platform, 
previously everything was working very fine, but How this issue has come?

Please help me.

On Wednesday, August 29, 2018 at 1:14:58 AM UTC+5:30, Sudhanshu Gaur wrote:
>
> Google App Engine many Logs are skipping, and not getting shown in the 
> Logging console, and it is happening always, the Logs I am showing using 
> console.log() are getting skipped but mongoosequery logs are getting 
> printed.
>
> Can anyone please tell me why is this happening?
>
> Thank You
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/877f6fdf-a9ee-472a-9fe8-d45c4a045292%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Logs not showing in the console?

[Sudhanshu Gaur]

I have added debugging points but the thing is my debug points are 
executed, but how come in the logs they are not getting printed.

On Wednesday, August 29, 2018 at 1:14:58 AM UTC+5:30, Sudhanshu Gaur wrote:
>
> Google App Engine many Logs are skipping, and not getting shown in the 
> Logging console, and it is happening always, the Logs I am showing using 
> console.log() are getting skipped but mongoosequery logs are getting 
> printed.
>
> Can anyone please tell me why is this happening?
>
> Thank You
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/267b0fdd-7a20-440e-b7d8-bedf2ca81a12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Logs not showing in the console?

[Sudhanshu Gaur]

Still waiting for any solution

On Wednesday, August 29, 2018 at 1:14:58 AM UTC+5:30, Sudhanshu Gaur wrote:
>
> Google App Engine many Logs are skipping, and not getting shown in the 
> Logging console, and it is happening always, the Logs I am showing using 
> console.log() are getting skipped but mongoosequery logs are getting 
> printed.
>
> Can anyone please tell me why is this happening?
>
> Thank You
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/c54d8b1e-6633-4b61-b40b-1baa7fdfb51e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine and Knative

['Katayoon (Cloud Platform Support)' via Google App Engine]

You can have both App Engine and Kubernetes Engine in a single project, 
however it is recommended creating a new project for this alpha program.

Knative is the most suitable approach when you want a serverless App Engine 
Flex-like experience, be available on every cloud (multi-cloud), hybrid, 
and on-prem setup. The goal for Knative is to fill that need, especially 
for people that already use kubernetes. 

Knative is on top of Kubernetes and is currently available in the alpha 
version 
,
 
but App Engine is a solid GA service that provides a fully managed 
experience and runs enormous services.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/85bc7f5e-dac3-4987-9beb-025381fbf025%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine roadmap

['Katayoon (Cloud Platform Support)' via Google App Engine]

I have created a feature request on "GAE roadmap" in the Issue Tracker 
. You may star the feature 
request for further updates, however we can't provide you ant ETA on it.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/280d6b96-abbf-4594-b3c8-ccafaca3d94c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine roadmap

[bFlood]

that article is from 2008 and the link does not point at a road-map, its 
just a description of the current standard offerings



On Friday, August 17, 2018 at 6:35:02 PM UTC-4, Katayoon (Cloud Platform 
Support) wrote:
>
> As mentioned in “Google App Engine Roadmap - Now Published 
> ”
>  
> article, App Engine road-map can be found here 
> .
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/9648550c-9abb-4879-a013-c94f3f48a130%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine and Knative

[Anil Kumar]

Thanks for your reply Katayoon.
I understand that both Knative and App Engine are 'managed platforms' and
both are two different offerings. What I am looking for is along the
following lines :
1. If I am starting on a completely new project now - then should I take
the Knative or the App Engine route?
2.  What are the advantages / disadvantages of using Knative vs App Engine?
3. When should I use Knative and when should I use App Engine?
-Anil

On Sat, Aug 18, 2018 at 4:16 AM 'Katayoon (Cloud Platform Support)' via
Google App Engine  wrote:

> For the time being they are different products. Knative
>  is a Kubernetes-based platform, and
> App Engine is a different fully managed platform to build and deploy
> applications.
>
> Your question is too general. More details and clarification would help us
> to assist you further.
>
> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> 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/0243ddb4-dab1-4fb8-9b04-16486efed15d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/CACyeKUusSXx5Om60%3Dmx9nX80OoLUkmzgUQ0ar7TsoFLTNOmyjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine and Knative

['Katayoon (Cloud Platform Support)' via Google App Engine]

For the time being they are different products. Knative 
 is a Kubernetes-based platform, and App 
Engine is a different fully managed platform to build and deploy 
applications.

Your question is too general. More details and clarification would help us 
to assist you further. 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/0243ddb4-dab1-4fb8-9b04-16486efed15d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine roadmap

['Katayoon (Cloud Platform Support)' via Google App Engine]

As mentioned in “Google App Engine Roadmap - Now Published 
”
 
article, App Engine road-map can be found here 
.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/a2e960eb-47b4-4bf5-b527-5fdfa671b53c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App engine with SSL does not work on Firefox

[Binh Bui Van]

Thanks Katayoon,
It is not seem to be my issue.
Opened new tracker issue

Vào 21:25:16 UTC+7 Thứ Tư, ngày 08 tháng 8 năm 2018, Binh Bui Van đã viết:
>
> Hi all,
>
> I have config ssl for Google App Engine (python standar).
> It work perfect on chrome.
> But with Firefox, it show 'Your connection is not secure'
>
> Any suggestions on what I might be doing wrong?
>
>
>
> Thanks
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/9c3519b0-699d-403e-9588-6d88b8dbf961%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App engine with SSL does not work on Firefox

['Katayoon (Cloud Platform Support)' via Google App Engine]

Hi Binh,

You may take a look at this thread in Stack Overflow 

 
which seems to be similar to your issue. If the issue persists, I recommend 
to open a report in the Issue Tracker 
 for further 
investigation.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/4e442877-65e8-45d4-b3e1-446a355c58de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine multiple regions

[BG Bruno]

I agree - this function have to be there already


also "google functions" are regional 
https://firebase.google.com/docs/functions/locations

if I see it right "aws lambda, aws elasticbeanstalk, aws cloudformation" 
support loadbalancing 勞
https://aws.amazon.com/blogs/compute/building-a-multi-region-serverless-application-with-amazon-api-gateway-and-aws-lambda/
https://aws.amazon.com/blogs/devops/part-2-develop-deploy-and-manage-for-scale-with-elastic-beanstalk-and-cloudformation


Q how can I create worldwide apps now with google ? 



On Monday, October 2, 2017 at 11:08:43 PM UTC+2, Robert Dyas wrote:
>
> We need this too for GAE Standard Environment... basically an GAE in EU 
> going to backend databases hosted on VMs in EU, and GAE in US going to 
> backend databases hosted on VMs in US.
>
> On Monday, June 20, 2016 at 5:13:12 AM UTC-4, Yon Dev wrote:
>>
>> I am evaluating whether GAE would be a good fit for an upcoming project.
>>
>> I was wondering how scaling across regions work with GAE? If I set my 
>> project location to US and then create an GAE instance and most access to 
>> the GAE is from EU will it automatically scale out to Europe? 
>> Or how does it work?
>> If it was a on Compute Engine I believe I could have created multiple 
>> instances and then made a HTTP Load Balancer that would route the user to 
>> the closest instance based on proximity.
>>
>> https://cloud.google.com/about/locations/
>> Reading the link above it says that it scales automatically within or 
>> accross multi-regional locations.
>> What does that mean? Do I have to enable automatic scaling across 
>> regions? If so, how do I do that?
>> And secondly, if it does handle automatic scaling across regions, the 
>> choice one makes for App engine location when creating a new project, is 
>> that irrelevant for a Google App Engine instance?
>>
>> I tried asking on Stackoverflow but without answer so I am turning to you 
>> in hope for an answer.
>>
>> http://stackoverflow.com/questions/37849433/google-app-engine-multiple-regions
>>
>> Thank you in advance,
>> Yon
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/1825497d-1a90-44ed-aa8a-716479225b2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine multiple regions

[BG Bruno]

I agree - this function have to be there already


also "google functions" are regional 
https://firebase.google.com/docs/functions/locations

if I see it right "aws lambda, aws elasticbeanstalk, aws cloudformation" 
support loadbalancing 勞
https://aws.amazon.com/blogs/compute/building-a-multi-region-serverless-application-with-amazon-api-gateway-and-aws-lambda/
https://aws.amazon.com/blogs/devops/part-2-develop-deploy-and-manage-for-scale-with-elastic-beanstalk-and-cloudformation


Q how can I create worldwide apps now with google ? 



On Monday, June 20, 2016 at 11:13:12 AM UTC+2, Yon Dev wrote:
>
> I am evaluating whether GAE would be a good fit for an upcoming project.
>
> I was wondering how scaling across regions work with GAE? If I set my 
> project location to US and then create an GAE instance and most access to 
> the GAE is from EU will it automatically scale out to Europe? 
> Or how does it work?
> If it was a on Compute Engine I believe I could have created multiple 
> instances and then made a HTTP Load Balancer that would route the user to 
> the closest instance based on proximity.
>
> https://cloud.google.com/about/locations/
> Reading the link above it says that it scales automatically within or 
> accross multi-regional locations.
> What does that mean? Do I have to enable automatic scaling across regions? 
> If so, how do I do that?
> And secondly, if it does handle automatic scaling across regions, the 
> choice one makes for App engine location when creating a new project, is 
> that irrelevant for a Google App Engine instance?
>
> I tried asking on Stackoverflow but without answer so I am turning to you 
> in hope for an answer.
>
> http://stackoverflow.com/questions/37849433/google-app-engine-multiple-regions
>
> Thank you in advance,
> Yon
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/4cb49a4d-3557-4a5c-9a8d-dc5986f895ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google app engine creating instances not in 'default internal' ip ranges?

['Julie (cloud platform support)' via Google App Engine]

On Thursday, August 2, 2018 at 3:13:49 PM UTC-4, Ryan Barker wrote:
>
> I am having issues that some of the instances that are being automatically 
> spun up by google app engine are not able to connect to my database. I have 
> a hunch the issue is that the problem relates to ip addresses outside of 
> the range of ip addresses that should be set up for internal machines.  
> Unfortunately (or fortunately) the problem resolved itself before I could 
> get the ip address of the machines that could not connect.
>
> 1) How can I find the logs of internal ip addresses that are being created?
> 2) What should the internal firewall ip range be set to? It is currently 
> set to 10.128.0.0/9 
>
>
> Thanks
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/5e9e98d4-8b35-4feb-942f-636580b43b1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine group

[Giuliano Ribeiro]

Yes, it is moderated.

_
Giuliano


On Mon, Aug 6, 2018 at 2:07 PM Steve Neal  wrote:

> Hi,
>
> Can you tell me if this group is moderated please?
>
> I've tried twice to post a question and it's not visible.
>
> Thanks, Steve.
>
>
> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> 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/CAGw%2BpadXaYAj326cwHnWG8e6h%2BkBbdQga93iOKFCXAh8%3DLEuvA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/CAFFKEc20MNKyz%2BxcsPN%3DS_czu91K%2BwKD3qKhuw4Kb4bfYiAB_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine group

[Steve Neal]

Hi,

Can you tell me if this group is moderated please?

I've tried twice to post a question and it's not visible.

Thanks, Steve.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/CAGw%2BpadXaYAj326cwHnWG8e6h%2BkBbdQga93iOKFCXAh8%3DLEuvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine. Start from last week, keep responding 503 error.

['George (Cloud Platform Support)' via Google App Engine]

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 truncated exponential 
back-off . 

This forum meant for general discussion on the platform and its services. 
If you would like to have this issue attract proper attention, and finally 
solved by Engineering, you are encouraged to open a case in the Public 
Tracker . 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/941822fe-06d3-4763-8627-2fe6505f814f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine. Start from last week, keep responding 503 error.

[epssdev]

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 not access the website and I found the server 
> respond 503 error. 
> Do you have any guide how to locate the root cause?
> I tried to redeploy it. It worked last night and broken again this morning.
>
> Thanks.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/6e9a0a14-967c-4c22-ab78-ad8505c88af9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Upload File to API Directory

['George (Cloud Platform Support)' via Google App Engine]

In case of an app deployed in the Cloud, the local filesystem that your 
application is deployed to is not writeable. This behavior ensures the 
security and scalability of your application. Why reading the file from GS 
represents a problem? Are there speed or otherwise performance 
considerations involved? If you are concerned about cost, your GS usage 
pattern may quite likely qualify as free of cost. You may have a look at 
the "Cloud Storage Pricing" page 
.  

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/0f42adf2-7726-484f-bad5-e9baf174e574%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine. Start from last week, keep responding 503 error.

[yi he]

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 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 Ribeiro wrote:
>>
>> 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 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)
>>>
>>> 018-07-06 12:14:44.000 CDT 
>>>
>>> INFO: Error body: RPC Error: /StubbyService.Send to (unknown) : 
>>> APP_ERROR(2)
>>> Expand all | Collapse all
>>> {
>>> insertId: "1l61xvbf9j89do"  
>>> labels: {…}  
>>> logName: "projects/triage/logs/appengine.googleapis.com%2Fstderr"  
>>> receiveTimestamp: "2018-07-06T17:14:44.240478404Z"  
>>> resource: {…}  
>>> textPayload: "INFO: Error body: RPC Error: /StubbyService.Send to 
>>> (unknown) : APP_ERROR(2) "  
>>> timestamp: "2018-07-06T17:14:44Z"  
>>> }
>>>
>>>
>>>
>>> 2018-07-06 12:14:44.000 CDTjava.util.concurrent.ExecutionException: 
>>> com.google.apphosting.api.ApiProxy$RPCFailedException: The remote RPC to 
>>> the application server failed for the call logservice.Flush(). at 
>>> java.util.concurrent.FutureTask.report(FutureTask.java:122) at 
>>> java.util.concurrent.FutureTask.get(FutureTask.java:206) at 
>>> com.google.apphosting.vmruntime.VmAppLogsWriter.waitForCurrentFlush(VmAppLogsWriter.java:226)
>>>  at 
>>> com.google.apphosting.vmruntime.VmAppLogsWriter.flushAndWait(VmAppLogsWriter.java:211)
>>>  at 
>>> com.google.apphosting.vmruntime.VmApiProxyEnvironment.flushLogs(VmApiProxyEnvironment.java:508)
>>>  at 
>>> com.google.apphosting.vmruntime.VmRuntimeUtils.flushLogsAndAddHeader(VmRuntimeUtils.java:109)
>>>  at 
>>> com.google.apphosting.vmruntime.jetty9.VmRuntimeWebAppContext.doScope(VmRuntimeWebAppContext.java:323)
>>>  at 
>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>>>  at 
>>> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>>>  at 
>>> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
>>>  at 
>>> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119)
>>>  at org.eclipse.jetty.server.Server.handle(Server.java:517) at 
>>> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:306) at 
>>> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242) 
>>> at 
>>> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261)
>>>  at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at 
>>> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75)
>>>  at 
>>> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213)
>>>  at 
>>> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)
>>>  at 
>>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
>>>  at 
>>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
>>>  at java.lang.Thread.run(Thread.java:745) Caused by: 
>>> com.google.apphosting.api.ApiProxy$RPCFailedException: The remote RPC to 
>>> the application server failed for the call logservice.Flush(). at 
>>> com.google.apphosting.vmruntime.VmApiProxyDelegate.runSyncCall(VmApiProxyDelegate.java:175)
>>>  at 
>>> com.google.apphosting.vmruntime.VmApiProxyDelegate.makeApiCall(VmApiProxyDelegate.java:155)
>>>  at 
>>> com.google.apphosting.vmruntime.VmApiProxyDelegate.access$000(VmApiProxyDelegate.java:75)
>>>  at 
>>> com.google.apphosting.vmruntime.VmApiProxyDelegate$MakeSyncCall.call(VmApiProxyDelegate.java:434)
>>>  at 
>>> com.google.apphosting.vmruntime.VmApiProxyDelegate$MakeSyncCall.call(VmApiProxyDelegate.java:410)
>>>  at java.util.concurrent.FutureTask.run(FutureTask.java:266) at 
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>  at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>  ... 1 more
>>>
>>> 2018-07-06 12:14:44.000 CDT2018-07-06 
>>> 17:14:44.933:INFO:oejs.ServerConnector:Thread-1: Stopped 
>>> ServerConnector@43184193{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
>>> Expand all | 

[google-appengine] Re: Google App Engine. Start from last week, keep responding 503 error.

[yi he]

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 Ribeiro wrote:
>
> 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 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)
>>
>> 018-07-06 12:14:44.000 CDT 
>>
>> INFO: Error body: RPC Error: /StubbyService.Send to (unknown) : 
>> APP_ERROR(2)
>> Expand all | Collapse all
>> {
>> insertId: "1l61xvbf9j89do"  
>> labels: {…}  
>> logName: "projects/triage/logs/appengine.googleapis.com%2Fstderr"  
>> receiveTimestamp: "2018-07-06T17:14:44.240478404Z"  
>> resource: {…}  
>> textPayload: "INFO: Error body: RPC Error: /StubbyService.Send to 
>> (unknown) : APP_ERROR(2) "  
>> timestamp: "2018-07-06T17:14:44Z"  
>> }
>>
>>
>>
>> 2018-07-06 12:14:44.000 CDTjava.util.concurrent.ExecutionException: 
>> com.google.apphosting.api.ApiProxy$RPCFailedException: The remote RPC to the 
>> application server failed for the call logservice.Flush(). at 
>> java.util.concurrent.FutureTask.report(FutureTask.java:122) at 
>> java.util.concurrent.FutureTask.get(FutureTask.java:206) at 
>> com.google.apphosting.vmruntime.VmAppLogsWriter.waitForCurrentFlush(VmAppLogsWriter.java:226)
>>  at 
>> com.google.apphosting.vmruntime.VmAppLogsWriter.flushAndWait(VmAppLogsWriter.java:211)
>>  at 
>> com.google.apphosting.vmruntime.VmApiProxyEnvironment.flushLogs(VmApiProxyEnvironment.java:508)
>>  at 
>> com.google.apphosting.vmruntime.VmRuntimeUtils.flushLogsAndAddHeader(VmRuntimeUtils.java:109)
>>  at 
>> com.google.apphosting.vmruntime.jetty9.VmRuntimeWebAppContext.doScope(VmRuntimeWebAppContext.java:323)
>>  at 
>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>>  at 
>> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>>  at 
>> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
>>  at 
>> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119)
>>  at org.eclipse.jetty.server.Server.handle(Server.java:517) at 
>> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:306) at 
>> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242) 
>> at 
>> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261)
>>  at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at 
>> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75)
>>  at 
>> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213)
>>  at 
>> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)
>>  at 
>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
>>  at 
>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
>>  at java.lang.Thread.run(Thread.java:745) Caused by: 
>> com.google.apphosting.api.ApiProxy$RPCFailedException: The remote RPC to the 
>> application server failed for the call logservice.Flush(). at 
>> com.google.apphosting.vmruntime.VmApiProxyDelegate.runSyncCall(VmApiProxyDelegate.java:175)
>>  at 
>> com.google.apphosting.vmruntime.VmApiProxyDelegate.makeApiCall(VmApiProxyDelegate.java:155)
>>  at 
>> com.google.apphosting.vmruntime.VmApiProxyDelegate.access$000(VmApiProxyDelegate.java:75)
>>  at 
>> com.google.apphosting.vmruntime.VmApiProxyDelegate$MakeSyncCall.call(VmApiProxyDelegate.java:434)
>>  at 
>> com.google.apphosting.vmruntime.VmApiProxyDelegate$MakeSyncCall.call(VmApiProxyDelegate.java:410)
>>  at java.util.concurrent.FutureTask.run(FutureTask.java:266) at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>  ... 1 more
>>
>> 2018-07-06 12:14:44.000 CDT2018-07-06 
>> 17:14:44.933:INFO:oejs.ServerConnector:Thread-1: Stopped 
>> ServerConnector@43184193{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
>> Expand all | Collapse all
>> {
>>  insertId: "1r9ki5zf9mcqwx"  
>>  labels: {…}  
>>  logName: "projects/triage/logs/appengine.googleapis.com%2Fstderr"  
>>  receiveTimestamp: "2018-07-06T17:14:45.895354407Z"  
>>  resource: {…}  
>>  textPayload: "2018-07-06 17:14:44.933:INFO:oejs.ServerConnector:Thread-1: 
>> Stopped 

[google-appengine] Re: Google App Engine. Start from last week, keep responding 503 error.

[Giuliano Ribeiro]

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 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)
>
> 018-07-06 12:14:44.000 CDT 
>
> INFO: Error body: RPC Error: /StubbyService.Send to (unknown) : 
> APP_ERROR(2)
> Expand all | Collapse all
> {
> insertId: "1l61xvbf9j89do"  
> labels: {…}  
> logName: "projects/triage/logs/appengine.googleapis.com%2Fstderr"  
> receiveTimestamp: "2018-07-06T17:14:44.240478404Z"  
> resource: {…}  
> textPayload: "INFO: Error body: RPC Error: /StubbyService.Send to 
> (unknown) : APP_ERROR(2) "  
> timestamp: "2018-07-06T17:14:44Z"  
> }
>
>
>
> 2018-07-06 12:14:44.000 CDTjava.util.concurrent.ExecutionException: 
> com.google.apphosting.api.ApiProxy$RPCFailedException: The remote RPC to the 
> application server failed for the call logservice.Flush(). at 
> java.util.concurrent.FutureTask.report(FutureTask.java:122) at 
> java.util.concurrent.FutureTask.get(FutureTask.java:206) at 
> com.google.apphosting.vmruntime.VmAppLogsWriter.waitForCurrentFlush(VmAppLogsWriter.java:226)
>  at 
> com.google.apphosting.vmruntime.VmAppLogsWriter.flushAndWait(VmAppLogsWriter.java:211)
>  at 
> com.google.apphosting.vmruntime.VmApiProxyEnvironment.flushLogs(VmApiProxyEnvironment.java:508)
>  at 
> com.google.apphosting.vmruntime.VmRuntimeUtils.flushLogsAndAddHeader(VmRuntimeUtils.java:109)
>  at 
> com.google.apphosting.vmruntime.jetty9.VmRuntimeWebAppContext.doScope(VmRuntimeWebAppContext.java:323)
>  at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
> at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>  at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
>  at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119)
>  at org.eclipse.jetty.server.Server.handle(Server.java:517) at 
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:306) at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242) 
> at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261)
>  at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75)
>  at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213)
>  at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)
>  at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
>  at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
>  at java.lang.Thread.run(Thread.java:745) Caused by: 
> com.google.apphosting.api.ApiProxy$RPCFailedException: The remote RPC to the 
> application server failed for the call logservice.Flush(). at 
> com.google.apphosting.vmruntime.VmApiProxyDelegate.runSyncCall(VmApiProxyDelegate.java:175)
>  at 
> com.google.apphosting.vmruntime.VmApiProxyDelegate.makeApiCall(VmApiProxyDelegate.java:155)
>  at 
> com.google.apphosting.vmruntime.VmApiProxyDelegate.access$000(VmApiProxyDelegate.java:75)
>  at 
> com.google.apphosting.vmruntime.VmApiProxyDelegate$MakeSyncCall.call(VmApiProxyDelegate.java:434)
>  at 
> com.google.apphosting.vmruntime.VmApiProxyDelegate$MakeSyncCall.call(VmApiProxyDelegate.java:410)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:266) at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ... 1 more
>
> 2018-07-06 12:14:44.000 CDT2018-07-06 
> 17:14:44.933:INFO:oejs.ServerConnector:Thread-1: Stopped 
> ServerConnector@43184193{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
> Expand all | Collapse all
> {
>  insertId: "1r9ki5zf9mcqwx"  
>  labels: {…}  
>  logName: "projects/triage/logs/appengine.googleapis.com%2Fstderr"  
>  receiveTimestamp: "2018-07-06T17:14:45.895354407Z"  
>  resource: {…}  
>  textPayload: "2018-07-06 17:14:44.933:INFO:oejs.ServerConnector:Thread-1: 
> Stopped ServerConnector@43184193{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
> "  
>  timestamp: "2018-07-06T17:14:44Z"  
> }
>
>
>
> I think above exception or error maybe related. But no idea how to get rid 
> of them.
>
> Thanks
>
> On Friday, July 6, 2018 at 11:34:34 AM UTC-5, Giuliano Ribeiro wrote:
>>
>> Hi Yi, 
>>
>> do you took a look on StackDrive logging? Any issues on the instances 
>> startup?
>>
>>
>>
>> On Friday, July 6, 2018 at 

[google-appengine] Re: Google App Engine. Start from last week, keep responding 503 error.

[yi he]

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)

018-07-06 12:14:44.000 CDT 

INFO: Error body: RPC Error: /StubbyService.Send to (unknown) : APP_ERROR(2)
Expand all | Collapse all
{
insertId: "1l61xvbf9j89do"  
labels: {…}  
logName: "projects/triage/logs/appengine.googleapis.com%2Fstderr"  
receiveTimestamp: "2018-07-06T17:14:44.240478404Z"  
resource: {…}  
textPayload: "INFO: Error body: RPC Error: /StubbyService.Send to (unknown) 
: APP_ERROR(2) "  
timestamp: "2018-07-06T17:14:44Z"  
}



2018-07-06 12:14:44.000 CDTjava.util.concurrent.ExecutionException: 
com.google.apphosting.api.ApiProxy$RPCFailedException: The remote RPC to the 
application server failed for the call logservice.Flush(). at 
java.util.concurrent.FutureTask.report(FutureTask.java:122) at 
java.util.concurrent.FutureTask.get(FutureTask.java:206) at 
com.google.apphosting.vmruntime.VmAppLogsWriter.waitForCurrentFlush(VmAppLogsWriter.java:226)
 at 
com.google.apphosting.vmruntime.VmAppLogsWriter.flushAndWait(VmAppLogsWriter.java:211)
 at 
com.google.apphosting.vmruntime.VmApiProxyEnvironment.flushLogs(VmApiProxyEnvironment.java:508)
 at 
com.google.apphosting.vmruntime.VmRuntimeUtils.flushLogsAndAddHeader(VmRuntimeUtils.java:109)
 at 
com.google.apphosting.vmruntime.jetty9.VmRuntimeWebAppContext.doScope(VmRuntimeWebAppContext.java:323)
 at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
 at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
 at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119) 
at org.eclipse.jetty.server.Server.handle(Server.java:517) at 
org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:306) at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242) at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261)
 at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at 
org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75) 
at 
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213)
 at 
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)
 at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
 at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572) 
at java.lang.Thread.run(Thread.java:745) Caused by: 
com.google.apphosting.api.ApiProxy$RPCFailedException: The remote RPC to the 
application server failed for the call logservice.Flush(). at 
com.google.apphosting.vmruntime.VmApiProxyDelegate.runSyncCall(VmApiProxyDelegate.java:175)
 at 
com.google.apphosting.vmruntime.VmApiProxyDelegate.makeApiCall(VmApiProxyDelegate.java:155)
 at 
com.google.apphosting.vmruntime.VmApiProxyDelegate.access$000(VmApiProxyDelegate.java:75)
 at 
com.google.apphosting.vmruntime.VmApiProxyDelegate$MakeSyncCall.call(VmApiProxyDelegate.java:434)
 at 
com.google.apphosting.vmruntime.VmApiProxyDelegate$MakeSyncCall.call(VmApiProxyDelegate.java:410)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
... 1 more

2018-07-06 12:14:44.000 CDT2018-07-06 
17:14:44.933:INFO:oejs.ServerConnector:Thread-1: Stopped 
ServerConnector@43184193{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
Expand all | Collapse all
{
 insertId: "1r9ki5zf9mcqwx"  
 labels: {…}  
 logName: "projects/triage/logs/appengine.googleapis.com%2Fstderr"  
 receiveTimestamp: "2018-07-06T17:14:45.895354407Z"  
 resource: {…}  
 textPayload: "2018-07-06 17:14:44.933:INFO:oejs.ServerConnector:Thread-1: 
Stopped ServerConnector@43184193{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
"  
 timestamp: "2018-07-06T17:14:44Z"  
}



I think above exception or error maybe related. But no idea how to get rid 
of them.

Thanks

On Friday, July 6, 2018 at 11:34:34 AM UTC-5, Giuliano Ribeiro wrote:
>
> 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 website and I found the server 
>> respond 503 error. 
>> Do you have any guide how to locate the root cause?
>> I tried to redeploy it. It worked last night and broken again this 
>> morning.
>>
>> Thanks.
>>
>

-- 
You received this message because you 

[google-appengine] Re: Google App Engine. Start from last week, keep responding 503 error.

[Giuliano Ribeiro]

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 website and I found the server 
> respond 503 error. 
> Do you have any guide how to locate the root cause?
> I tried to redeploy it. It worked last night and broken again this morning.
>
> Thanks.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/59504a79-06ab-4fd5-beb0-2158af7d8297%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google app engine can requests fail while shifting traffic to the new version?

['Kenworth (Google Cloud Platform)' via Google App Engine]

The answer is different depending on the App Engine environment. GAE 
Standard for example, supports gradual traffic migration wherein you can 
enable 'warmup request' to prepare the new instances before those instances 
serve any traffic.

In contrast, GAE Flex does not support gradual traffic migration which 
means user requests are sent to those instances before the instances get 
created. This results to delay/latency (not an outright fail) since the 
request has to wait until the instance gets up and running. It is possible 
that request may fail if the request timeouts before the instance is ready. 
See full article here 
.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/0cdab1f5-54da-46ed-b21b-8aba5edd5867%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Java deployment with gcloud skips almost all files

[Thomas Becker]

George,

I'm sure you're right about Maven being the better way to do things. Here's 
the reason why I haven't gone there. I've been working with the Google App 
Engine Eclipse plugin since 2010 or so. I recently switched to the new 
plugin, Google Cloud Tools for Eclipse. After installing that plugin, I was 
prompted to convert to a Google Cloud Tools project, which I did. Since I 
wasn't using Maven before, my project was  converted to a non-Maven Google 
Cloud Tools for Eclipse project. So now what I need to do is convert a 
non-Maven Google Cloud Tools for Eclipse project to a Maven Google Cloud 
Tools for Eclipse project. I haven't seen that particular work flow 
mentioned anywhere in the docs. Any advice, any experience?

On Sunday, June 17, 2018 at 12:49:45 PM UTC-6, George (Cloud Platform 
Support) wrote:
>
> Hello Thomas, 
>
> This is an excellent observation! Grateful for bringing this apparent 
> discrepancy to our attention. The page you refer to might well have to be 
> brought in tune with the others. Why do I mention the other pages? Because 
> all other Java-related pages and tutorials on cloud.google.com, for 
> instance the collection of tutorials linked to on the "Building an App on 
> App Engine" documentation page 
> , 
> and I stress "all", indicate mvn appengine:deploy as the proper command to 
> deploy a Java app. This cannot be a simple coincidence. 
>
> Why do you prefer to use gcloud in spite of the general consensus in favor 
> of Maven? Would this meet a special need of yours? Maven offers other 
> advantages, beside ease of app deployment. 
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/ad0a2922-dd35-4983-81f7-1d855ad97047%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Java deployment with gcloud skips almost all files

['George (Cloud Platform Support)' via Google App Engine]

Hello Thomas, 

This is an excellent observation! Grateful for bringing this apparent 
discrepancy to our attention. The page you refer to might well have to be 
brought in tune with the others. Why do I mention the other pages? Because 
all other Java-related pages and tutorials on cloud.google.com, for 
instance the collection of tutorials linked to on the "Building an App on 
App Engine" documentation page 
, and 
I stress "all", indicate mvn appengine:deploy as the proper command to 
deploy a Java app. This cannot be a simple coincidence. 

Why do you prefer to use gcloud in spite of the general consensus in favor 
of Maven? Would this meet a special need of yours? Maven offers other 
advantages, beside ease of app deployment. 

mvn appengine:deploy

mvn appengine:deploy

gcloud app browse

gcloud app browse


gcloud app browse

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/e1eb4cd0-4fc2-4054-b248-bb9597abdee7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Java deployment with gcloud skips almost all files

[Thomas Becker]

I'm going to have to respectfully disagree with you here. Below is a direct 
copy and paste from the page


https://cloud.google.com/sdk/gcloud/reference/app/deploy


To deploy an App Engine Standard Java service, run: 

  $ gcloud app deploy 
 
~/my_app/WEB-INF/appengine-web.xml


That very clearly refers to Java and not to Python. It tells us to use 
"gcloud app deploy" to deploy a Java App Engine sevice to the App Engine 
Standard environment.
On the other hand, the page

https://cloud.google.com/appengine/docs/standard/java/tools/migrating-from-appcfg-to-gcloud

says

Currently, the gcloud command-line tool does not deploy Java applications 
to production App Engine

I would much appreciate it if you could acknowledge that these two 
statements are in contradiction to each other.

Sincerely,
Thomas Becker

On Saturday, June 16, 2018 at 1:29:30 PM UTC-6, George (Cloud Platform 
Support) wrote:
>
> Hello Thomas, 
>
> There is no contradiction between the two pages you link to, as one page 
> refers to Python apps, the other to Java. 
>
> Your request to not change the default values of options refers to gloud 
> app deploy, a deployment command that is specifically described in 
> documentation as not supported for Java. Your success in using it might be 
> of limited scope, as the same command might not work for another Java 
> application. It is better to follow documentation and deploy Java apps as 
> recommended, namely with Cloud SDK-based Maven, Gradle, Eclipse, or 
> IntelliJ plugins. 
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/1ac8b754-1b30-40af-8868-b04470300195%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Java deployment with gcloud skips almost all files

['George (Cloud Platform Support)' via Google App Engine]

Hello Thomas, 

There is no contradiction between the two pages you link to, as one page 
refers to Python apps, the other to Java. 

Your request to not change the default values of options refers to gloud 
app deploy, a deployment command that is specifically described in 
documentation as not supported for Java. Your success in using it might be 
of limited scope, as the same command might not work for another Java 
application. It is better to follow documentation and deploy Java apps as 
recommended, namely with Cloud SDK-based Maven, Gradle, Eclipse, or 
IntelliJ plugins. 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/1e0b3749-bd10-4497-8ce9-313986c4e393%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Java deployment with gcloud skips almost all files

[Thomas Becker]

After some more research and experimentation, I believe that I solved the 
mystery. So again, on the page

https://cloud.google.com/sdk/gcloud/reference/app/deploy

is says that you can deploy Java services to App Engine standard with 
"gcloud app deploy", and on the page

https://cloud.google.com/appengine/docs/standard/java/tools/migrating-from-appcfg-to-gcloud

it says that you cannot. On the page 

https://cloud.google.com/appengine/docs/standard/java/config/appref

it says that one of the differences between deploying a Java app with 
appcfg and with "gcloud app deploy"
is that the default for making a jar of the class files was "false" under 
appcfg, but has changed to "true"
when using "gcloud app deploy". There was a reason why the default used to 
be "false": the jarring of
the class files changes the class loading order, in a manner that is likely 
to break apps that use web 
frameworks, which is pretty much every app, including mine. So I made 
"gcloud app deploy" use the 
former default behavior by adding

 
 false
 

to my appengine-web.xml . And Bingo, deploying my Java app to App Engine 
Standard with "gcloud app deploy"
now works like a charm.

I would like to respectfully request to not change the default values of 
options. Changing default vaules of options 
is likely to cause a lot of people a lot of pain.

On Friday, June 15, 2018 at 9:40:31 AM UTC-6, Thomas Becker wrote:

> Thanks for the information. As a suggestion, you may want to correct the 
> page
>
> https://cloud.google.com/sdk/gcloud/reference/app/deploy
>
> On that page, in the example section, it says, To deploy an App Engine 
> Standard Java service, run: 
>
>
> $ gcloud app deploy 
>  
> ~/my_app/WEB-INF/appengine-web.xml
>
>
> On Friday, June 15, 2018 at 8:14:37 AM UTC-6, Kenworth (Google Cloud 
> Platform) wrote:
>>
>> Per this article 
>> ,
>>  
>> currently the gcloud command-line tool does not deploy Java applications to 
>> production App Engine. So if you use the Cloud SDK to develop in Java on 
>> App Engine, you must use the Cloud SDK-based Maven 
>>  or 
>> Gradle plugins to deploy applications.
>>
>> mvn appengine:deploy
>>
>>
>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/d17d5a9d-7750-4afe-a9f0-32e1a52bce06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Java deployment with gcloud skips almost all files

[Thomas Becker]

Thanks for the information. As a suggestion, you may want to correct the 
page

https://cloud.google.com/sdk/gcloud/reference/app/deploy

On that page, in the example section, it says, To deploy an App Engine 
Standard Java service, run: 


$ gcloud app deploy  
~/my_app/WEB-INF/appengine-web.xml


On Friday, June 15, 2018 at 8:14:37 AM UTC-6, Kenworth (Google Cloud 
Platform) wrote:
>
> Per this article 
> ,
>  
> currently the gcloud command-line tool does not deploy Java applications to 
> production App Engine. So if you use the Cloud SDK to develop in Java on 
> App Engine, you must use the Cloud SDK-based Maven 
>  or 
> Gradle plugins to deploy applications.
>
> mvn appengine:deploy
>
>
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/73213385-be93-4e0f-83d0-95355f46adfa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.