[google-appengine] Re: AppEngie OUTAGE

[Rob Curtis]

Hi, In the past I've found it's better to report downtime issues on their 
issue tracker. https://issuetracker.google.com/issues/
If you're not already, also subscribe to the downtime notify group 
https://groups.google.com/forum/#!forum/google-appengine-downtime-notify 

Good luck

On Tuesday, October 8, 2019 at 4:47:42 PM UTC+2, Doug Stoddart wrote:
>
> yes, same here for nearly 1hr
>
> On Tuesday, October 8, 2019 at 9:48:59 AM UTC+2, Paolo Conte wrote:
>>
>> Hello,
>> suddently most requests return error 500, log shows "The request failed 
>> because the instance could not start successfully"
>> Project is in europe-west
>>
>> Anyone else?
>>
>

-- 
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/30dedf4b-384c-4332-a903-27f6b6572a8a%40googlegroups.com.

[google-appengine] Are Google App Engine A/AAAA records fixed?

[NP]

Hello,

The process for mapping a custom domain to an app engine project is 
documented here 


The final step is updating your DNS configuration with the records (ip 
addresses) generated by Google. 

My question is - are these records static? Put another way are the values 
always


A   216.239.32.21

A216.239.34.21

A216.239.36.21

A.  216.239.38.21

2001:4860:4802:32::15

   2001:4860:4802:34::15

   2001:4860:4802:36::15

  2001:4860:4802:38::15


for naked domains 


and CNAME.ghs.googlehosted.com. for www (or subdomains)?



I'm asking because if these values are fixed, then I should be able to add 
them to the DNS at the same that I'm adding the values (TXT or CNAME) for 
domain ownership verification. 

-- 
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/a9993678-7ede-465d-aca6-af1c2fbe7f6a%40googlegroups.com.

[google-appengine] Re: Deploy two versions of same app at same time

[Nicholas Swekosky]

Can you please provide more context regarding the project, service, 
version, and instance with respect to the deployment?

On Monday, October 7, 2019 at 7:01:20 AM UTC-5, Mahmmoud Mahdi wrote:
>
> Hello All,
> Is possible to deploy two version of same app at same time using gcloud 
> command
> 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/9ced684f-bddf-4805-8998-f077c20e54d1%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[Doug Stoddart]

yes, same here for nearly 1hr

On Tuesday, October 8, 2019 at 9:48:59 AM UTC+2, Paolo Conte wrote:
>
> Hello,
> suddently most requests return error 500, log shows "The request failed 
> because the instance could not start successfully"
> Project is in europe-west
>
> Anyone else?
>

-- 
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/fd04b1d2-717a-46d3-81fd-a8ca474e1ac0%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[Doug Stoddart]

Still no acknowledgement of this incident from Google
https://status.cloud.google.com/?_ga=2.187839338.-379351283.1560761695

disgraceful behaviour.


On Tuesday, October 8, 2019 at 11:36:11 AM UTC+2, mark negus wrote:
>
> Thanks, thats useful.
> Yes I see a few of these  A problem was encountered with the process that 
> handled this request, causing it to exit. This is likely to cause a new 
> process to be used for the next request to your application. (Error code 
> 121)  
> during warmup calls but just can't get enough started.
>
> Just had 15mins without an error and now they are back again. Sigh.
>
> On Tuesday, October 8, 2019 at 10:17:42 AM UTC+1, Paolo Conte wrote:
>>
>> My settings are below. By looking at the logs of /_ah/warmup to me it 
>> seems that some instances start and some don't, so you need some luck to 
>> get a good amount of working instances
>>
>>
>> F1
>>
>> 
>>
>> 35
>> 35
>>
>> 3
>> 5
>> 500ms
>> 5 
>> 0.9
>> 0.8
>> 
>>
>>
>> On Tuesday, October 8, 2019 at 11:05:13 AM UTC+2, mark negus wrote:
>>>
>>> This app version won't even start at all. What else did you do?
>>> java8, F4
>>>
>>> automatic_scaling:
>>>   min_idle_instances: 3
>>>   max_idle_instances: automatic
>>>   min_pending_latency: automatic
>>>   max_pending_latency: automatic
>>>   max_instances: 4
>>>
>>> On Tuesday, October 8, 2019 at 9:30:26 AM UTC+1, Paolo Conte wrote:

 Manual scaling seems to also have trouble starting instances. For now I 
 kept autoscaling with a high minimum instances number and the error rate 
 is 
 almost zero at the moment 

 On Tuesday, October 8, 2019 at 10:16:57 AM UTC+2, mark negus wrote:
