[google-appengine] Re: GAE deployment throwing Error Response: [13] The system encountered a fatal error

2022-05-27 Thread 'Ernesto Contreras Pinon' via Google App Engine


The solution from the IssueTracker URL you were not able to access is also 
published in this  Stackoverflow 
thread. You can try to check if it helps, but from the new error that you 
have received, it seems this is more of an issue related to the process of 
building your custom runtime on App Engine Flex.

How long is the build process taking? In case it’s more than the default of 
10 minutes, you’d have to set a larger timeout 
,
 
which can be done alternatively with this command: “gcloud config set 
app/cloud_build_timeout ”. Otherwise, doing a fresh build 
without using cached layers, could also help. You can use the “--no-cache” 
flag when running gcloud app deploy 
 to test this 
out. Moreover, have you also seen any difference when allocating additional 
memory and CPU to your App Engine instance?
On Friday, May 27, 2022 at 10:06:55 AM UTC-5 adrian...@gmail.com wrote:

> Hi Ernesto,
>
> Thanks a lot for the response. 
>
> We have already tried the solutions we found online ie. validated billing 
> account is okay, and adding permissions. etc. Specifics are below:
>
>1. Verified almost all other threads
>2. App.yaml has not defined min or max instance...just instances count 
>is defined as 1
>3. Not a transient network errors as we have tried it almost 15-20 
>times  with no network issues
>4. Reg the code changeseven after reverting the code back to what 
>we had in the successful build it's failing
>5. Quotas are still under the limit
>
> *app.yaml:*
> runtime: custom
> env: flex
> resources:
>   cpu: 1
>   memory_gb: 2
>   disk_size_gb: 15
> manual_scaling:
>   instances: 1
> I will send the full logs as well.
>
> One thing we haven't tried is re-associating the App Engine account to the 
> app. However, we can't access this link in your comment. 
> https://issuetracker.google.com/issues/201556420 Would you be able to 
> give me access to view it or screenshots of the resolution if the access is 
> not possible?
>
> Many thanks!
> On Friday, May 27, 2022 at 5:07:30 AM UTC+8 Ernesto Contreras Pinon wrote:
>
>> This error is rather generic and can be caused by multiple factors. Have 
>> you read past issues like this that have possible solutions? In this 
>> sample , the issue was 
>> solved through re-associating the App Engine service account with the app, 
>> for example. On a different occasion, it appears to be caused by transient 
>> network errors , are 
>> you still unable to deploy the version and are seeing the same error?
>>
>> Otherwise, can you give more details about the changes that you added in 
>> the last deployment which failed? Confirming whether all your App Engine 
>> Flex quotas  are under 
>> the limit would also be useful, which you can confirm by searching on 
>> the Cloud Audit logs 
>>  for any 
>> quota exceeded errors.
>> On Thursday, May 26, 2022 at 10:51:53 AM UTC-5 adrian...@gmail.com wrote:
>>
>>> Wondering if anybody here encountered this error when deploying to app 
>>> engine? There are no changes with the app.yml file config and this was 
>>> working before.
>>>
>>> command used: gcloud app deploy --quiet --no-promote 
>>> --no-stop-previous-version --version={VERSION_NUMBER}
>>>
>>> I have submitted an issue here: 
>>> https://issuetracker.google.com/issues/233865148
>>>
>>

-- 
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/6e849165-e23a-4b94-b0c0-856d4a235926n%40googlegroups.com.


[google-appengine] Re: GAE deployment throwing Error Response: [13] The system encountered a fatal error

2022-05-27 Thread Adriana Capua
Hi Ernesto,

Thanks a lot for the response. 

We have already tried the solutions we found online ie. validated billing 
account is okay, and adding permissions. etc. Specifics are below:

   1. Verified almost all other threads
   2. App.yaml has not defined min or max instance...just instances count 
   is defined as 1
   3. Not a transient network errors as we have tried it almost 15-20 
   times  with no network issues
   4. Reg the code changeseven after reverting the code back to what we 
   had in the successful build it's failing
   5. Quotas are still under the limit

