Code=killed, Status=4/ILL General

General
1

I have this problem

Sep 13 22:59:19 arm sudo[4115]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 13 22:59:19 arm Node-RED[3164]: 13 Sep 22:59:19 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Sep 13 22:59:21 arm sudo[4115]: pam_unix(sudo:session): session closed for user root
Sep 13 23:31:47 arm sudo[4143]: ubuntu : TTY=unknown ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/systemctl restart zavitIO.service
Sep 13 23:31:47 arm sudo[4143]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 13 23:31:48 arm sudo[4143]: pam_unix(sudo:session): session closed for user root
Sep 14 00:31:47 arm sudo[4198]: ubuntu : TTY=unknown ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/systemctl restart zavitIO.service
Sep 14 00:31:47 arm sudo[4198]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 14 00:31:48 arm sudo[4198]: pam_unix(sudo:session): session closed for user root
Sep 14 00:36:27 arm systemd[1]: nodered.service: Main process exited, code=killed, status=4/ILL
Sep 14 00:36:27 arm systemd[1]: nodered.service: Failed with result 'signal'.
Sep 14 00:36:28 arm systemd[1]: nodered.service: Service hold-off time over, scheduling restart.
Sep 14 00:36:28 arm systemd[1]: nodered.service: Scheduled restart job, restart counter is at 1.
Sep 14 00:36:28 arm systemd[1]: Stopped Node-RED graphical event wiring tool.
Sep 14 00:36:28 arm systemd[1]: Started Node-RED graphical event wiring tool.
Sep 14 00:36:35 arm systemd[1]: nodered.service: Main process exited, code=killed, status=4/ILL
Sep 14 00:36:35 arm systemd[1]: nodered.service: Failed with result 'signal'.
Sep 14 00:36:35 arm systemd[1]: nodered.service: Service hold-off time over, scheduling restart.
Sep 14 00:36:35 arm systemd[1]: nodered.service: Scheduled restart job, restart counter is at 2.
Sep 14 00:36:35 arm systemd[1]: Stopped Node-RED graphical event wiring tool.
Sep 14 00:36:35 arm systemd[1]: Started Node-RED graphical event wiring tool.
Sep 14 00:36:35 arm systemd[1]: nodered.service: Main process exited, code=killed, status=4/ILL
Sep 14 00:36:35 arm systemd[1]: nodered.service: Failed with result 'signal'.
Sep 14 00:36:35 arm systemd[1]: nodered.service: Service hold-off time over, scheduling restart.
Sep 14 00:36:35 arm systemd[1]: nodered.service: Scheduled restart job, restart counter is at 3.
Sep 14 00:36:35 arm systemd[1]: Stopped Node-RED graphical event wiring tool.
Sep 14 00:36:35 arm systemd[1]: Started Node-RED graphical event wiring tool.
Sep 14 00:36:36 arm systemd[1]: nodered.service: Main process exited, code=killed, status=4/ILL
Sep 14 00:36:36 arm systemd[1]: nodered.service: Failed with result 'signal'.
Sep 14 00:36:36 arm systemd[1]: nodered.service: Service hold-off time over, scheduling restart.
Sep 14 00:36:36 arm systemd[1]: nodered.service: Scheduled restart job, restart counter is at 4.
Sep 14 00:36:36 arm systemd[1]: Stopped Node-RED graphical event wiring tool.
Sep 14 00:36:36 arm systemd[1]: Started Node-RED graphical event wiring tool.
Sep 14 00:36:36 arm systemd[1]: nodered.service: Main process exited, code=killed, status=4/ILL
Sep 14 00:36:36 arm systemd[1]: nodered.service: Failed with result 'signal'.
Sep 14 00:36:36 arm systemd[1]: nodered.service: Service hold-off time over, scheduling restart.
Sep 14 00:36:36 arm systemd[1]: nodered.service: Scheduled restart job, restart counter is at 5.
Sep 14 00:36:36 arm systemd[1]: Stopped Node-RED graphical event wiring tool.
Sep 14 00:36:36 arm systemd[1]: Started Node-RED graphical event wiring tool.
Sep 14 00:36:37 arm systemd[1]: nodered.service: Main process exited, code=killed, status=4/ILL
Sep 14 00:36:37 arm systemd[1]: nodered.service: Failed with result 'signal'.
Sep 14 00:36:37 arm systemd[1]: nodered.service: Service hold-off time over, scheduling restart.
Sep 14 00:36:37 arm systemd[1]: nodered.service: Scheduled restart job, restart counter is at 6.
Sep 14 00:36:37 arm systemd[1]: Stopped Node-RED graphical event wiring tool.
Sep 14 00:36:37 arm systemd[1]: nodered.service: Start request repeated too quickly.
Sep 14 00:36:37 arm systemd[1]: nodered.service: Failed with result 'signal'.
Sep 14 00:36:37 arm systemd[1]: Failed to start Node-RED graphical event wiring tool.

