search

node-red / node-red-nodes

Extra nodes for Node-RED
Other
1k stars 595 forks source link

"Error: read ETIMEDOUT" #487

Open JPOyarzunA opened 6 years ago

JPOyarzunA commented 6 years ago

Hi, I've been using node-red-node-mysql for almost a year in a Node-Red instance created as Cloud Foundry app in IBM Cloud. The node worked fine with several MySQL DB from ClearDB. The MySQL ClearDB DB also were generated through IBM Cloud as a service. Since IBM Cloud announced that ClearDB will no longer run as a service, I migrated these DB to new MySQL of ClearDB. Since then I noticed that several data is not been inserted into the DB and usually followed by "Error: read ETIMEDOUT". What does mean? How can I fixed this problem? The Node-Red version is v0.17.5 and the noder-red-node-mysql version is 0.0.17.

dceejay commented 6 years ago

it means it timed out trying to read from the database. you will need to try and work out why that is happening. Is the database online ? Is the network down ? Is the ip address/name resolution working ? Can you reach the database from another client ?

JPOyarzunA commented 6 years ago

Thanks for your reply. The DB is online and I can reach them from another client any time through a data visualization platform. The behaviour seems intermintent. It get connected after several "Error: read ETIMEDOUT", then it insert data to the BD for a while, and then again the connection is lost with the DB (I can see this in the dashboard of the DB). Then the cycle starts over. The problem is during the "Error: read ETIMEDOUT" and until it get connected again I lost data that must be inserted in the DB. In the Node-RED dashboard the state of the node is always OK (with green square). Here is an image where only the debug nodes "Join" and "Debug DB CEQUC" are selected. The debug "Join" node has a correct topic, but the DB node does nothing.

captura de pantalla 2018-09-11 19 46 23

Promise111 commented 2 years ago

Hi, I am assuming you found a solution to this. Can you please share, I'm having the same issues with cleardb on heroku, migrations run and tables are created but queries won't work after that. I find that I can also access the database using mysql workbench, so the db is actually up.