Deploy application :Error Response: [13] Timed out when starting VMs.

292 views
Skip to first unread message

Diego Molteni

unread,
Sep 26, 2016, 10:23:52 AM9/26/16
to Google App Engine
Dear Expert,
I receive this error if i try to deploy my application on Google App Engine (gcloud preview app deploy).
I never had this problem and i can't find a solution.
any Idea on how to fix this problem?

Thanks :)

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Removing intermediate container 14c27f9e927f
Successfully built cd16b300dd47
PUSH
The push refers to a repository [us.gcr.io/fatty-acid/appengine/a2viewer.20160926t090506] (len: 1)
cd16b300dd47: Preparing
cd16b300dd47: Pushing
cd16b300dd47: Pushed
bbcf7801e7ba: Preparing
bbcf7801e7ba: Pushing
bbcf7801e7ba: Pushed
4284f4572084: Preparing
4284f4572084: Pushing
4284f4572084: Pushed
ef62c3a94308: Preparing
ef62c3a94308: Pushing
ef62c3a94308: Pushed
9ff051f37ab2: Image already exists
363507e00b22: Image already exists
818131a74c7c: Image already exists
cc57a274adf5: Image already exists
c7c7a273971f: Image already exists
b21b3e3bc691: Image already exists
latest: digest: sha256:3a014c49ccd20ca9f4060599bf94f0e36a18232bba8907b4db7f20ecd71af9ec size: 33268
DONE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Updating service [a2viewer]...failed.
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).
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Nick (Cloud Platform Support)

unread,
Sep 29, 2016, 7:17:40 PM9/29/16
to Google App Engine
Hey Diego,

The details for why the deploy failed will be located in 'crash.log', 'syslog' or 'stderr' in the Cloud Console Logs Viewer.

You can access these by going to 'Logging' -> 'Logs' -> 'App Engine' -> 'Default service' -> <version>, and then selecting the log type from the dropdown ('Any log level').

Locate the error logs for the timestamp matching the most recent deploy attempt.

If you can't make sense of the logs, feel free to post the error information here and I'll be happy to assist!

Cheers,

Nick
Cloud Platform Community Support
Message has been deleted

Diego Molteni

unread,
Oct 3, 2016, 10:06:51 AM10/3/16
to Google App Engine
HI Nick,
These are the error that I received when i try to upload the application:


