Having trouble installing - Google Cloud SDK - Help!

Hello, I have been trying to install Google Cloud SDK and have run into some issues that I cannot seem to rectify. I have placed the list of operations below and their outcome to help with the explanation.

Steps 1,2 & 3. run successfully

Step 4. Clone this repo: git clone https://github.com/kwnevarez/particle-device-locator

  • fatal: destination path β€˜particle-device-locator’ already exists and is not an empty directory.

Step 5. Ran successful

Step 6. Run the sample with npm: npm start

  • This is where it goes awry…

Step 7. Visit the application at http://localhost:8080.

  • page fails to open page.

I have researched the web for solutions for a few days but am not getting any resolution. Does anyone have an idea how to fix this mess?

Thank you,

You should change the Thread-category from β€˜Tutorials’ to β€˜Troubleshooting’. It seems more for an technical issue. I suggest that you should describe your context more in detail and put in screenshots. Good luck.

Hello @Postler many thanks for the recommendation. I will definitely do that. I’ve got a lot to learn here!

You probably need to cd into the particle-device-locator directory. It looks like you’re at the top level of your home directory, you have to issue the npm start in the top level of the downloaded repository where package.json is.

HI @rickkas7, I think the file is in the home directory of zeytin though. Is this not correct? Below I have placed the files under that directory. It may be a mess because I’ve been a lot of strange stuff from various other forums.

@ScruffR do you have experience here or know someone who does?

@Clifton, I agree with @rickkas7 that you need to cd to the particle-device-locator directory and then run npm install and npm start. The file in the home directory is not the correct one.

2 Likes

Hi @peekay123 and @rickkas7 ,

Ok so I have cd to the correct folder and have successfully (I believe) installed the package. I do run into some problems when I run npm start. I have placed the terminal info below. What do you guys think and thank you again for your patience.

cliftons-brain:~ Zeytin$ npm install
cliftons-brain:~ Zeytin$ npm start
npm ERR! Darwin 16.6.0
npm ERR! argv β€œ/usr/local/bin/node” β€œ/usr/local/bin/npm” "start"
npm ERR! node v6.11.1
npm ERR! npm v3.10.10

