npm and node_index.js high CPU load

[Joulinar]

that's all? looks like it is not starting correctly. can you do a reboot and check again

[novitibo]

no, i did't paste everything
Jan 25 23:02:53 DietPi systemd[1]: Started Node-RED (DietPi).
Jan 25 23:03:05 DietPi node-red[1266]: 25 Jan 23:03:05 - [info]
Jan 25 23:03:05 DietPi node-red[1266]: Welcome to Node-RED
Jan 25 23:03:05 DietPi node-red[1266]: ===================
Jan 25 23:03:05 DietPi node-red[1266]: 25 Jan 23:03:05 - [info] Node-RED version: v1.2.7
Jan 25 23:03:05 DietPi node-red[1266]: 25 Jan 23:03:05 - [info] Node.js version: v15.6.0
Jan 25 23:03:05 DietPi node-red[1266]: 25 Jan 23:03:05 - [info] Linux 5.4.83-v7+ arm LE
Jan 25 23:03:10 DietPi node-red[1266]: 25 Jan 23:03:10 - [info] Loading palette nodes
Jan 25 23:03:24 DietPi node-red[1266]: 25 Jan 23:03:24 - [info] Settings file : /mnt/dietpi_userdata/node-red/settings.js
Jan 25 23:03:24 DietPi node-red[1266]: 25 Jan 23:03:24 - [info] Context store : 'default' [module=memory]
Jan 25 23:03:24 DietPi node-red[1266]: 25 Jan 23:03:24 - [info] User directory : /mnt/dietpi_userdata/node-red
Jan 25 23:03:24 DietPi node-red[1266]: 25 Jan 23:03:24 - [warn] Projects disabled : editorTheme.projects.enabled=false
Jan 25 23:03:24 DietPi node-red[1266]: 25 Jan 23:03:24 - [info] Flows file : /mnt/dietpi_userdata/node-red/flows_DietPi.json
Jan 25 23:03:24 DietPi node-red[1266]: 25 Jan 23:03:24 - [info] Server now running at http://127.0.0.1:1880/
Jan 25 23:03:24 DietPi node-red[1266]: 25 Jan 23:03:24 - [warn]
Jan 25 23:03:24 DietPi node-red[1266]: ---------------------------------------------------------------------
Jan 25 23:03:24 DietPi node-red[1266]: Your flow credentials file is encrypted using a system-generated key.
Jan 25 23:03:24 DietPi node-red[1266]: If the system-generated key is lost for any reason, your credentials
Jan 25 23:03:24 DietPi node-red[1266]: file will not be recoverable, you will have to delete it and re-enter
Jan 25 23:03:24 DietPi node-red[1266]: your credentials.
Jan 25 23:03:24 DietPi node-red[1266]: You should set your own key using the 'credentialSecret' option in
Jan 25 23:03:24 DietPi node-red[1266]: your settings file. Node-RED will then re-encrypt your credentials
Jan 25 23:03:24 DietPi node-red[1266]: file using your chosen key the next time you deploy a change.
Jan 25 23:03:24 DietPi node-red[1266]: ---------------------------------------------------------------------
Jan 25 23:03:24 DietPi node-red[1266]: 25 Jan 23:03:24 - [info] Starting flows


everythimg seems fine. node-red works perfectly.

should I ignore mentioned issue or do you think that it needs to be investigated further?


after stop node-red:

Jan 25 23:09:24 DietPi node-red[1266]: 25 Jan 23:09:24 - [info] Stopped flows
Jan 25 23:09:24 DietPi systemd[1]: node-red.service: Succeeded.
Jan 25 23:09:24 DietPi systemd[1]: Stopped Node-RED (DietPi).

[Joulinar]

and starting it again?

[novitibo]

temporary fix:

with cron job that keeps those two processes alive just for needed 1 minute per day should be ok?

[Joulinar]

temporary fix:

with cron job that keeps those two processes alive just for needed 1 minute per day should be ok?

this I don't understood. What should be the aim?

[novitibo]

and starting it again?

no.

node-red does not keeps restarting

[Joulinar]

so it is running fine now? No CPU spikes anymore?

[novitibo]

temporary fix:

with cron job that keeps those two processes alive just for needed 1 minute per day should be ok?

this I don't understood. What should be the aim?

I need node-red only for to few flows, all are scheduled for one second before and one second after midnight.
I can keep node-red alive only for those two seconds (or let's say 1 minute). For RPI's health

[novitibo]

so it is running fine now? No CPU spikes anymore?

node-red isn't restarting, but node and npm processes are CPU spiking

[Joulinar]

well you could create a script stating node, do a sleep 120 and stop node again. This than to be scheduled on cron