>
> Hi Paolo,
> Let me know how you get on. We were manual scaling for ages as we had 
> terrible issues with auto-scaling a while back. Once it randomly launched 
> 40 instances and burnt through our daily budget in a few hours. Its been 
> ok 
> though this last year.
>
> On Tuesday, October 8, 2019 at 9:10:06 AM UTC+1, Paolo Conte wrote:
>>
>> Thanks Mark. I'm trying to use manual scaling to see if it improves
>>
>> On Tuesday, October 8, 2019 at 10:02:41 AM UTC+2, mark negus wrote:
>>>
>>>
>>> https://status.cloud.google.com/?_ga=2.187839338.-379351283.1560761695
>>>
>>> On Tuesday, October 8, 2019 at 8:57:06 AM UTC+1, mark negus wrote:

 Yes, we are having problems for the last hour in europe-west. 
 Mainly 500s. Looks like the auto-scaling is having issues.

 On Tuesday, October 8, 2019 at 8:48:59 AM UTC+1, Paolo Conte wrote:
>
> Hello,
> suddently most requests return error 500, log shows "The request 
> failed because the instance could not start successfully"
> Project is in europe-west
>
> Anyone else?
>


-- 
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/cd3e91f8-7895-4a9e-8597-dfbb26589225%40googlegroups.com.

[google-appengine] GAE outage in EU

[Doug Stoddart]

Since 9am CEST today we've had huge server problems on GCP - GAE/J in EU.

time out errors
seems to be a problem with instance scaling from that I can see...

any info please?

-- 
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/1f5a4b87-5b93-4bb8-812f-15cf26d7fd11%40googlegroups.com.

[google-appengine] Re: deploy error - token exchange failed

[Laurent Parodi]

Hello,

Thanks for the reply, I'm really lost. 

Granted roles to my user account are:

App Engine Admin

Cloud Build Editor

Owner

Storage Admin


Then, I log on : 

@nuc:~/nodejs-docs-samples/appengine/hello-world/standard$ gcloud auth login

Go to the following link in your browser:



https://accounts.google.com/o/oauth2/auth?code_challenge=rg4Kgf6ucDNPqHSyi3QyicMNO623iRBt4v0wMAMaLM0=select_account_challenge_method=S256_type=offline_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob_type=code_id=32555940559.apps.googleusercontent.com=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcloud-platform+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fappengine.admin+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcompute+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Faccounts.reauth



Enter verification code: 
4/rwFIdCe_S7C63_y0P0tvGV8zK4zJRplLKFXhb0VX9XTVz24KqZsBADg

WARNING: `gcloud auth login` no longer writes application default 
credentials.

If you need to use ADC, see:

  gcloud auth application-default --help


You are now logged in as [xx....@zz.com].

Your current project is [lp-sandbox-254814].  You can change this setting 
by running:

  $ gcloud config set project PROJECT_ID


Then, I run the deploy:


l@nuc:~/nodejs-docs-samples/appengine/hello-world/standard$ gcloud app 
deploy

Services to deploy:


descriptor:  
[/home/l/nodejs-docs-samples/appengine/hello-world/standard/app.yaml]

source:  
[/home/l/nodejs-docs-samples/appengine/hello-world/standard]

target project:  [lp-sandbox-254814]

target service:  [default]

target version:  [20191007t222332]

