I'm trying to deploy my projet on Google App Engine. It previously worked successfully but since yesterday, I can't deploy it.
I get the following error :
File upload done.
Updating service [default]...failed.
ERROR: (gcloud.app.deploy) Error Response: [13] The system encountered a fatal error
When looking at the log file, I get the following :
2017-02-17 10:15:51,710 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.
2017-02-17 10:15:56,876 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.
2017-02-17 10:16:02,173 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.
2017-02-17 10:16:07,352 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.
2017-02-17 10:16:12,654 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.
2017-02-17 10:16:17,817 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.
2017-02-17 10:16:23,119 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.
2017-02-17 10:16:28,296 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.
2017-02-17 10:16:33,475 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.
2017-02-17 10:16:38,650 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.
2017-02-17 10:16:43,838 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] complete. Result: {
"metadata": {
"target": "apps/my-project/services/default/versions/20170217t100612",
"method": "google.appengine.v1.Versions.CreateVersion",
"user": "user#gmail.com",
"insertTime": "2017-02-17T09:06:34.800Z",
"ephemeralMessage": "Creating new version configuration in service \"20170217t100612\".",
"endTime": "2017-02-17T09:16:43.099Z",
"#type": "type.googleapis.com/google.appengine.v1.OperationMetadataV1"
},
"done": true,
"name": "apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae",
"error": {
"message": "The system encountered a fatal error",
"code": 13
}
}
2017-02-17 10:16:43,838 DEBUG root (gcloud.app.deploy) Error Response: [13] The system encountered a fatal error
Traceback (most recent call last):
File "/opt/google-cloud-sdk/lib/googlecloudsdk/calliope/cli.py", line 742, in Execute
resources = args.calliope_command.Run(cli=self, args=args)
File "/opt/google-cloud-sdk/lib/googlecloudsdk/calliope/backend.py", line 739, in Run
resources = command_instance.Run(args)
File "/opt/google-cloud-sdk/lib/surface/app/deploy.py", line 59, in Run
return deploy_util.RunDeploy(args)
File "/opt/google-cloud-sdk/lib/googlecloudsdk/command_lib/app/deploy_util.py", line 413, in RunDeploy
all_services)
File "/opt/google-cloud-sdk/lib/googlecloudsdk/command_lib/app/deploy_util.py", line 255, in Deploy
endpoints_info)
File "/opt/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/appengine_api_client.py", line 141, in DeployService
operation)
File "/opt/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/operations_util.py", line 142, in WaitForOperation
encoding.MessageToPyValue(completed_operation.error)))
OperationError: Error Response: [13] The system encountered a fatal error
2017-02-17 10:16:43,841 ERROR root (gcloud.app.deploy) Error Response: [13] The system encountered a fatal error
2017-02-17 10:16:44,726 DEBUG root Metrics reporting process started...
There is a lot of similar line like "2017-02-17 10:15:51,710 DEBUG root Operation [apps/my-project/operations/4aced3ef-a018-4913-9a5b-b3f8f13ed4ae] not complete. Waiting 5s.".
When I take a look at the "Activity" tab on the GAE web console, here's what I see :
Sorry it's in French. It's written :
10:16 - Successful operation : create a version of AppEngine
10:06 - Create a version of AppEngine
So I suspect the deployment worked, but took a lot of time to be deployed (10 minutes). Also you can see that it always take 10 minutes to be successfully done, on all my attempts.
What is wrong?
From recent google-cloud-sdk issue 1443 (same symptoms as far as I can tell):
We suspect from the backend logs that the application is actually
deploying successfully but that part that checks if the application is
ready to serve is in fact returning a false negative and thus,
returning the error message you received. It is then stuck in this
inaccurate state. I've added the internal tracking number of that
issue to this report as well.
Can you try issuing requests to that application/service before,
during and after attempting to deploy? The hypothesis is that this
request should provide a positive response to a health check. If this
is received during the troubling deployment, it may trigger the
deployment to returning a positive when checking if the version is
ready to serve.
And the workaround suggestion worked:
As per your request: I issued requests before, during and after
deployment. The deployment was successful. 'gcloud app deploy'
returned normally without any errors reported I tested the GAE app and
indeed the code running in the GAE project is the newly deployed
version.
Related
Running Neo4j Desktop version 1.0.15. Trying to start DB causes the start fail:
Database failed to start:
DB [database-f8950fdd-6b5f-4fea-8c9f-e8457ee1da9a] 'v3.3.1' exited
with status 'KILLED'. Check the logs
Major Log parts are below
2018-02-26 23:03:38.004+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#6411d3c8' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#6411d3c8' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect".
Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory, C:\Users\kiril\AppData\Roaming\Neo4j Desktop\Application\neo4jDatabases\database-f8950fdd-6b5f-4fea-8c9f-e8457ee1da9a\installation-3.3.1\data\databases\graph.db
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.backup.OnlineBackupKernelExtension#c6e0f32' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect".
Suppressed: org.neo4j.kernel.lifecycle.LifecycleException: Exception during graceful attempt to stop partially started component. Please use non suppressed exception to see original component failure.
Caused by: java.io.IOException: Unable to establish loopback connection
It might be your neo4j was still running.
I solved this problem by shutting down the database and restarting it.
Platform: Windows 10;
Neo4j Desktop version: 1.1.13
Open a commend-line window and go to the directory of your neo4j database.
run
bin\neo4j status
to check the status of your database.
If it is running, run
bin\neo4j stop
to shut down your database.
Then go back to the Neo4j Desktop, click the start button, and it could be symptom-free.
I had the same problem and the issue was resolved when I cloned the graph I was connecting. Thereafter, I could connect to the new graph without any problem.
I just finished building my app and I sent a build with no certificate and it worked...now on adding an android certificate, it reports a build error on my codename one dashboard. A help will be appreciated.
FAILURE: Build failed with an exception. * What went wrong: Execution
failed for task '
:transformClassesAndResourcesWithProguardForRelease'. >
java.io.IOException: Please correct the above warnings first.
Warning: Exception while processing task java.io.IOException: Please correct the above warnings first.
:transformClassesAndResourcesWithProguardForRelease FAILED
:transformClassesAndResourcesWithProguardForRelease (Thread[Daemon
worker,5,main]) completed. Took 4.163 secs.
I will need the full error as that point is already too low. I recall seeing some failures when punctuation was used in one of the certificate properties as Android chokes on that. It should appear in the error logs.
I have been trying to deploy a modified docker image on google appengine from the google custom runtimes tutorial but it looks like there are errors that google cloud logs dont seem to show clearly.
Has anyone been able to ever make sense of these logs?
Updating service [default]...|DEBUG: Operation [apps/cobalt-door-118421/operations/c34145bb-3baf-4d1b-8e34-e39f0ec65743] not complete. Waiting 5s.
Updating service [default]...-DEBUG: Operation [apps/cobalt-door-118421/operations/c34145bb-3baf-4d1b-8e34-e39f0ec65743] not complete. Waiting 5s.
Updating service [default]...\DEBUG: Operation [apps/cobalt-door-118421/operations/c34145bb-3baf-4d1b-8e34-e39f0ec65743] not complete. Waiting 5s.
Updating service [default]...|DEBUG: Operation [apps/cobalt-door-118421/operations/c34145bb-3baf-4d1b-8e34-e39f0ec65743] not complete. Waiting 5s.
Updating service [default].../DEBUG: Operation [apps/myprojectid/operations/c34145bb-3baf-4d1b-8e34-e39f0ec65743] complete. Result: {
Updating service [default]...failed.
DEBUG: (gcloud.preview.app.deploy) Error Response: [13] Timed out when starting VMs. It's possible that the application code is unhealthy. (0/2 ready, 2 still deploying).
Traceback (most recent call last):
File "/home/japheth/Downloads/google-cloud-sdk/lib/googlecloudsdk/calliope/cli.py", line 715, in Execute
resources = args.calliope_command.Run(cli=self, args=args)
File "/home/japheth/Downloads/google-cloud-sdk/lib/googlecloudsdk/calliope/backend.py", line 1538, in Run
resources = command_instance.Run(args)
File "/home/japheth/Downloads/google-cloud-sdk/lib/surface/app/deploy.py", line 80, in Run
return deploy_util.RunDeploy(self, args, enable_endpoints=True)
File "/home/japheth/Downloads/google-cloud-sdk/lib/googlecloudsdk/command_lib/app/deploy_util.py", line 378, in RunDeploy
all_services)
File "/home/japheth/Downloads/google-cloud-sdk/lib/googlecloudsdk/command_lib/app/deploy_util.py", line 253, in Deploy
endpoints_info)
File "/home/japheth/Downloads/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/appengine_api_client.py", line 118, in DeployService
return operations.WaitForOperation(self.client.apps_operations, operation)
File "/home/japheth/Downloads/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/api/operations.py", line 70, in WaitForOperation
encoding.MessageToPyValue(completed_operation.error)))
OperationError: Error Response: [13] Timed out when starting VMs. It's possible that the application code is unhealthy. (0/2 ready, 2 still deploying).
ERROR: (gcloud.preview.app.deploy) Error Response: [13] Timed out when starting VMs. It's possible that the application code is unhealthy. (0/2 ready, 2 still deploying).
#WillHayworth The Dockerfile looks like this
#FROM nginx
FROM eu.gcr.io/myprojectid/nginx_september
COPY nginx.conf /etc/nginx/nginx.conf
RUN mkdir -p /var/log/app_engine
RUN mkdir /usr/local/installations
RUN mkdir -p /usr/share/nginx/www/_ah && \
echo "healthy" > /usr/share/nginx/www/_ah/health
ADD www/ /usr/share/nginx/www/
RUN chmod -R a+r /usr/share/nginx/www This is the example from google, notice I have FROM pointing to a custom image which is just the original nginx image but modified with say a command like mkdir /usr/local
Our deployments for the default module of a particular app are failing, seemingly at random, at least 50% of the time, which is constantly disrupting our workflow.
With verbose logging turned on via appcfg.py update app.yaml --verbose, this error appears on the terminal:
03:43 PM Uploaded 4 files and blobs.
03:43 PM Compilation starting.
2015-09-23 15:43:51,886 INFO appcfg.py:1735 Send: /api/appversion/precompile, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
03:43 PM Compilation completed.
03:43 PM Starting deployment.
2015-09-23 15:43:54,215 INFO appcfg.py:1735 Send: /api/appversion/deploy, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
2015-09-23 15:43:56,341 INFO appcfg.py:2601 HTTP Error (HTTP Error 400: Bad Request Unexpected HTTP status 400)
03:43 PM Rolling back the update.
2015-09-23 15:43:56,341 INFO appcfg.py:1735 Send: /api/appversion/rollback, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
Error 400: --- begin server output ---
Client Error (400)
The request is invalid for an unspecified reason.
--- end server output ---
The failure is extremely consistent, in that most of the time we try deploying the module after not having deployed for a few hours, the deployment attempt will fail with the above output.
Then, without changing any app code, retrying the deployment usually succeeds (but at times, the second attempt also fails, requiring subsequent deployment attempts).
This problem started happening earlier this year. Once the problem started occurring, it has not ceased. Before it occurred, we had no no issues with deployments.
The version of the module being deployed has no effect on the rate of deployment success. We are using the Python runtime for this module.
I have already emailed a Solutions Architect from Google about this, but apart from upgrading to a paid support plan to ensure someone looks into this, he suggested I post on here with the hope that the App Engine support team gets back to me.
App Engine support team - can you find out what is going on (and ideally provide a fix)? If you need more information (such as my app ID), please let me know.
I'm getting the below error in my production environment
DEBUG org.apache.camel.processor.DefaultErrorHandler - Failed delivery for exchangeId: ID-*-56874-1372457272212-0-1. On delivery attempt: 0 caught: org.apache.camel.CamelExecutionException: Exception occurred during execution on the exchange: Exchange
DEBUG org.apache.camel.processor.Pipeline - Message exchange has failed: so breaking out of pipeline for exchange: Exchange[***] Handled by the error handler.
Same build with same dependecies is working in 3 of my other environments in LINUX Box. We are using camel-core-2.8.0-fuse and Java 1.6
There were 2 JAR for beans and it was pointing to wrong JAR. After removing the old JAR, error is rectified. Not sure why CAMEL was giving Camel Execution Exception for JAR Issues :(