This repository was archived by the owner on Nov 20, 2025. It is now read-only.
This repository was archived by the owner on Nov 20, 2025. It is now read-only.
Auth error: ETIMEDOUT #283
Description
Copied from original issue: googleapis/nodejs-pubsub#30
@jamesholcomb
January 5, 2018 3:50 AM
Environment details
Note: App is running external from GCP
- OS: Ubuntu 16.04.3 LTS
- Node.js version: 8.9.1
- npm version: 5.5.1
- @google-cloud/pubsub version: 0.14.5
Steps to reproduce
UNKNOWN
Auth error:Error: connect ETIMEDOUT 172.217.4.109:443
Auth error:Error: connect ETIMEDOUT 172.217.4.109:443
Auth error:Error: connect ETIMEDOUT 172.217.4.109:443
Auth error:Error: connect ETIMEDOUT 172.217.4.109:443
Dec 31, 2017 7:05 AM ERROR { message: 'Getting metadata from plugin failed with error: con
nect ETIMEDOUT 172.217.4.109:443',
stack: 'Error: Getting metadata from plugin failed with error: connect ETIMEDOUT 172.217.4.109:44
3\n at ClientDuplexStream.onConnectionStatus (/home/jholcomb/ridealert.server/node_modules/@goog
le-cloud/pubsub/src/connection-pool.js:270:21)\n at emitOne (events.js:116:13)\n at ClientDup
lexStream.emit (events.js:211:7)\n at ClientDuplexStream._emitStatusIfDone (/home/jholcomb/ridea
lert.server/node_modules/grpc/src/node/src/client.js:260:10)\n at ClientDuplexStream._receiveSta
tus (/home/jholcomb/ridealert.server/node_modules/grpc/src/node/src/client.js:233:8)\n at /home/
jholcomb/ridealert.server/node_modules/grpc/src/node/src/client.js:757:12',
code: 16 }
This error occured after the server app had been connected and processing messages for several days. Is it expected that the pubsub lib automatically reconnects (eventually) or does a reconnect in this situation have to be handled by the client?