9 Mar 12:38:01 - [info]
Welcome to Node-RED
===================
9 Mar 12:38:01 - [info] Node-RED version: v1.0.4
9 Mar 12:38:01 - [info] Node.js version: v12.16.1
9 Mar 12:38:01 - [info] Linux 4.19.97-v7+ arm LE
9 Mar 12:38:02 - [info] Loading palette nodes
9 Mar 12:38:05 - [info] Dashboard version 2.19.4 started at /ui
9 Mar 12:38:05 - [warn] Missing node modules:
9 Mar 12:38:05 - [warn] - node-red-contrib-bigtimer (2.2.6): bigtimer
9 Mar 12:38:05 - [info] Removing modules from config
9 Mar 12:38:05 - [info] Settings file : /home/pi/.node-red/settings.js
9 Mar 12:38:05 - [info] Context store : 'default' [module=memory]
9 Mar 12:38:05 - [info] User directory : /home/pi/.node-red
9 Mar 12:38:05 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Mar 12:38:05 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
9 Mar 12:38:05 - [info] Creating new flow file
9 Mar 12:38:05 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
9 Mar 12:38:05 - [info] Starting flows
9 Mar 12:38:05 - [info] Started flows
9 Mar 12:38:05 - [info] Server now running at http://127.0.0.1:1880/
free(): invalid pointer
nodered.service: Main process exited, code=killed, status=6/ABRT
nodered.service: Failed with result 'signal'.
nodered.service: Service RestartSec=100ms expired, scheduling restart.
nodered.service: Scheduled restart job, restart counter is at 1.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
9 Mar 12:39:48 - [info]
Welcome to Node-RED
===================
9 Mar 12:39:48 - [info] Node-RED version: v1.0.4
9 Mar 12:39:48 - [info] Node.js version: v12.16.1
9 Mar 12:39:48 - [info] Linux 4.19.97-v7+ arm LE
9 Mar 12:39:50 - [info] Loading palette nodes
free(): invalid pointer
nodered.service: Main process exited, code=killed, status=6/ABRT
nodered.service: Failed with result 'signal'.
nodered.service: Service RestartSec=100ms expired, scheduling restart.
nodered.service: Scheduled restart job, restart counter is at 2.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
9 Mar 12:39:54 - [info]
Welcome to Node-RED
===================
9 Mar 12:39:54 - [info] Node-RED version: v1.0.4
9 Mar 12:39:54 - [info] Node.js version: v12.16.1
9 Mar 12:39:54 - [info] Linux 4.19.97-v7+ arm LE
9 Mar 12:39:55 - [info] Loading palette nodes
9 Mar 12:39:59 - [info] Dashboard version 2.19.4 started at /ui
9 Mar 12:39:59 - [info] Settings file : /home/pi/.node-red/settings.js
9 Mar 12:39:59 - [info] Context store : 'default' [module=memory]
9 Mar 12:39:59 - [info] User directory : /home/pi/.node-red
9 Mar 12:39:59 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Mar 12:39:59 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
9 Mar 12:39:59 - [info] Creating new flow file
9 Mar 12:39:59 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
9 Mar 12:39:59 - [info] Starting flows
9 Mar 12:39:59 - [info] Started flows
9 Mar 12:39:59 - [info] Server now running at http://127.0.0.1:1880/
I've read that big timer could be the culprit, so I uninstalled it using npm, but keeps restarting.
