Connection fails: Error: connect ETIMEDOUT

s26 commented 8 years ago

Hello,

I am getting following error randomly when I run try to restart my app. Not able to figure out how can I fix it. Can someone please assist me to resolve this error?

Web server listening at: http://0.0.0.0:3000
Browse your REST API at http://0.0.0.0:3000/explorer
Connection fails: Error: connect ETIMEDOUT
It will be retried for the next request.
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: connect ETIMEDOUT
    at PoolConnection.Connection._handleConnectTimeout (/Users/xxx/api/node_modules/loopback-connector-mysql/node_modules/mysql/lib/Connection.js:425:13)
    at Socket.g (events.js:291:16)
    at emitNone (events.js:86:13)
    at Socket.emit (events.js:185:7)
    at Socket._onTimeout (net.js:334:8)
    at tryOnTimeout (timers.js:232:11)
    at Timer.listOnTimeout (timers.js:202:5)
    --------------------
    at Protocol._enqueue (/Users/xxx/api/node_modules/loopback-connector-mysql/node_modules/mysql/lib/protocol/Protocol.js:141:48)
    at Protocol.handshake (/Users/xxx/api/node_modules/loopback-connector-mysql/node_modules/mysql/lib/protocol/Protocol.js:52:41)
    at PoolConnection.connect (/Users/xxx/api/node_modules/loopback-connector-mysql/node_modules/mysql/lib/Connection.js:136:18)
    at Pool.getConnection (/Users/xxx/api/node_modules/loopback-connector-mysql/node_modules/mysql/lib/Pool.js:48:16)
    at MySQL.connect (/Users/xxx/api/node_modules/loopback-connector-mysql/lib/mysql.js:86:17)
    at Object.initializeDataSource [as initialize] (/Users/xxx/api/node_modules/loopback-connector-mysql/lib/mysql.js:40:28)
    at DataSource.setup (/Users/xxx/api/node_modules/loopback-datasource-juggler/lib/datasource.js:339:19)
    at new DataSource (/Users/xxx/api/node_modules/loopback-datasource-juggler/lib/datasource.js:117:8)
    at Registry.createDataSource (/Users/xxx/api/node_modules/loopback/lib/registry.js:355:12)
    at dataSourcesFromConfig (/Users/xxx/api/node_modules/loopback/lib/application.js:440:19)

superkhau commented 7 years ago

Is your MySQL server running?

s26 commented 7 years ago

Yes. My MySql server is running. I am able to start the app successfully, but not all the time. I get this error randomly. 8 out of 10 times I get above error while restarting the app. It is annoying, Sometimes I have to try for 10-15 times to start the app. Everytime I am getting above error.

superkhau commented 7 years ago

@s26 That is the worse case because it should be 100% of the time. It'll make it much harder to reproduce if it's intermittent like that. Can you try scaffolding a new basic LoopBack application to see if it occurs there? I'm thinking it's something else.

ernie58 commented 7 years ago

I have this to lately.

Mostly I have it when I'm starting my application in the morning the first time (when a lot of other processes are starting too), or when I try to start it with the debugger (which is kind a heavy) .

I think it occurs when my vagrant is under heavy load. Is there any way to set a timeout option in my loopback datasource config to see if increasing the timeout helps?

bbito commented 7 years ago

@ernie58 I'm not sure that it solves your problem, but a connectTimeout connection option value can be passed to the underlying mysqljs/mysql module through your Loopback \server\datasources.json configuration file.

connectTimeout: The milliseconds before a timeout occurs during the initial connection to the MySQL server. (Default: 10000)

https://github.com/mysqljs/mysql#connection-options

You would add the option to datasources.json something like this for a 30 second timeout:

{
  "my_mysql_db": {
    "port": 3306,
    "url": "localhost",
    "database": "my_mysql_db",
    "password": "myPassword",
    "name": "my_mysql_db",
    "user": "my_node_mysql_user",
    "connector": "mysql",
    "connectTimeout": 30000
  }
}

superkhau commented 7 years ago

Would you like to submit a PR? You can see the options we pass in at https://github.com/strongloop/loopback-workspace/blob/master/available-connectors.json#L280

bbito commented 7 years ago

@superkhau If the above comment is addressed to me, I'm confused...

I wasn't suggesting a change to the Loopback connector
The datasources.json modification I suggested works as is - that connectTimeout value will pass through to mysqljs/mysql

Connection options beyond those listed in the JSON you linked to _will_ pass through to mysql. I have been using dateStrings for some time and just tested connectTimeout.

superkhau commented 7 years ago

@bbito I thought we wanted to set a default timeout permanently to make it more explicit (ie. the underlying driver's 10000 you mentioned). Anyways, it's all good and thanks for helping out. You are right though, any options you set in datasources.json will be passed down to the driver -- that should solve @s26's issue.

@s26 Can you confirm whether @bbito's solution works for you? Can I close this?