2

Would have been better to start a whole new topic instead of reviving a 2+ year old one.

And supplying more details such as versions, hardware, etc.

3

[ADMIN - moved to new topic}

@Rcrdo Ricardo - welcome to the forum. as @Gunner suggested you need to provide more information if you want some help.

  1. Was your NR ever working? If so, what did you change?
  2. It looks like you are running as root. Why?
  3. What device are you running on? What OS are you using?
  4. What version of NR nad node.js are you using? (this can be gotton from te startup log)
  5. What are you trying to do?
  6. what were you doing when the issue cropped up?

Please answer ALL the questions.

4

Hi, I working with the

  • node red version 2.0.5
  • npm version 6.10.3
  • nodejs version 10.16.2
  • OS ARM Ubuntu 18.0.4
    what runs as root is commands in terminal, with the exec node

Oct 13 14:18:10 arm systemd[1]: Started Node-RED graphical event wiring tool.
Oct 13 14:19:09 arm Node-RED[265]: BAIL ON node-red-contrib-snmp-trap-listener/snmp-trap-listener
Oct 13 14:19:09 arm Node-RED[265]: BAIL ON node-red-contrib-configurable-interval/configurable interval
Oct 13 14:19:09 arm Node-RED[265]: BAIL ON node-red-contrib-gpsd/gpsd
Oct 13 14:19:09 arm Node-RED[265]: BAIL ON node-red-contrib-ibm-watson-iot/wiotp
Oct 13 14:19:12 arm Node-RED[265]: BAIL ON node-red-contrib-moment/moment
Oct 13 14:19:12 arm Node-RED[265]: BAIL ON node-red-contrib-moment/humanizer
Oct 13 14:19:12 arm Node-RED[265]: BAIL ON node-red-contrib-binary/binary
Oct 13 14:19:15 arm Node-RED[265]: 13 Oct 14:19:15 - [info] Dashboard version 2.30.0 started at /ui
Oct 13 14:19:16 arm Node-RED[265]: BAIL ON node-red-node-base64/base64
Oct 13 14:19:16 arm Node-RED[265]: BAIL ON node-red-node-ping/ping
Oct 13 14:19:16 arm Node-RED[265]: BAIL ON node-red-node-random/random
Oct 13 14:19:16 arm Node-RED[265]: BAIL ON node-red-node-smooth/smooth
Oct 13 14:19:16 arm Node-RED[265]: BAIL ON node-red-node-snmp/snmp
Oct 13 14:19:18 arm Node-RED[265]: 13 Oct 14:19:18 - [info] Settings file : /home/ubuntu/.node-red/settings.js
Oct 13 14:19:18 arm Node-RED[265]: 13 Oct 14:19:18 - [info] Context store : 'default' [module=memory]
Oct 13 14:19:18 arm Node-RED[265]: 13 Oct 14:19:18 - [info] User directory : /home/ubuntu/.node-red
Oct 13 14:19:18 arm Node-RED[265]: 13 Oct 14:19:18 - [warn] Projects disabled : editorTheme.projects.enabled=false
Oct 13 14:19:18 arm Node-RED[265]: 13 Oct 14:19:18 - [warn] Flows file name not set. Generating name using hostname.
Oct 13 14:19:18 arm Node-RED[265]: 13 Oct 14:19:18 - [info] Flows file : /home/ubuntu/.node-red/flows_arm.json
Oct 13 14:19:18 arm Node-RED[265]: (node:265) ExperimentalWarning: The dns.promises API is experimental
Oct 13 14:19:19 arm Node-RED[265]: 13 Oct 14:19:19 - [info] Server now running at http://127.0.0.1:1880/
Oct 13 14:19:19 arm Node-RED[265]: 13 Oct 14:19:19 - [warn]
Oct 13 14:19:19 arm Node-RED[265]: ---------------------------------------------------------------------
Oct 13 14:19:19 arm Node-RED[265]: Your flow credentials file is encrypted using a system-generated key.
Oct 13 14:19:19 arm Node-RED[265]: If the system-generated key is lost for any reason, your credentials
Oct 13 14:19:19 arm Node-RED[265]: file will not be recoverable, you will have to delete it and re-enter
Oct 13 14:19:19 arm Node-RED[265]: your credentials.
Oct 13 14:19:19 arm Node-RED[265]: You should set your own key using the 'credentialSecret' option in
Oct 13 14:19:19 arm Node-RED[265]: your settings file. Node-RED will then re-encrypt your credentials
Oct 13 14:19:19 arm Node-RED[265]: file using your chosen key the next time you deploy a change.
Oct 13 14:19:19 arm Node-RED[265]: ---------------------------------------------------------------------
Oct 13 14:19:22 arm Node-RED[265]: 13 Oct 14:19:22 - [info] Starting flows
Oct 13 14:19:27 arm Node-RED[265]: 13 Oct 14:19:27 - [info] Started flows
Oct 13 14:19:31 arm Node-RED[265]: 13 Oct 14:19:31 - [info] [sqlitedb:bd6ed0d6.cd08a8] opened dbTowerZavitV1 ok
Oct 13 14:19:31 arm Node-RED[265]: 13 Oct 14:19:31 - [info] [sqlitedb:bd6ed0d6.cd08a8] opened dbTowerZavitV1 ok
Oct 13 14:19:31 arm Node-RED[265]: 13 Oct 14:19:31 - [info] [sqlitedb:75c9a5b5.6a3a8c] opened dbTowerZavitConfigV1 ok
Oct 13 14:19:31 arm Node-RED[265]: 13 Oct 14:19:31 - [info] serial port /dev/ttyACM0 opened at 9600 baud 8N1
Oct 13 14:19:33 arm sudo[515]: ubuntu : TTY=unknown ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/systemctl start NoderedSTS.service
Oct 13 14:19:33 arm sudo[514]: ubuntu : TTY=unknown ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/systemctl restart zavitIO.service
Oct 13 14:19:33 arm Node-RED[265]: 13 Oct 14:19:33 - [info] [mqtt-broker:5b89c792.bebd28] Connection failed to broker: mqtt://68.66.205.226:1883
Oct 13 14:19:33 arm sudo[515]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 13 14:19:33 arm sudo[514]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 13 14:19:35 arm sudo[515]: pam_unix(sudo:session): session closed for user root
Oct 13 14:19:36 arm Node-RED[265]: 13 Oct 14:19:36 - [warn] [function:EXECUTE TASK] TASK: 0
Oct 13 14:19:36 arm Node-RED[265]: 13 Oct 14:19:36 - [warn] [function:EXECUTE TASK] TASK: 0
Oct 13 14:19:36 arm sudo[514]: pam_unix(sudo:session): session closed for user root
Oct 13 14:19:38 arm sudo[563]: ubuntu : TTY=unknown ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/chmod 777 /dev/usb/lp0
Oct 13 14:19:38 arm sudo[563]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 13 14:19:38 arm sudo[563]: pam_unix(sudo:session): session closed for user root
Oct 13 14:19:39 arm Node-RED[265]: 13 Oct 14:19:39 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:39 arm sudo[572]: ubuntu : TTY=unknown ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/printf \x1C\x2E\x1B\x52\x07\x1B\x74\x12\x1B\x61\x01
Oct 13 14:19:39 arm sudo[572]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 13 14:19:39 arm sudo[572]: pam_unix(sudo:session): session closed for user root
Oct 13 14:19:39 arm Node-RED[265]: 13 Oct 14:19:39 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:40 arm Node-RED[265]: 13 Oct 14:19:40 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:41 arm Node-RED[265]: 13 Oct 14:19:41 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:42 arm Node-RED[265]: 13 Oct 14:19:42 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:44 arm Node-RED[265]: 13 Oct 14:19:44 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:45 arm Node-RED[265]: 13 Oct 14:19:45 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:46 arm Node-RED[265]: 13 Oct 14:19:46 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:47 arm Node-RED[265]: 13 Oct 14:19:47 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:48 arm Node-RED[265]: 13 Oct 14:19:48 - [info] [mqtt-broker:5b89c792.bebd28] Connected to broker: mqtt://68.66.205.226:1883
Oct 13 14:19:48 arm Node-RED[265]: 13 Oct 14:19:48 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:50 arm Node-RED[265]: 13 Oct 14:19:50 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:51 arm Node-RED[265]: 13 Oct 14:19:51 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:52 arm Node-RED[265]: 13 Oct 14:19:52 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:53 arm Node-RED[265]: 13 Oct 14:19:53 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:54 arm Node-RED[265]: 13 Oct 14:19:54 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:56 arm Node-RED[265]: 13 Oct 14:19:56 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:57 arm Node-RED[265]: 13 Oct 14:19:57 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:58 arm Node-RED[265]: 13 Oct 14:19:58 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:19:59 arm Node-RED[265]: 13 Oct 14:19:59 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:00 arm Node-RED[265]: 13 Oct 14:20:00 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:01 arm Node-RED[265]: 13 Oct 14:20:01 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:02 arm Node-RED[265]: 13 Oct 14:20:02 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:03 arm Node-RED[265]: 13 Oct 14:20:03 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:04 arm Node-RED[265]: 13 Oct 14:20:04 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:05 arm Node-RED[265]: 13 Oct 14:20:05 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:07 arm Node-RED[265]: 13 Oct 14:20:07 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:07 arm Node-RED[265]: 13 Oct 14:20:07 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:08 arm Node-RED[265]: 13 Oct 14:20:08 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:09 arm Node-RED[265]: 13 Oct 14:20:09 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:11 arm Node-RED[265]: 13 Oct 14:20:11 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:12 arm Node-RED[265]: 13 Oct 14:20:12 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:20:13 arm Node-RED[265]: 13 Oct 14:20:13 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:27:44 arm Node-RED[265]: 13 Oct 14:27:44 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)
Oct 13 14:32:48 arm Node-RED[265]: 13 Oct 14:32:48 - [info] [mqtt-broker:5b89c792.bebd28] Disconnected from broker: mqtt://68.66.205.226:1883
Oct 13 14:33:03 arm Node-RED[265]: 13 Oct 14:33:03 - [info] [mqtt-broker:5b89c792.bebd28] Connected to broker: mqtt://68.66.205.226:1883
Oct 13 14:34:02 arm Node-RED[265]: 13 Oct 14:34:02 - [warn] [function:ADD ACTION SESSION] Num cara disponible 1 (face_enable)