npm ERR! missing script: start
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! /Users/Zeytin/npm-debug.log
cliftons-brain:~ Zeytin$ cd users/Zeytin/particle-device-locator
-bash: cd: users/Zeytin/particle-device-locator: No such file or directory
cliftons-brain:~ Zeytin$ cd particle-device-locator/
cliftons-brain:particle-device-locator Zeytin$ npm install
npm WARN excluding symbolic link test/server/static/ie8-polyfill.js -> …/…/…/ie8-polyfill.js
npm WARN excluding symbolic link test/server/static/ie8-polyfill.js -> …/…/…/ie8-polyfill.js
Locator@0.1.0 /Users/Zeytin/particle-device-locator
β”œβ”€β”¬ body-parser@1.17.2
β”‚ β”œβ”€β”€ bytes@2.4.0
β”‚ β”œβ”€β”€ content-type@1.0.2
β”‚ β”œβ”€β”¬ debug@2.6.7
β”‚ β”‚ └── ms@2.0.0
β”‚ β”œβ”€β”€ depd@1.1.1
β”‚ β”œβ”€β”¬ http-errors@1.6.1
β”‚ β”‚ β”œβ”€β”€ depd@1.1.0
β”‚ β”‚ └── inherits@2.0.3
β”‚ β”œβ”€β”€ iconv-lite@0.4.15
β”‚ β”œβ”€β”¬ on-finished@2.3.0
β”‚ β”‚ └── ee-first@1.1.1
β”‚ β”œβ”€β”€ qs@6.4.0
β”‚ β”œβ”€β”¬ raw-body@2.2.0
β”‚ β”‚ └── unpipe@1.0.0
β”‚ └─┬ type-is@1.6.15
β”‚ └── media-typer@0.3.0
β”œβ”€β”€ ejs@2.5.7
β”œβ”€β”¬ express@4.15.3
β”‚ β”œβ”€β”¬ accepts@1.3.3
β”‚ β”‚ └── negotiator@0.6.1
β”‚ β”œβ”€β”€ array-flatten@1.1.1
β”‚ β”œβ”€β”€ content-disposition@0.5.2
β”‚ β”œβ”€β”€ cookie@0.3.1
β”‚ β”œβ”€β”€ cookie-signature@1.0.6
β”‚ β”œβ”€β”€ encodeurl@1.0.1
β”‚ β”œβ”€β”€ escape-html@1.0.3
β”‚ β”œβ”€β”€ etag@1.8.0
β”‚ β”œβ”€β”€ finalhandler@1.0.3
β”‚ β”œβ”€β”€ fresh@0.5.0
β”‚ β”œβ”€β”€ merge-descriptors@1.0.1
β”‚ β”œβ”€β”€ methods@1.1.2
β”‚ β”œβ”€β”€ parseurl@1.3.1
β”‚ β”œβ”€β”€ path-to-regexp@0.1.7
β”‚ β”œβ”€β”¬ proxy-addr@1.1.5
β”‚ β”‚ β”œβ”€β”€ forwarded@0.1.0
β”‚ β”‚ └── ipaddr.js@1.4.0
β”‚ β”œβ”€β”€ range-parser@1.2.0
β”‚ β”œβ”€β”¬ send@0.15.3
β”‚ β”‚ β”œβ”€β”€ destroy@1.0.4
β”‚ β”‚ └── mime@1.3.4
β”‚ β”œβ”€β”€ serve-static@1.12.3
β”‚ β”œβ”€β”€ setprototypeof@1.0.3
β”‚ β”œβ”€β”€ statuses@1.3.1
β”‚ β”œβ”€β”€ utils-merge@1.0.0
β”‚ └── vary@1.1.1
β”œβ”€β”¬ express-session@1.15.4
β”‚ β”œβ”€β”€ crc@3.4.4
β”‚ β”œβ”€β”€ debug@2.6.8
β”‚ β”œβ”€β”€ on-headers@1.0.1
β”‚ └─┬ uid-safe@2.1.4
β”‚ └── random-bytes@1.0.0
β”œβ”€β”¬ express-ws@3.0.0
β”‚ └─┬ ws@2.3.1
β”‚ └── ultron@1.1.0
β”œβ”€β”¬ particle-api-js@6.5.0
β”‚ β”œβ”€β”¬ babel-runtime@6.25.0
β”‚ β”‚ β”œβ”€β”€ core-js@2.4.1
β”‚ β”‚ └── regenerator-runtime@0.10.5
β”‚ β”œβ”€β”¬ form-data@1.0.0-rc4
β”‚ β”‚ └── async@1.5.2
β”‚ β”œβ”€β”¬ stream-http@2.2.1
β”‚ β”‚ β”œβ”€β”€ builtin-status-codes@2.0.0
β”‚ β”‚ β”œβ”€β”€ to-arraybuffer@1.0.1
β”‚ β”‚ └── xtend@4.0.1
β”‚ β”œβ”€β”¬ superagent@2.3.0
β”‚ β”‚ β”œβ”€β”€ component-emitter@1.2.1
β”‚ β”‚ β”œβ”€β”€ cookiejar@2.1.1
β”‚ β”‚ β”œβ”€β”€ formidable@1.1.1
β”‚ β”‚ └─┬ readable-stream@2.3.3
β”‚ β”‚ β”œβ”€β”€ core-util-is@1.0.2
β”‚ β”‚ β”œβ”€β”€ isarray@1.0.0
β”‚ β”‚ β”œβ”€β”€ process-nextick-args@1.0.7
β”‚ β”‚ β”œβ”€β”€ safe-buffer@5.1.1
β”‚ β”‚ β”œβ”€β”¬ string_decoder@1.0.3
β”‚ β”‚ β”‚ └── safe-buffer@5.1.1
β”‚ β”‚ └── util-deprecate@1.0.2
β”‚ └── superagent-prefix@0.0.2
└─┬ request@2.81.0
β”œβ”€β”€ aws-sign2@0.6.0
β”œβ”€β”€ aws4@1.6.0
β”œβ”€β”€ caseless@0.12.0
β”œβ”€β”¬ combined-stream@1.0.5
β”‚ └── delayed-stream@1.0.0
β”œβ”€β”€ extend@3.0.1
β”œβ”€β”€ forever-agent@0.6.1
β”œβ”€β”¬ form-data@2.1.4
β”‚ └── asynckit@0.4.0
β”œβ”€β”¬ har-validator@4.2.1
β”‚ β”œβ”€β”¬ ajv@4.11.8
β”‚ β”‚ β”œβ”€β”€ co@4.6.0
β”‚ β”‚ └─┬ json-stable-stringify@1.0.1
β”‚ β”‚ └── jsonify@0.0.0
β”‚ └── har-schema@1.0.5
β”œβ”€β”¬ hawk@3.1.3
β”‚ β”œβ”€β”€ boom@2.10.1
β”‚ β”œβ”€β”€ cryptiles@2.0.5
β”‚ β”œβ”€β”€ hoek@2.16.3
β”‚ └── sntp@1.0.9
β”œβ”€β”¬ http-signature@1.1.1
β”‚ β”œβ”€β”€ assert-plus@0.2.0
β”‚ β”œβ”€β”¬ jsprim@1.4.0
β”‚ β”‚ β”œβ”€β”€ assert-plus@1.0.0
β”‚ β”‚ β”œβ”€β”€ extsprintf@1.0.2
β”‚ β”‚ β”œβ”€β”€ json-schema@0.2.3
β”‚ β”‚ └── verror@1.3.6
β”‚ └─┬ sshpk@1.13.1
β”‚ β”œβ”€β”€ asn1@0.2.3
β”‚ β”œβ”€β”€ assert-plus@1.0.0
β”‚ β”œβ”€β”€ bcrypt-pbkdf@1.0.1
β”‚ β”œβ”€β”¬ dashdash@1.14.1
β”‚ β”‚ └── assert-plus@1.0.0
β”‚ β”œβ”€β”€ ecc-jsbn@0.1.1
β”‚ β”œβ”€β”¬ getpass@0.1.7
β”‚ β”‚ └── assert-plus@1.0.0
β”‚ β”œβ”€β”€ jsbn@0.1.1
β”‚ └── tweetnacl@0.14.5
β”œβ”€β”€ is-typedarray@1.0.0
β”œβ”€β”€ isstream@0.1.2
β”œβ”€β”€ json-stringify-safe@5.0.1
β”œβ”€β”¬ mime-types@2.1.16
β”‚ └── mime-db@1.29.0
β”œβ”€β”€ oauth-sign@0.8.2
β”œβ”€β”€ performance-now@0.2.0
β”œβ”€β”€ safe-buffer@5.0.1
β”œβ”€β”€ stringstream@0.0.5
β”œβ”€β”¬ tough-cookie@2.3.2
β”‚ └── punycode@1.4.1
β”œβ”€β”€ tunnel-agent@0.6.0
└── uuid@3.1.0

cliftons-brain:particle-device-locator Zeytin$ npm start

Locator@0.1.0 start /Users/Zeytin/particle-device-locator
node app.js

Websocket server listening on port 50051
App listening on port 8080
Press Ctrl+C to quit.
Logging in
Logging in
logged in. Getting event stream
Got event stream.
Error while talking to metadata server, assuming localhost
External IP: localhost