*app.yaml:*
runtime: custom
env: flex
resources:
  cpu: 1
  memory_gb: 2
  disk_size_gb: 15
manual_scaling:
  instances: 1
I will send the full logs as well.

One thing we haven't tried is re-associating the App Engine account to the 
app. However, we can't access this link in your comment. 
https://issuetracker.google.com/issues/201556420 Would you be able to give 
me access to view it or screenshots of the resolution if the access is not 
possible?

Many thanks!
On Friday, May 27, 2022 at 5:07:30 AM UTC+8 Ernesto Contreras Pinon wrote:

> This error is rather generic and can be caused by multiple factors. Have 
> you read past issues like this that have possible solutions? In this 
> sample , the issue was 
> solved through re-associating the App Engine service account with the app, 
> for example. On a different occasion, it appears to be caused by transient 
> network errors , are you 
> still unable to deploy the version and are seeing the same error?
>
> Otherwise, can you give more details about the changes that you added in 
> the last deployment which failed? Confirming whether all your App Engine 
> Flex quotas  are under 
> the limit would also be useful, which you can confirm by searching on the 
> Cloud Audit logs 
>  for any 
> quota exceeded errors.
> On Thursday, May 26, 2022 at 10:51:53 AM UTC-5 adrian...@gmail.com wrote:
>
>> Wondering if anybody here encountered this error when deploying to app 
>> engine? There are no changes with the app.yml file config and this was 
>> working before.
>>
>> command used: gcloud app deploy --quiet --no-promote 
>> --no-stop-previous-version --version={VERSION_NUMBER}
>>
>> I have submitted an issue here: 
>> https://issuetracker.google.com/issues/233865148
>>
>

-- 
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/c681576f-4c31-46f3-9152-97d30ebc400bn%40googlegroups.com.


[google-appengine] Re: Error Response: [13] The system encountered a fatal error

2022-05-27 Thread Adriana Capua
Hi, we are currently experiencing this same issue. May I know how this got 
fixed? Would really appreciate a response. Thank you!

btw- we have already submitted a ticket to Google for this but they haven't 
responded back yet.

On Wednesday, January 26, 2022 at 12:37:12 AM UTC+8 babdelrahman wrote:

