Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error [13] Timed out when starting VMs #69

Closed
otymartin opened this issue Feb 26, 2016 · 5 comments
Closed

Error [13] Timed out when starting VMs #69

otymartin opened this issue Feb 26, 2016 · 5 comments
Labels
🚨 This issue needs some love. triage me I really want to be triaged.

Comments

@otymartin
Copy link

I've made several attempts to deploy on app engine and i can't get passed this error.

Beginning teardown of remote build environment (this may take a few seconds). Updating module [default]...|Deleted [https://www.googleapis.com/compute/v1/projects/##################]. Updating module [default]...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). My-MacBook-Pro-2:appName-server myMacName$

Typing the above URL into the browser I get this
[{ "error": { "errors": [ { "domain": "global", "reason": "required", "message": "Login Required", "locationType": "header", "location": "Authorization" } ], "code": 401, "message": "Login Required" } }]

@otymartin
Copy link
Author

Fyi when I created my project in google cloud, I specified "USEast" but when I was deploying, I noticied the URL had us-central1-f

@jmdobry
Copy link
Member

jmdobry commented Feb 26, 2016

What are you trying to deploy?

@otymartin
Copy link
Author

@jmdobry Im trying to deploy the Parse-server using this tutorial

@jmdobry
Copy link
Member

jmdobry commented Feb 26, 2016

From the error message, it looks like the app deployed but failed to start. Have you set the required environment variables in app.yaml?

You can go to the Logging view in the Developers Console to see error stack traces that were printed.

@otymartin
Copy link
Author

@jmdobry Hey thanks you were right. My cloud code destination was misplaced I fixed it

cloud: __dirname + '/cloud/main.js',

@jmdobry jmdobry closed this as completed Feb 27, 2016
sethbergman pushed a commit to stackriot/nodejs-docs-samples that referenced this issue Jun 4, 2017
* Upgrade dependencies

* Fix key.
@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Apr 6, 2020
telpirion pushed a commit that referenced this issue Nov 9, 2022
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
gcf-merge-on-green bot pushed a commit that referenced this issue Nov 9, 2022
…nter-insights (#2817)

- feat: initial generation of templated files
- feat: add initial samples (#2)
- chore(deps): update dependency mocha to v9 (#3)
- chore: release 1.0.0 (#1)
- chore: release 1.0.1 (#12)
- chore: release 1.0.2 (#18)
- chore: release 1.1.0 (#21)
- chore: release 1.2.0 (#26)
- chore: release 1.2.1 (#29)
- chore: release 1.3.0 (#36)
- chore: release 1.4.0 (#40)
- samples: get operation (#52)
- samples: create conversation, create analysis, export data to BigQuery (#34)
- samples: enable pubsub notifications (#48)
- samples: modify TTL in create conversation with TTL sample (#57)
- samples: create topic model (#49)
- chore: release 1.5.0 (#58)
- samples: set project-level TTL (#51)
- samples: create custom highlights (#53)
- chore: release 1.6.0 (#65)
- chore: release 1.7.0 (#69)
- chore: release 1.8.0 (#75)
- chore: release 1.9.0 (#81)
- chore(main): release 1.11.0 (#107)
- build: add retries for flaky test (#109)
- build!: update library to use Node 12 (#122)
- chore(main): release 2.0.0 (#124)
- fix(deps): update dependency @google-cloud/bigquery to v6 (#127)
- fix(deps): update dependency @google-cloud/pubsub to v3 (#126)
- chore(main): release 2.0.1 (#129)
- chore(main): release 2.1.0 (#134)
- chore(main): release 2.1.1 (#139)
- chore(deps): update dependency uuid to v9 (#142)
ace-n pushed a commit that referenced this issue Nov 10, 2022
rogerthatdev pushed a commit that referenced this issue Nov 10, 2022
ace-n pushed a commit that referenced this issue Nov 10, 2022
rogerthatdev pushed a commit that referenced this issue Nov 11, 2022
NimJay pushed a commit that referenced this issue Nov 11, 2022
ace-n pushed a commit that referenced this issue Nov 11, 2022
ace-n pushed a commit that referenced this issue Nov 14, 2022
ace-n pushed a commit that referenced this issue Nov 14, 2022
ace-n pushed a commit that referenced this issue Nov 14, 2022
ace-n pushed a commit that referenced this issue Nov 14, 2022
ace-n pushed a commit that referenced this issue Nov 15, 2022
ace-n pushed a commit that referenced this issue Nov 17, 2022
kweinmeister pushed a commit that referenced this issue Nov 18, 2022
* chore: ignore package-log.json

* remove locky

* renovateeee
pattishin pushed a commit that referenced this issue Nov 18, 2022
* fix: reduced image size due to new file size limit (1.5 MB)
* fix: more file sizing
ace-n pushed a commit that referenced this issue Nov 21, 2022
ace-n pushed a commit that referenced this issue Nov 21, 2022
pattishin pushed a commit that referenced this issue Nov 22, 2022
* fix: reduced image size due to new file size limit (1.5 MB)
* fix: more file sizing
jsimonweb pushed a commit to jsimonweb/nodejs-docs-samples that referenced this issue Dec 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚨 This issue needs some love. triage me I really want to be triaged.
Projects
None yet
Development

No branches or pull requests

3 participants