this is the service data

nodered.service - Node-RED graphical event wiring tool
Loaded: loaded (/lib/systemd/system/nodered.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-10-13 14:18:10 UTC; 31min ago
Docs: Redirecting…
Main PID: 265 (node-red)
CGroup: /system.slice/nodered.service
└─265 node-red

5

That version of node-red needs nodejs at least 12.

6

the node-red version is 12.0.5
you say me, if i have node red in version 12.0.5, i need update nodejs to version 12

7

You mean 2.0.5

Yes, that is my understanding.

Did you install/upgrade node-red using the recommended script for Ubuntu/Debian/Pi? If so then I am surprised it did not insist on upgrading nodejs. The easiest way to upgrade is to first make sure all the installed nodes are up to date then re-run that script, adding --node12 (or 14 or 16). It will install the latest node-red and also upgrade nodejs. I use version 14 generally.

Whether that is the cause of your particular problem I don't know.

8

Update with the script you mentioned, now I have the problem that node-red takes time to start, the command npm -v takes time to execute.

And it is normal ? that if I run the command nodejs -v I get v10.16.2, and if I run node -v I get the version v14.18.1

9

I don't know what the command nodes does, it looks like you now have two versions installed. You need to sort that out. Running
which nodejs might give you a clue.

10

Once you have sorted nodejs post the startup log when you stop node red and start it again.

11

I execute this command, but i have the same problem, node-red takes time like nine minutes to run

12

The purpose was to see where that is installed, to allow you to work out where it has come from.

You haven't posted the startup log I asked for.

13

Oct 14 12:57:11 arm systemd[1]: Started Node-RED graphical event wiring tool.
Oct 14 12:58:09 arm systemd[1]: Stopping Node-RED graphical event wiring tool...
Oct 14 12:58:09 arm systemd[1]: Stopped Node-RED graphical event wiring tool.
Oct 14 13:02:16 arm systemd[1]: Started Node-RED graphical event wiring tool.
Oct 14 13:05:54 arm Node-RED[526]: 14 Oct 13:05:54 - [info]
Oct 14 13:05:54 arm Node-RED[526]: Welcome to Node-RED
Oct 14 13:05:54 arm Node-RED[526]: ===================
Oct 14 13:05:54 arm Node-RED[526]: 14 Oct 13:05:54 - [info] Node-RED version: v2.0.6
Oct 14 13:05:54 arm Node-RED[526]: 14 Oct 13:05:54 - [info] Node.js version: v14.18.1
Oct 14 13:05:54 arm Node-RED[526]: 14 Oct 13:05:54 - [info] Linux 4.14.88-01445-g234c56a-dirty arm LE
Oct 14 13:06:01 arm Node-RED[526]: 14 Oct 13:06:01 - [info] Loading palette nodes
Oct 14 13:06:21 arm Node-RED[526]: BAIL ON node-red-contrib-configurable-interval/configurable interval
Oct 14 13:06:26 arm Node-RED[526]: 14 Oct 13:06:26 - [info] Dashboard version 2.30.0 started at /ui
Oct 14 13:06:28 arm Node-RED[526]: 14 Oct 13:06:28 - [info] Settings file : /home/ubuntu/.node-red/settings.js
Oct 14 13:06:28 arm Node-RED[526]: 14 Oct 13:06:28 - [info] Context store : 'default' [module=memory]
Oct 14 13:06:28 arm Node-RED[526]: 14 Oct 13:06:28 - [info] User directory : /home/ubuntu/.node-red
Oct 14 13:06:28 arm Node-RED[526]: 14 Oct 13:06:28 - [warn] Projects disabled : editorTheme.projects.enabled=false
Oct 14 13:06:29 arm Node-RED[526]: 14 Oct 13:06:29 - [warn] Flows file name not set. Generating name using hostname.
Oct 14 13:06:29 arm Node-RED[526]: 14 Oct 13:06:29 - [info] Flows file : /home/ubuntu/.node-red/flows_arm.json
Oct 14 13:06:29 arm Node-RED[526]: 14 Oct 13:06:29 - [info] Server now running at http://127.0.0.1:1880/
Oct 14 13:06:29 arm Node-RED[526]: 14 Oct 13:06:29 - [warn]
Oct 14 13:06:29 arm Node-RED[526]: ---------------------------------------------------------------------
Oct 14 13:06:29 arm Node-RED[526]: Your flow credentials file is encrypted using a system-generated key.
Oct 14 13:06:29 arm Node-RED[526]: If the system-generated key is lost for any reason, your credentials
Oct 14 13:06:29 arm Node-RED[526]: file will not be recoverable, you will have to delete it and re-enter
Oct 14 13:06:29 arm Node-RED[526]: your credentials.
Oct 14 13:06:29 arm Node-RED[526]: You should set your own key using the 'credentialSecret' option in
Oct 14 13:06:29 arm Node-RED[526]: your settings file. Node-RED will then re-encrypt your credentials
Oct 14 13:06:29 arm Node-RED[526]: file using your chosen key the next time you deploy a change.
Oct 14 13:06:29 arm Node-RED[526]: ---------------------------------------------------------------------
Oct 14 13:06:32 arm Node-RED[526]: 14 Oct 13:06:32 - [info] Starting flows
Oct 14 13:06:39 arm Node-RED[526]: 14 Oct 13:06:39 - [info] Started flows
Oct 14 13:06:42 arm Node-RED[526]: 14 Oct 13:06:42 - [info] [sqlitedb:bd6ed0d6.cd08a8] opened dbTowerZavitV1 ok
Oct 14 13:06:42 arm Node-RED[526]: 14 Oct 13:06:42 - [info] [sqlitedb:75c9a5b5.6a3a8c] opened dbTowerZavitConfigV1 ok
Oct 14 13:06:42 arm Node-RED[526]: 14 Oct 13:06:42 - [info] [serialconfig:fed31a1d.daf68] serial port /dev/ttyACM0 opened at 9600 baud 8N1
Oct 14 13:06:45 arm sudo[615]: ubuntu : TTY=unknown ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/systemctl start NoderedSTS.service
Oct 14 13:06:45 arm sudo[615]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 14 13:06:46 arm Node-RED[526]: 14 Oct 13:06:46 - [info] [mqtt-broker:5b89c792.bebd28] Connection failed to broker: mqtt://68.66.205.226:1883
Oct 14 13:06:46 arm sudo[615]: pam_unix(sudo:session): session closed for user root

14

It took 50 seconds to start, not 9 minutes.

15

No, I am wrong, it is a bit longer. Can you run
node-red-stop
Then
node-red-start
And post that please. Note whether there is a significant time between typing the start command and the first output.

What hardware are you running on and is it Ubuntu server or Ubuntu desktop?

16

when the system startup, run the nodered service after start system and node red is start take nine minutes, but when node red start no problem take 50 seconds.

i check the problem with npm, when y execute npm -v command take that same nine minutes, the npm version is 6.10.3

17

Linux arm 4.14.88-01445-g234c56a-dirty #11 Thu Jun 3 15:08:33 -05 2021 armv7l armv7l armv7l GNU/Linux

18

Do you mean it takes that long to boot up and start node red automatically? If so then as a test, disable node red auto start
sudo systemctl disable nodered
Then reboot.
After it has fully booted run
node-red-start|

You haven't said what hardware it is running on. Is it a Pi? If so, which one?

You haven't said whether it is Ubuntu server or Ubuntu desktop. Please try to answer all questions, it saves me wearing out my phone touch screen asking questions multiple times. :slight_smile:

19

Glomation - GESBC-9G25i

Sorry :cold_sweat:

20

You still haven't answered this.