> Hello, 
>
> Is this is a Flex deployment? 
> Were there any Org policy changes ?
>
> Document [1] : 
>
> You cannot use the App Engine flexible environment if the organization 
> policy 
>  
> on 
> your project restricts access to external IPs 
> ,
>  
> for example:
>
>- The effective policy for constraints/compute.vmExternalIpAccess is 
>set to DENY_ALL.
>- The effective policy for constraints/compute.vmExternalIpAccess is 
>set to allow only specific VM instances.
>
> Please check the Organization policy for your project, following steps in 
> [1].
>
> [1] https://cloud.google.com/appengine/docs/flexible/known-issues
> [2] 
> https://cloud.google.com/resource-manager/docs/organization-policy/using-constraints#override_boolean_policy
> On Tuesday, January 25, 2022 at 10:05:15 AM UTC-5 jose...@gmail.com wrote:
>
>> Hi App Engine Team,
>>
>>
>> We have been using App Engine normally and just this weekend start to 
>> fail the update. 
>>
>> We update from a Docker container, so there is no cloud build and the 
>> app.yaml file has not changed.
>>
>> After reviewing some suggestions online, we have tried:
>>
>>- Updating the gcloud SDK
>>- Removing old versions in the App Engine console
>>- Validating the docker container into a VM in GCloud
>>- Run this quickstart 
>> 
>>in the same project
>>
>> The problem is that the error is very generic. Do you have any 
>> suggestions?
>>
>>
>> Updating service [default] (this may take several minutes)...-DEBUG: 
>> Operation [apps/-/operations/7162ec80-93f3-4f4e-b555-2ad82e76e90a] not 
>> complete. Waiting to retry.
>> Updating service [default] (this may take several minutes)...|DEBUG: 
>> Operation [apps/-/operations/7162ec80-93f3-4f4e-b555-2ad82e76e90a] 
>> complete. Result: 
>> {
>> "done": true,
>> "error": {
>> "code": 13,
>> "message": "The system encountered a fatal error"
>> },
>> "metadata": {
>> "@type": "
>> type.googleapis.com/google.appengine.v1.OperationMetadataV1",
>> "endTime": "2022-01-25T13:24:24.274Z",
>> "insertTime": "2022-01-25T12:58:17.876Z",
>> "method": "google.appengine.v1.Versions.CreateVersion",
>> "target": "apps/-/services/default/versions/20220125t135813",
>> "user": "@gmail.com"
>> },
>> "name": "apps/-/operations/7162ec80-93f3-4f4e-b555-2ad82e76e90a"
>> }
>> Updating service [default] (this may take several minutes)...failed.
>> DEBUG: (gcloud.app.deploy) Error Response: [13] The system encountered a 
>> fatal error
>> Traceback (most recent call last):
>>   File "D:\Program Files (x86)\Google\Cloud 
>> SDK\google-cloud-sdk\lib\googlecloudsdk\calliope\cli.py", line 987, in 
>> Execute
>> resources = calliope_command.Run(cli=self, args=args)
>>   File "D:\Program Files (x86)\Google\Cloud 
>> SDK\google-cloud-sdk\lib\googlecloudsdk\calliope\backend.py", line 809, in 
>> Run
>> resources = command_instance.Run(args)
>>   File "D:\Program Files (x86)\Google\Cloud 
>> SDK\google-cloud-sdk\lib\surface\app\deploy.py", line 123, in Run
>> return deploy_util.RunDeploy(
>>   File "D:\Program Files (x86)\Google\Cloud 
>> SDK\google-cloud-sdk\lib\googlecloudsdk\command_lib\app\deploy_util.py", 
>> line 680, in RunDeploy
>> deployer.Deploy(
>>   File "D:\Program Files (x86)\Google\Cloud 
>> SDK\google-cloud-sdk\lib\googlecloudsdk\command_lib\app\deploy_util.py", 
>> line 461, in Deploy
>> self.api_client.DeployService(new_version.service, new_version.id,
>>   File "D:\Program Files (x86)\Google\Cloud 
>> SDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\app\appengine_api_client.py",
>>  
>> line 216, in DeployService
>> return operations_util.WaitForOperation(
>>   File "D:\Program Files (x86)\Google\Cloud 
>> SDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\app\operations_util.py", 
>> line 307, in WaitForOperation
>> completed_operation = waiter.WaitFor(
>>   File "D:\Program Files (x86)\Google\Cloud 
>> SDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\util\waiter.py", line 261, 
>> in WaitFor
>> operation = PollUntilDone(
>>   File "D:\Program Files (x86)\Google\Cloud 
>> SDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\util\waiter.py", line 322, 
>> in PollUntilDone
>> operation = retryer.RetryOnResult(
>>   File "D:\Program Files (x86)\Google\Cloud 
>> SDK\google-cloud-sdk\lib\googlecloudsdk\core\util\retry.py", 

[google-appengine] Re: GAE deployment throwing Error Response: [13] The system encountered a fatal error

2022-05-27 Thread Adriana Capua
Here's the part of the logs. Also, the weird thing is we are getting 
different error messages. Last time we were getting the error "[13] The 
system encountered a fatal error" and sometimes "[14] Cloud Container build 
either failed or interrupted.". For this instance when I tried to do a 
deployment again, it's the error 14 again.
On Friday, May 27, 2022 at 5:07:30 AM UTC+8 Ernesto Contreras Pinon wrote:

> This error is rather generic and can be caused by multiple factors. Have 
> you read past issues like this that have possible solutions? In this 
> sample , the issue was 
> solved through re-associating the App Engine service account with the app, 
> for example. On a different occasion, it appears to be caused by transient 
> network errors , are you 
> still unable to deploy the version and are seeing the same error?
>
> Otherwise, can you give more details about the changes that you added in 
> the last deployment which failed? Confirming whether all your App Engine 
> Flex quotas  are under 
> the limit would also be useful, which you can confirm by searching on the 
> Cloud Audit logs 
>  for any 
> quota exceeded errors.
> On Thursday, May 26, 2022 at 10:51:53 AM UTC-5 adrian...@gmail.com wrote:
>
>> Wondering if anybody here encountered this error when deploying to app 
>> engine? There are no changes with the app.yml file config and this was 
>> working before.
>>
>> command used: gcloud app deploy --quiet --no-promote 
>> --no-stop-previous-version --version={VERSION_NUMBER}
>>
>> I have submitted an issue here: 
>> https://issuetracker.google.com/issues/233865148
>>
>

-- 
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/91a45347-5d36-4505-8b7f-79875d937810n%40googlegroups.com.
Step #1: ?  (Server)  server-side renders at runtime (uses getInitialProps or 
getServerSideProps)
Step #1: ?  (Static)  automatically rendered as static HTML (uses no initial 
props)
Step #1: ?  (SSG) automatically generated as static HTML + JSON (uses 
getStaticProps)
Step #1:(ISR) incremental static regeneration (uses revalidate in 
getStaticProps)
Step #1:
Step #1: Done in 1474.55s.
DEBUG: https://storage.googleapis.com:443 "GET 
/staging.{PROJECT_ID}.appspot.com/log-6a4fedba-d61a-4816-874e-98b24f8884a7.txt 
HTTP/1.1" 416 168
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: https://storage.googleapis.com:443 "GET 
/staging.{PROJECT_ID}.appspot.com/log-6a4fedba-d61a-4816-874e-98b24f8884a7.txt 
HTTP/1.1" 416 168
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: https://storage.googleapis.com:443 "GET 
/staging.{PROJECT_ID}.appspot.com/log-6a4fedba-d61a-4816-874e-98b24f8884a7.txt 
HTTP/1.1" 416 168
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: https://storage.googleapis.com:443 "GET 
/staging.{PROJECT_ID}.appspot.com/log-6a4fedba-d61a-4816-874e-98b24f8884a7.txt 
HTTP/1.1" 416 168
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: https://storage.googleapis.com:443 "GET 
/staging.{PROJECT_ID}.appspot.com/log-6a4fedba-d61a-4816-874e-98b24f8884a7.txt 
HTTP/1.1" 416 168
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: https://storage.googleapis.com:443 "GET 
/staging.{PROJECT_ID}.appspot.com/log-6a4fedba-d61a-4816-874e-98b24f8884a7.txt 
HTTP/1.1" 416 168
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: https://storage.googleapis.com:443 "GET 
/staging.{PROJECT_ID}.appspot.com/log-6a4fedba-d61a-4816-874e-98b24f8884a7.txt 
HTTP/1.1" 416 168
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: https://storage.googleapis.com:443 "GET 
/staging.{PROJECT_ID}.appspot.com/log-6a4fedba-d61a-4816-874e-98b24f8884a7.txt 
HTTP/1.1" 416 168
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: https://storage.googleapis.com:443 "GET 
/staging.{PROJECT_ID}.appspot.com/log-6a4fedba-d61a-4816-874e-98b24f8884a7.txt 
HTTP/1.1" 416 168
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: https://storage.googleapis.com:443 "GET 
/staging.{PROJECT_ID}.appspot.com/log-6a4fedba-d61a-4816-874e-98b24f8884a7.txt 
HTTP/1.1" 206 561
DEBUG: Reading GCS logfile: 206 (read 561 bytes)
Step #1: Removing intermediate container a54ced4dff06
Step #1:  ---> 5695c63c8a99
Step #1: Step 50/51 : EXPOSE 8080
Step #1:  ---> Running in f242da7d775b
Step #1: Removing intermediate container f242da7d775b
Step #1:  ---> 573718eac234
Step #1: Step 51/51 : CMD [ "yarn", "start:prod" ]
Step #1:  --->