Node Red wont load again

Damien Murphy

unread,

May 22, 2018, 1:31:11 PM5/22/18

to Node-RED

Hi i had issues with NR not loading last week and its happened again.. I did leave mysql nodes not connected in flows i was rushing out.. But the tab wont load again any help please i have a project due in Monday morning and i really need to work on it. Here is the command window it shows mysql is affecting NR but how can i fix i have tried uninstalling the node i am trying to fix last few it last few hours but time aint on my side.

To find more nodes and example flows - go to http://flows.nodered.org

Starting as a systemd service.

22 May 17:23:54 - [error] [MySQLdatabase:c8a0236a.b3265] Error: connect ETIMEDOUT

22 May 17:24:08 - [error] [mysql:8e8683d9.fbe6d] Database not connected

22 May 17:24:15 - [error] [mysql:685ce8f5.c72d78] Database not connected

22 May 17:24:22 - [error] [mysql:4cc68ad3.fa7804] Database not connected

22 May 17:24:39 - [error] [mysql:8e8683d9.fbe6d] Database not connected

22 May 17:24:47 - [error] [mysql:685ce8f5.c72d78] Database not connected

22 May 17:24:54 - [error] [mysql:4cc68ad3.fa7804] Database not connected

22 May 17:25:07 - [error] [MySQLdatabase:c8a0236a.b3265] Error: connect ETIMEDOUT

22 May 17:25:10 - [error] [mysql:8e8683d9.fbe6d] Database not connected

22 May 17:25:18 - [error] [mysql:685ce8f5.c72d78] Database not connected

22 May 17:25:34 - [error] [mysql:4cc68ad3.fa7804] Database not connected

22 May 17:25:41 - [error] [mysql:8e8683d9.fbe6d] Database not connected

22 May 17:25:58 - [error] [mysql:685ce8f5.c72d78] Database not connected

22 May 17:26:05 - [error] [mysql:4cc68ad3.fa7804] Database not connected

22 May 17:26:08 - [error] [MySQLdatabase:c8a0236a.b3265] Error: connect ETIMEDOUT

22 May 17:26:22 - [error] [mysql:8e8683d9.fbe6d] Database not connected

22 May 17:26:29 - [error] [mysql:685ce8f5.c72d78] Database not connected

22 May 17:26:36 - [error] [mysql:4cc68ad3.fa7804] Database not connected

22 May 17:26:53 - [error] [mysql:8e8683d9.fbe6d] Database not connected

22 May 17:27:00 - [error] [mysql:685ce8f5.c72d78] Database not connected

22 May 17:27:07 - [error] [mysql:4cc68ad3.fa7804] Database not connected

22 May 17:27:21 - [error] [MySQLdatabase:c8a0236a.b3265] Error: connect ETIMEDOUT

22 May 17:27:24 - [error] [mysql:8e8683d9.fbe6d] Database not connected

22 May 17:27:31 - [error] [mysql:685ce8f5.c72d78] Database not connected

22 May 17:27:38 - [error] [mysql:4cc68ad3.fa7804] Database not connected

22 May 17:27:55 - [error] [mysql:8e8683d9.fbe6d] Database not connected

22 May 17:28:02 - [error] [mysql:685ce8f5.c72d78] Database not connected

22 May 17:28:09 - [error] [mysql:4cc68ad3.fa7804] Database not connected

22 May 17:28:22 - [error] [MySQLdatabase:c8a0236a.b3265] Error: connect ETIMEDOUT

steve rickus

unread,

May 22, 2018, 1:48:06 PM5/22/18

to Node-RED

Damien,

Have you uninstalled the mysql config node? Under the upper right menu, select Config Nodes, and look for any unused node. Double click them, select the Delete button, and do a full deploy. Last resort is to restart node-red.

Damien Murphy

unread,

May 22, 2018, 1:49:28 PM5/22/18

to node...@googlegroups.com

I can't get into node red to delete them

--
http://nodered.org

** We're moving this mailing list over to the new Node-RED Forum: https://discourse.nodered.org **

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/967acd36-a3a4-4561-bdcf-89e12f07b5f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Damien Murphy

unread,

May 22, 2018, 2:31:06 PM5/22/18

to Node-RED

I uninstalled it in the command window

steve rickus

unread,

May 22, 2018, 2:52:01 PM5/22/18

to Node-RED

Then what I've had to do in the past is to open the flows.json file in an editor, find the offending node(s), remove those sections (making sure to keep the JSON syntax valid), save it, and restart node-red. Please make a backup of your *.js and *.json file first, of course...

Damien Murphy

unread,

May 22, 2018, 3:00:50 PM5/22/18

to node...@googlegroups.com

Thanks for reply I had my flows backed up.. I had to take the drastic action and wipe everything could not try and fix any longer project due in Monday morning... Thanks again

--
http://nodered.org

** We're moving this mailing list over to the new Node-RED Forum: https://discourse.nodered.org **

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/59fcc9dc-fa6b-4a52-afd0-86ce85e9bb74%40googlegroups.com.

Reply all

Reply to author

Forward