08:58:55.000
npm ERR! /app/npm-debug.log
08:58:55.000
npm ERR! Please include the following file with any support request:
08:58:55.000
08:58:55.000
npm ERR! There is likely additional logging output above.
08:58:55.000
npm ERR! npm owner ls a2viewer
08:58:55.000
npm ERR! Or if that isn't available, you can get their info via:
08:58:55.000
npm ERR! npm bugs a2viewer
08:58:55.000
npm ERR! You can get information on how to open an issue for this project with:
08:58:55.000
npm ERR! npm run tsc
08:58:55.000
npm ERR! Tell the author that this fails on your system:
08:58:55.000
npm ERR! not with npm itself.
08:58:55.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:58:55.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:58:55.000
npm ERR! Failed at the a2vi...@1.0.0 prestart script 'npm run tsc'.
08:58:55.000
npm ERR!
08:58:55.000
npm ERR! Exit status 1
08:58:55.000
npm ERR! a2vi...@1.0.0 prestart: `npm run tsc`
08:58:55.000
npm ERR! code ELIFECYCLE
08:58:55.000
npm ERR! npm v3.10.3
08:58:55.000
npm ERR! node v6.7.0
08:58:55.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "start"
08:58:55.000
npm ERR! Linux 3.16.0-4-amd64
08:58:55.000
08:58:55.000
npm ERR! /app/npm-debug.log
08:58:55.000
npm ERR! Please include the following file with any support request:
08:58:55.000
08:58:55.000
npm ERR! There is likely additional logging output above.
08:58:55.000
npm ERR! npm owner ls a2viewer
08:58:55.000
npm ERR! Or if that isn't available, you can get their info via:
08:58:55.000
npm ERR! npm bugs a2viewer
08:58:55.000
npm ERR! You can get information on how to open an issue for this project with:
08:58:55.000
npm ERR! tsc
08:58:55.000
npm ERR! Tell the author that this fails on your system:
08:58:55.000
npm ERR! not with npm itself.
08:58:55.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:58:55.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:58:55.000
npm ERR! Failed at the a2vi...@1.0.0 tsc script 'tsc'.
08:58:55.000
npm ERR!
08:58:55.000
npm ERR! spawn ENOENT
08:58:55.000
npm ERR! a2vi...@1.0.0 tsc: `tsc`
08:58:55.000
npm ERR! syscall spawn
08:58:55.000
npm ERR! errno ENOENT
08:58:55.000
npm ERR! code ELIFECYCLE
08:58:55.000
npm ERR! file sh
08:58:55.000
npm ERR! npm v3.10.3
08:58:55.000
npm ERR! node v6.7.0
08:58:55.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "run" "tsc"
08:58:55.000
npm ERR! Linux 3.16.0-4-amd64
08:58:55.000
08:58:55.000
sh: 1: tsc: not found
08:58:55.000
npm ERR! /app/npm-debug.log
08:58:55.000
npm ERR! Please include the following file with any support request:
08:58:55.000
08:58:55.000
npm ERR! There is likely additional logging output above.
08:58:55.000
npm ERR! npm owner ls a2viewer
08:58:55.000
npm ERR! Or if that isn't available, you can get their info via:
08:58:55.000
npm ERR! npm bugs a2viewer
08:58:55.000
npm ERR! You can get information on how to open an issue for this project with:
08:58:55.000
npm ERR! npm run tsc
08:58:55.000
npm ERR! Tell the author that this fails on your system:
08:58:55.000
npm ERR! not with npm itself.
08:58:55.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:58:55.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:58:55.000
npm ERR! Failed at the a2vi...@1.0.0 prestart script 'npm run tsc'.
08:58:55.000
npm ERR!
08:58:55.000
npm ERR! Exit status 1
08:58:55.000
npm ERR! a2vi...@1.0.0 prestart: `npm run tsc`
08:58:55.000
npm ERR! code ELIFECYCLE
08:58:55.000
npm ERR! npm v3.10.3
08:58:55.000
npm ERR! node v6.7.0
08:58:55.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "start"
08:58:55.000
npm ERR! Linux 3.16.0-4-amd64
08:58:55.000
08:58:55.000
npm ERR! /app/npm-debug.log
08:58:55.000
npm ERR! Please include the following file with any support request:
08:58:55.000
08:58:55.000
npm ERR! There is likely additional logging output above.
08:58:55.000
npm ERR! npm owner ls a2viewer
08:58:55.000
npm ERR! Or if that isn't available, you can get their info via:
08:58:55.000
npm ERR! npm bugs a2viewer
08:58:55.000
npm ERR! You can get information on how to open an issue for this project with:
08:58:55.000
npm ERR! tsc
08:58:55.000
npm ERR! Tell the author that this fails on your system:
08:58:55.000
npm ERR! not with npm itself.
08:58:55.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:58:55.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:58:55.000
npm ERR! Failed at the a2vi...@1.0.0 tsc script 'tsc'.
08:58:55.000
npm ERR!
08:58:55.000
npm ERR! spawn ENOENT
08:58:55.000
npm ERR! a2vi...@1.0.0 tsc: `tsc`
08:58:55.000
npm ERR! syscall spawn
08:58:55.000
npm ERR! errno ENOENT
08:58:55.000
npm ERR! code ELIFECYCLE
08:58:55.000
npm ERR! file sh
08:58:55.000
npm ERR! npm v3.10.3
08:58:55.000
npm ERR! node v6.7.0
08:58:55.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "run" "tsc"
08:58:55.000
npm ERR! Linux 3.16.0-4-amd64
08:58:55.000
08:58:55.000
sh: 1: tsc: not found
08:56:27.000
npm ERR! /app/npm-debug.log
08:56:27.000
npm ERR! Please include the following file with any support request:
08:56:27.000
08:56:27.000
npm ERR! There is likely additional logging output above.
08:56:27.000
npm ERR! npm owner ls a2viewer
08:56:27.000
npm ERR! Or if that isn't available, you can get their info via:
08:56:27.000
npm ERR! npm bugs a2viewer
08:56:27.000
npm ERR! You can get information on how to open an issue for this project with:
08:56:27.000
npm ERR! npm run tsc
08:56:27.000
npm ERR! Tell the author that this fails on your system:
08:56:27.000
npm ERR! not with npm itself.
08:56:27.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:56:27.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:56:27.000
npm ERR! Failed at the a2vi...@1.0.0 prestart script 'npm run tsc'.
08:56:27.000
npm ERR!
08:56:27.000
npm ERR! Exit status 1
08:56:27.000
npm ERR! a2vi...@1.0.0 prestart: `npm run tsc`
08:56:27.000
npm ERR! code ELIFECYCLE
08:56:27.000
npm ERR! npm v3.10.3
08:56:27.000
npm ERR! node v6.7.0
08:56:27.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "start"
08:56:27.000
npm ERR! Linux 3.16.0-4-amd64
08:56:27.000
08:56:27.000
npm ERR! /app/npm-debug.log
08:56:27.000
npm ERR! Please include the following file with any support request:
08:56:27.000
08:56:27.000
npm ERR! There is likely additional logging output above.
08:56:27.000
npm ERR! npm owner ls a2viewer
08:56:27.000
npm ERR! Or if that isn't available, you can get their info via:
08:56:27.000
npm ERR! npm bugs a2viewer
08:56:27.000
npm ERR! You can get information on how to open an issue for this project with:
08:56:27.000
npm ERR! tsc
08:56:27.000
npm ERR! Tell the author that this fails on your system:
08:56:27.000
npm ERR! not with npm itself.
08:56:27.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:56:27.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:56:27.000
npm ERR! Failed at the a2vi...@1.0.0 tsc script 'tsc'.
08:56:27.000
npm ERR!
08:56:27.000
npm ERR! spawn ENOENT
08:56:27.000
npm ERR! a2vi...@1.0.0 tsc: `tsc`
08:56:27.000
npm ERR! syscall spawn
08:56:27.000
npm ERR! errno ENOENT
08:56:27.000
npm ERR! code ELIFECYCLE
08:56:27.000
npm ERR! file sh
08:56:27.000
npm ERR! npm v3.10.3
08:56:27.000
npm ERR! node v6.7.0
08:56:27.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "run" "tsc"
08:56:27.000
npm ERR! Linux 3.16.0-4-amd64
08:56:27.000
08:56:27.000
sh: 1: tsc: not found
08:56:18.000
npm ERR! /app/npm-debug.log
08:56:18.000
npm ERR! Please include the following file with any support request:
08:56:18.000
08:56:18.000
npm ERR! There is likely additional logging output above.
08:56:18.000
npm ERR! npm owner ls a2viewer
08:56:18.000
npm ERR! Or if that isn't available, you can get their info via:
08:56:18.000
npm ERR! npm bugs a2viewer
08:56:18.000
npm ERR! You can get information on how to open an issue for this project with:
08:56:18.000
npm ERR! npm run tsc
08:56:18.000
npm ERR! Tell the author that this fails on your system:
08:56:18.000
npm ERR! not with npm itself.
08:56:18.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:56:18.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:56:18.000
npm ERR! Failed at the a2vi...@1.0.0 prestart script 'npm run tsc'.
08:56:18.000
npm ERR!
08:56:18.000
npm ERR! Exit status 1
08:56:18.000
npm ERR! a2vi...@1.0.0 prestart: `npm run tsc`
08:56:18.000
npm ERR! code ELIFECYCLE
08:56:18.000
npm ERR! npm v3.10.3
08:56:18.000
npm ERR! node v6.7.0
08:56:18.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "start"
08:56:18.000
npm ERR! Linux 3.16.0-4-amd64
08:56:18.000
08:56:18.000
npm ERR! /app/npm-debug.log
08:56:18.000
npm ERR! Please include the following file with any support request:
08:56:18.000
08:56:18.000
npm ERR! There is likely additional logging output above.
08:56:18.000
npm ERR! npm owner ls a2viewer
08:56:18.000
npm ERR! Or if that isn't available, you can get their info via:
08:56:18.000
npm ERR! npm bugs a2viewer
08:56:18.000
npm ERR! You can get information on how to open an issue for this project with:
08:56:18.000
npm ERR! tsc
08:56:18.000
npm ERR! Tell the author that this fails on your system:
08:56:18.000
npm ERR! not with npm itself.
08:56:18.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:56:18.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:56:18.000
npm ERR! Failed at the a2vi...@1.0.0 tsc script 'tsc'.
08:56:18.000
npm ERR!
08:56:18.000
npm ERR! spawn ENOENT
08:56:18.000
npm ERR! a2vi...@1.0.0 tsc: `tsc`
08:56:18.000
npm ERR! syscall spawn
08:56:18.000
npm ERR! errno ENOENT
08:56:18.000
npm ERR! code ELIFECYCLE
08:56:18.000
npm ERR! file sh
08:56:18.000
npm ERR! npm v3.10.3
08:56:18.000
npm ERR! node v6.7.0
08:56:18.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "run" "tsc"
08:56:18.000
npm ERR! Linux 3.16.0-4-amd64
08:56:18.000
08:56:18.000
sh: 1: tsc: not found



Nick (Cloud Platform Support)

unread,
Oct 3, 2016, 3:37:37 PM10/3/16
to Google App Engine
Hey Diego,

It appears from the error that something is failing in the build of your node project. See these lines (I've reversed the order of lines since they were written bottom-to-top in the output you pasted):


npm ERR! Failed at the a2vi...@1.0.0 tsc script 'tsc'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the a2viewer package,

npm ERR! not with npm itself.

So, you should check your Dockerfile and check the version of node.js and npm installed. Another good method of debugging before deployment is to build a container image from the Dockerfile using the docker build command. Then use docker run and see if the container receives requests and processes them properly. Of course if you were using an App Engine standard runtime "compat" base image, the RPC connections to the production APIs would fail, but for a Node JS app, you'll get a more or less perfect approximation of the container in deployment, except for the google infrastructure between your request and the container.

Let me know if you have any further questions!


Cheers,

Nick
Cloud Platform Community Support
Reply all
Reply to author
Forward
0 new messages