target url:  [https://lp-sandbox-254814.appspot.com]



Do you want to continue (Y/n)?  y


Beginning deployment of service [default]...

╔╗

╠═ Uploading 0 files to Google Cloud Storage═╣

╚╝

File upload done.

Updating service [default]...failed.

ERROR: (gcloud.app.deploy) Error Response: [9] Cloud build 
bc837367-c520-48f4-a734-a5e86f33aa30 status: FAILURE.

Build error details: 
{"error":{"errorType":"BuildError","canonicalCode":"INVALID_ARGUMENT","errorId":"A815B8B7","errorMessage":"INFO
 
FTL version node-v0.17.0\nINFO Beginning FTL build for node\nINFO   
  FTL arg passed: exposed_ports None\nINFO FTL arg passed: 
cache_repository 
eu.gcr.io/lp-sandbox-254814/app-engine-tmp/build-cache/ttl-7d\nINFO FTL 
arg passed: tar_base_image_path None\nINFO FTL arg passed: 
export_cache_stats False\nINFO FTL arg passed: builder_output_path 
\"\"\nINFO FTL arg passed: name 
eu.gcr.io/lp-sandbox-254814/app-engine-tmp/app/ttl-2h:77c7b674-1333-4cdc-9a6d-5631eca997be\nINFO
 
FTL arg passed: ttl 168\nINFO FTL arg passed: global_cache 
False\nINFO FTL arg passed: cache True\nINFO FTL arg passed: upload 
True\nINFO FTL arg passed: sh_c_prefix False\nINFO FTL arg passed: 
fail_on_error True\nINFO FTL arg passed: base 
eu.gcr.io/gae-runtimes/nodejs10:nodejs10_20190827_10_16_2_RC00\nINFO FTL 
arg passed: output_path None\nINFO FTL arg passed: cache_key_version 
v0.17.0\nINFO FTL arg passed: cache_salt \nINFO FTL arg passed: 
directory /workspace\nINFO FTL arg passed: entrypoint None\nINFO FTL 
arg passed: additional_directory /.gaeconfig\nINFO FTL arg passed: 
destination_path /srv\nINFO FTL arg passed: verbosity NOTSET\nINFO 
starting: 
full build\nINFO starting: builder initialization\nINFO Loading 
Docker credentials for repository 
'eu.gcr.io/gae-runtimes/nodejs10:nodejs10_20190827_10_16_2_RC00'\nINFO 
Loading 
Docker credentials for repository 
'eu.gcr.io/lp-sandbox-254814/app-engine-tmp/app/ttl-2h:77c7b674-1333-4cdc-9a6d-5631eca997be'\nINFO
 
builder initialization took 0 seconds\nINFO starting: build process 
for FTL image\nINFO starting: rm_node_modules\nINFO rm_node_modules 
rm -rf /workspace/node_modules\nINFO `rm_node_modules` stdout:\n\nINFO   
  rm_node_modules took 0 seconds\nINFO using 
descriptor:package-lock.json\nINFO using descriptor:package.json\nINFO   
  starting: checking_cached_packages_json_layer\nDEBUGChecking cache 
for cache_key 
3b92fb27b83299cc2b8917f2ca0220beaabd42233b14dd6f9083dce71babb387\nINFO No 
cached base image found for entry: 
eu.gcr.io/lp-sandbox-254814/app-engine-tmp/build-cache/ttl-7d/node-cache:3b92fb27b83299cc2b8917f2ca0220beaabd42233b14dd6f9083dce71babb387.\nINFO
 
Cache miss on local cache for 
eu.gcr.io/lp-sandbox-254814/app-engine-tmp/build-cache/ttl-7d/node-cache:3b92fb27b83299cc2b8917f2ca0220beaabd42233b14dd6f9083dce71babb387\nINFO
 
No cached dependency layer for 
3b92fb27b83299cc2b8917f2ca0220beaabd42233b14dd6f9083dce71babb387\nINFO 
[CACHE][MISS] 
v0.17.0:NODE-\u003e3b92fb27b83299cc2b8917f2ca0220beaabd42233b14dd6f9083dce71babb387\nINFO
 

[google-appengine] Re: AppEngie OUTAGE

[Doug Stoddart]

yes major problems on EU servers for 49 mins already..

On Tuesday, October 8, 2019 at 9:48:59 AM UTC+2, Paolo Conte wrote:
>
> Hello,
> suddently most requests return error 500, log shows "The request failed 
> because the instance could not start successfully"
> Project is in europe-west
>
> Anyone else?
>

-- 
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/5730db6c-6ce2-41d4-9ffc-3071882128db%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[Paolo Conte]

Looks normal now

On Tuesday, October 8, 2019 at 11:36:11 AM UTC+2, mark negus wrote:
>
> Thanks, thats useful.
> Yes I see a few of these  A problem was encountered with the process that 
> handled this request, causing it to exit. This is likely to cause a new 
> process to be used for the next request to your application. (Error code 
> 121)  
> during warmup calls but just can't get enough started.
>
> Just had 15mins without an error and now they are back again. Sigh.
>
> On Tuesday, October 8, 2019 at 10:17:42 AM UTC+1, Paolo Conte wrote:
>>
>> My settings are below. By looking at the logs of /_ah/warmup to me it 
>> seems that some instances start and some don't, so you need some luck to 
>> get a good amount of working instances
>>
>>
>> F1
>>
>> 
>>
>> 35
>> 35
>>
>> 3
>> 5
>> 500ms
>> 5 
>> 0.9
>> 0.8
>> 
>>
>>
>> On Tuesday, October 8, 2019 at 11:05:13 AM UTC+2, mark negus wrote:
>>>
>>> This app version won't even start at all. What else did you do?
>>> java8, F4
>>>
>>> automatic_scaling:
>>>   min_idle_instances: 3
>>>   max_idle_instances: automatic
>>>   min_pending_latency: automatic
>>>   max_pending_latency: automatic
>>>   max_instances: 4
>>>
>>> On Tuesday, October 8, 2019 at 9:30:26 AM UTC+1, Paolo Conte wrote:

 Manual scaling seems to also have trouble starting instances. For now I 
 kept autoscaling with a high minimum instances number and the error rate 
 is 
 almost zero at the moment 

 On Tuesday, October 8, 2019 at 10:16:57 AM UTC+2, mark negus wrote:
>
> Hi Paolo,
> Let me know how you get on. We were manual scaling for ages as we had 
> terrible issues with auto-scaling a while back. Once it randomly launched 
> 40 instances and burnt through our daily budget in a few hours. Its been 
> ok 
> though this last year.
>
> On Tuesday, October 8, 2019 at 9:10:06 AM UTC+1, Paolo Conte wrote:
>>
>> Thanks Mark. I'm trying to use manual scaling to see if it improves
>>
>> On Tuesday, October 8, 2019 at 10:02:41 AM UTC+2, mark negus wrote:
>>>
>>>
>>> https://status.cloud.google.com/?_ga=2.187839338.-379351283.1560761695
>>>
>>> On Tuesday, October 8, 2019 at 8:57:06 AM UTC+1, mark negus wrote:

 Yes, we are having problems for the last hour in europe-west. 
 Mainly 500s. Looks like the auto-scaling is having issues.

 On Tuesday, October 8, 2019 at 8:48:59 AM UTC+1, Paolo Conte wrote:
>
> Hello,
> suddently most requests return error 500, log shows "The request 
> failed because the instance could not start successfully"
> Project is in europe-west
>
> Anyone else?
>


-- 
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/1a75efa0-0e27-4579-b1a5-3c3bfbaea427%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[mark negus]

Thanks, thats useful.
Yes I see a few of these  A problem was encountered with the process that 
handled this request, causing it to exit. This is likely to cause a new 
process to be used for the next request to your application. (Error code 
121)  
during warmup calls but just can't get enough started.

Just had 15mins without an error and now they are back again. Sigh.

On Tuesday, October 8, 2019 at 10:17:42 AM UTC+1, Paolo Conte wrote:
>
> My settings are below. By looking at the logs of /_ah/warmup to me it 
> seems that some instances start and some don't, so you need some luck to 
> get a good amount of working instances
>
>
> F1
>
> 
>
> 35
> 35
>
> 3
> 5
> 500ms
> 5 
> 0.9
> 0.8
> 
>
>
> On Tuesday, October 8, 2019 at 11:05:13 AM UTC+2, mark negus wrote:
>>
>> This app version won't even start at all. What else did you do?
>> java8, F4
>>
>> automatic_scaling:
>>   min_idle_instances: 3
>>   max_idle_instances: automatic
>>   min_pending_latency: automatic
>>   max_pending_latency: automatic
>>   max_instances: 4
>>
>> On Tuesday, October 8, 2019 at 9:30:26 AM UTC+1, Paolo Conte wrote:
>>>
>>> Manual scaling seems to also have trouble starting instances. For now I 
>>> kept autoscaling with a high minimum instances number and the error rate is 
>>> almost zero at the moment 
>>>
>>> On Tuesday, October 8, 2019 at 10:16:57 AM UTC+2, mark negus wrote:

 Hi Paolo,
 Let me know how you get on. We were manual scaling for ages as we had 
 terrible issues with auto-scaling a while back. Once it randomly launched 
 40 instances and burnt through our daily budget in a few hours. Its been 
 ok 
 though this last year.

 On Tuesday, October 8, 2019 at 9:10:06 AM UTC+1, Paolo Conte wrote:
>
> Thanks Mark. I'm trying to use manual scaling to see if it improves
>
> On Tuesday, October 8, 2019 at 10:02:41 AM UTC+2, mark negus wrote:
>>
>> https://status.cloud.google.com/?_ga=2.187839338.-379351283.1560761695
>>
>> On Tuesday, October 8, 2019 at 8:57:06 AM UTC+1, mark negus wrote:
>>>
>>> Yes, we are having problems for the last hour in europe-west. Mainly 
>>> 500s. Looks like the auto-scaling is having issues.
>>>
>>> On Tuesday, October 8, 2019 at 8:48:59 AM UTC+1, Paolo Conte wrote:

 Hello,
 suddently most requests return error 500, log shows "The request 
 failed because the instance could not start successfully"
 Project is in europe-west

 Anyone else?

>>>

-- 
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/498d0a17-d57c-4039-8878-06db8d5a3d8f%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[Paolo Conte]

My settings are below. By looking at the logs of /_ah/warmup to me it seems 
that some instances start and some don't, so you need some luck to get a 
good amount of working instances


F1



35
35

3
5
500ms
5 
0.9
0.8



On Tuesday, October 8, 2019 at 11:05:13 AM UTC+2, mark negus wrote:
>
> This app version won't even start at all. What else did you do?
> java8, F4
>
> automatic_scaling:
>   min_idle_instances: 3
>   max_idle_instances: automatic
>   min_pending_latency: automatic
>   max_pending_latency: automatic
>   max_instances: 4
>
> On Tuesday, October 8, 2019 at 9:30:26 AM UTC+1, Paolo Conte wrote:
>>
>> Manual scaling seems to also have trouble starting instances. For now I 
>> kept autoscaling with a high minimum instances number and the error rate is 
>> almost zero at the moment 
>>
>> On Tuesday, October 8, 2019 at 10:16:57 AM UTC+2, mark negus wrote:
>>>
>>> Hi Paolo,
>>> Let me know how you get on. We were manual scaling for ages as we had 
>>> terrible issues with auto-scaling a while back. Once it randomly launched 
>>> 40 instances and burnt through our daily budget in a few hours. Its been ok 
>>> though this last year.
>>>
>>> On Tuesday, October 8, 2019 at 9:10:06 AM UTC+1, Paolo Conte wrote:

 Thanks Mark. I'm trying to use manual scaling to see if it improves

 On Tuesday, October 8, 2019 at 10:02:41 AM UTC+2, mark negus wrote:
>
> https://status.cloud.google.com/?_ga=2.187839338.-379351283.1560761695
>
> On Tuesday, October 8, 2019 at 8:57:06 AM UTC+1, mark negus wrote:
>>
>> Yes, we are having problems for the last hour in europe-west. Mainly 
>> 500s. Looks like the auto-scaling is having issues.
>>
>> On Tuesday, October 8, 2019 at 8:48:59 AM UTC+1, Paolo Conte wrote:
>>>
>>> Hello,
>>> suddently most requests return error 500, log shows "The request 
>>> failed because the instance could not start successfully"
>>> Project is in europe-west
>>>
>>> Anyone else?
>>>
>>

-- 
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/eaa9c19d-db3a-478f-a38b-3d4c105055cd%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[mark negus]

This app version won't even start at all. What else did you do?
java8, F4

automatic_scaling:
  min_idle_instances: 3
  max_idle_instances: automatic
  min_pending_latency: automatic
  max_pending_latency: automatic
  max_instances: 4

On Tuesday, October 8, 2019 at 9:30:26 AM UTC+1, Paolo Conte wrote:
>
> Manual scaling seems to also have trouble starting instances. For now I 
> kept autoscaling with a high minimum instances number and the error rate is 
> almost zero at the moment 
>
> On Tuesday, October 8, 2019 at 10:16:57 AM UTC+2, mark negus wrote:
>>
>> Hi Paolo,
>> Let me know how you get on. We were manual scaling for ages as we had 
>> terrible issues with auto-scaling a while back. Once it randomly launched 
>> 40 instances and burnt through our daily budget in a few hours. Its been ok 
>> though this last year.
>>
>> On Tuesday, October 8, 2019 at 9:10:06 AM UTC+1, Paolo Conte wrote:
>>>
>>> Thanks Mark. I'm trying to use manual scaling to see if it improves
>>>
>>> On Tuesday, October 8, 2019 at 10:02:41 AM UTC+2, mark negus wrote:

 https://status.cloud.google.com/?_ga=2.187839338.-379351283.1560761695

 On Tuesday, October 8, 2019 at 8:57:06 AM UTC+1, mark negus wrote:
>
> Yes, we are having problems for the last hour in europe-west. Mainly 
> 500s. Looks like the auto-scaling is having issues.
>
> On Tuesday, October 8, 2019 at 8:48:59 AM UTC+1, Paolo Conte wrote:
>>
>> Hello,
>> suddently most requests return error 500, log shows "The request 
>> failed because the instance could not start successfully"
>> Project is in europe-west
>>
>> Anyone else?
>>
>

-- 
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/5cb15032-82b0-4037-9e9a-1e4388920185%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[Paolo Conte]

Manual scaling seems to also have trouble starting instances. For now I 
kept autoscaling with a high minimum instances number and the error rate is 
almost zero at the moment 

On Tuesday, October 8, 2019 at 10:16:57 AM UTC+2, mark negus wrote:
>
> Hi Paolo,
> Let me know how you get on. We were manual scaling for ages as we had 
> terrible issues with auto-scaling a while back. Once it randomly launched 
> 40 instances and burnt through our daily budget in a few hours. Its been ok 
> though this last year.
>
> On Tuesday, October 8, 2019 at 9:10:06 AM UTC+1, Paolo Conte wrote:
>>
>> Thanks Mark. I'm trying to use manual scaling to see if it improves
>>
>> On Tuesday, October 8, 2019 at 10:02:41 AM UTC+2, mark negus wrote:
>>>
>>> https://status.cloud.google.com/?_ga=2.187839338.-379351283.1560761695
>>>
>>> On Tuesday, October 8, 2019 at 8:57:06 AM UTC+1, mark negus wrote:

 Yes, we are having problems for the last hour in europe-west. Mainly 
 500s. Looks like the auto-scaling is having issues.

 On Tuesday, October 8, 2019 at 8:48:59 AM UTC+1, Paolo Conte wrote:
>
> Hello,
> suddently most requests return error 500, log shows "The request 
> failed because the instance could not start successfully"
> Project is in europe-west
>
> Anyone else?
>


-- 
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/31272cb1-c766-4d4c-a1f2-cd0fc1f5787a%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[mark negus]

Hi Paolo,
Let me know how you get on. We were manual scaling for ages as we had 
terrible issues with auto-scaling a while back. Once it randomly launched 
40 instances and burnt through our daily budget in a few hours. Its been ok 
though this last year.

On Tuesday, October 8, 2019 at 9:10:06 AM UTC+1, Paolo Conte wrote:
>
> Thanks Mark. I'm trying to use manual scaling to see if it improves
>
> On Tuesday, October 8, 2019 at 10:02:41 AM UTC+2, mark negus wrote:
>>
>> https://status.cloud.google.com/?_ga=2.187839338.-379351283.1560761695
>>
>> On Tuesday, October 8, 2019 at 8:57:06 AM UTC+1, mark negus wrote:
>>>
>>> Yes, we are having problems for the last hour in europe-west. Mainly 
>>> 500s. Looks like the auto-scaling is having issues.
>>>
>>> On Tuesday, October 8, 2019 at 8:48:59 AM UTC+1, Paolo Conte wrote:

 Hello,
 suddently most requests return error 500, log shows "The request failed 
 because the instance could not start successfully"
 Project is in europe-west

 Anyone else?

>>>

-- 
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/c92f0dc6-9bed-43bb-9a83-4312bc281819%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[Paolo Conte]

Thanks Mark. I'm trying to use manual scaling to see if it improves

On Tuesday, October 8, 2019 at 10:02:41 AM UTC+2, mark negus wrote:
>
> https://status.cloud.google.com/?_ga=2.187839338.-379351283.1560761695
>
> On Tuesday, October 8, 2019 at 8:57:06 AM UTC+1, mark negus wrote:
>>
>> Yes, we are having problems for the last hour in europe-west. Mainly 
>> 500s. Looks like the auto-scaling is having issues.
>>
>> On Tuesday, October 8, 2019 at 8:48:59 AM UTC+1, Paolo Conte wrote:
>>>
>>> Hello,
>>> suddently most requests return error 500, log shows "The request failed 
>>> because the instance could not start successfully"
>>> Project is in europe-west
>>>
>>> Anyone else?
>>>
>>

-- 
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/63bc0117-1ac1-4fb4-852c-c39685f95ff8%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[mark negus]

https://status.cloud.google.com/?_ga=2.187839338.-379351283.1560761695

On Tuesday, October 8, 2019 at 8:57:06 AM UTC+1, mark negus wrote:
>
> Yes, we are having problems for the last hour in europe-west. Mainly 500s. 
> Looks like the auto-scaling is having issues.
>
> On Tuesday, October 8, 2019 at 8:48:59 AM UTC+1, Paolo Conte wrote:
>>
>> Hello,
>> suddently most requests return error 500, log shows "The request failed 
>> because the instance could not start successfully"
>> Project is in europe-west
>>
>> Anyone else?
>>
>

-- 
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/e5a2e743-10da-4910-bfd3-dd39a7d03fdf%40googlegroups.com.

[google-appengine] Re: AppEngie OUTAGE

[mark negus]

Yes, we are having problems for the last hour in europe-west. Mainly 500s. 
Looks like the auto-scaling is having issues.

On Tuesday, October 8, 2019 at 8:48:59 AM UTC+1, Paolo Conte wrote:
>
> Hello,
> suddently most requests return error 500, log shows "The request failed 
> because the instance could not start successfully"
> Project is in europe-west
>
> Anyone else?
>

-- 
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/a64df96f-f5cb-4c82-b925-878cf26019c9%40googlegroups.com.

[google-appengine] AppEngie OUTAGE

[Paolo Conte]

Hello,
suddently most requests return error 500, log shows "The request failed 
because the instance could not start successfully"
Project is in europe-west

Anyone else?

-- 
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/b72c9e22-e43b-4891-a551-2bb3db946288%40googlegroups.com.