Hello I have a problem with node-red. I have installed the node.js application from the PlcNext store. and then, installed node-red but as I need NodeRed starts automatically at startup, I also tried to install and run pm2. But with the node.js application coming from the plcnext store, pm2 doesn’t work anymore : https://www.plcnext-community.net/index.php?option=com_content&view;=article&id;=300:how-to-start-node-red-automatically-when-the-plc-starts&catid;=78&Itemid;=366⟨=en so, i have used this one : https://www.plcnext-community.net/index.php?option=com_content&view;=article&id;=379:how-to-start-node-red-automatically-on-boot-using-init-d⟨=en But there is one problem : this script starts node red as root, and nodered doesn’t work fine as root. Some nodes don’t work correctly anymore (opcua ping, exec, etc…) I found a line user=root in this file, and I modified it as user=admin But it seems that this modified file doesn’t start node-red (I don’t know if it is because of a problem in the file itself, or in the handling of this file). After I made a change in the file, I typed these commands : root@axcf2152:/etc/init.d# sudo chmod 755 start_nodered root@axcf2152:/etc/init.d# sudo chmod 755 start_noderedroot@axcf2152:/etc/init.d# sudo update-rc.d start_nodered defaults 99
And I got this result :
System startup links for /etc/init.d/start_nodered already exist. Is this normel? Is this a problem? how to make this script work correctly and node-red starts automatically as admin, and not as root? Thanks
Hi Michel, yes the result is ok. The command update-rc.d was triggered before and the symlink to the init script were already setup in the /etc/rc*.d folders. You can check if node-red is running with the command
ps | grep node
It should emit something like this
admin@axcf2152:~$ ps | grep node
> 1752 admin 152m S node-red
> 1780 admin 2604 S grep node
> admin@axcf2152:~$
The username is written after the PID (1752) of the process. In this case it is admin.
Unfortunately, i only get this reply : admin@axcf2152:~$ ps | grep node
5301 admin 2604 S grep node And a ‘top’ command returns only this : PID PPID USER STAT VSZ %VSZ %CPU COMMAND
1288 1 plcnext_ S 569m 116% 26% Arp.System.Application --main=true --s
1337 1288 plcnext_ S 190m 39% 10% /usr/bin/Arp.System.Application --chil
1338 1288 plcnext_ S 174m 36% 6% /usr/bin/Arp.System.Application --chil
21 2 root SW 0 0% 5% [ktimersoftd/1]
8 2 root SW 0 0% 2% [ktimersoftd/0]
20 2 root SW 0 0% 1% [rcuc/1]
5290 2 root IW 0 0% 1% [kworker/1:0]
5305 5296 admin R 2836 1% 0% top
12 2 root SW 0 0% 0% [rcuc/0]
5295 5293 admin S 7072 1% 0% sshd: admin@pts/0> 22 2 root SW 0 0% 0% [ksoftirqd/1]
7 2 root SW 0 0% 0% [ksoftirqd/0]
9 2 root IW 0 0% 0% [rcu_preempt]
578 2 root SW 0 0% 0% [spi0]
1053 1 root S 99028 20% 0% /usr/bin/lttng-sessiond --daemonize
1230 1 tss S 13064 3% 0% /usr/sbin/tcsd
1030 1 ntp S 8556 2% 0% /usr/sbin/ntpd -u ntp:ntp -p /var/run/
1245 1240 www S 7700 2% 0% nginx: worker process
1242 1240 www S 7700 2% 0% nginx: worker process
1241 1240 www S 7700 2% 0% nginx: worker process any other suggestion? Nothing else to change in the script file?
So it seems the process does not come up on startup. Is something written to the log files? If you used the init script from Martin Boers there should be a log file in
/var/log/node-red.log
Hi Michel, I have used the script with root user and in my case the node-red have worked well. I am using only the OPCUA Client and Mqtt Client. I tested using the admin user (USER = admin) and as you have tested, the node-red don´t start. I think with admin user the script can´t to write the node-red log file in the default path (var/log). Maybe this is causing any error. Then I have changed the path to LOG=‘/opt/plcnext/node-red.log’. Now the node-red is starting again. Please try these changes: USER = admin LOG='/opt/plcnext/node-red.log
So here is something very strange Now nodered starts with the changes in the file
But, yesterday I had to start nodered manually as admin, and my Ping node was working fine. Now that nodered starts automatically, ping node doesn’t work anymore. It returns a message ENOENT ping command not found How can this command be not found while it was working yesterday, and of course, it also works fine in the terminal Do you have a idea?
Here is the log : (now in the /opt/plcnext directory)
14 May 19:07:02 - [info]
Welcome to Node-RED===================
14 May 19:07:02 - [info] Node-RED version: v0.20.514 May 19:07:02 - [info] Node.js version: v10.15.314 May 19:07:02 - [info] Linux 4.14.63-rt40-pxc arm LE14 May 19:07:09 - [info] Loading palette nodes14 May 19:07:58 - [warn] rpi-gpio : Raspberry Pi specific node set inactive14 May 19:07:59 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library14 May 19:08:02 - [info] Dashboard version 2.14.0 started at /ui14 May 19:08:45 - [info] Settings file : /opt/plcnext/.node-red/settings.js14 May 19:08:45 - [info] Context store : ‘default’ [module=memory]14 May 19:08:45 - [info] User directory : /opt/plcnext/.node-red14 May 19:08:45 - [warn] Projects disabled : editorTheme.projects.enabled=false14 May 19:08:45 - [info] Flows file : /opt/plcnext/.node-red/flows_axcf2152.json14 May 19:08:45 - [info] Server now running at http://127.0.0.1:1880/14 May 19:08:45 - [warn]
---------------------------------------------------------------------Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentialsfile will not be recoverable, you will have to delete it and re-enteryour credentials.
You should set your own key using the ‘credentialSecret’ option inyour settings file. Node-RED will then re-encrypt your credentialsfile using your chosen key the next time you deploy a change.---------------------------------------------------------------------
14 May 19:08:47 - [info] Starting flows14 May 19:08:52 - [info] [google-action in:Action Request] Listening on port 808114 May 19:08:53 - [error] [wunderground:fe87b03e.74aa3] No Wunderground API key set14 May 19:08:53 - [info] Started flows14 May 19:08:54 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:08:54 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:54 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:54 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:54 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:54 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:08:55 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:08:55 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:55 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:08:55 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:55 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:56 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:56 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:08:56 - [info] [mqtt-broker:beebotte] Connected to broker: mqtt://mqtt.beebotte.com:188314 May 19:08:57 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:57 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:57 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:57 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:57 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:08:57 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:08:58 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:58 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:58 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:58 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:58 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:08:58 - [error] [OPCUA-IIoT-Read:… In the local server] Error: Client Not Open On Read14 May 19:08:59 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:08:59 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:59 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:59 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:59 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:08:59 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:00 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:09:00 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:09:00 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:01 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:01 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:01 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:01 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:09:02 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:02 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:02 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:02 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:02 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:09:03 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:09:03 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:03 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:03 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:03 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:03 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:09:04 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:09:04 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:04 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:04 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:04 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:09:05 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:10 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:13 - [error] [http request:Load JPG image from AXIS] Error: connect EHOSTUNREACH 192.168.1.46:8014 May 19:09:13 - [error] [file:Write image] failed to write to file: Error: EACCES: permission denied, open 'image.jpg’14 May 19:09:15 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:20 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:25 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:30 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:35 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:40 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:45 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:50 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:09:56 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:01 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:06 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:11 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:16 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:21 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:26 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:31 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:36 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:41 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:46 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:51 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:10:57 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:01 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:02 - [error] [http request:Load JPG image from AXIS] Error: connect EHOSTUNREACH 192.168.1.46:8014 May 19:11:02 - [error] [file:Write image] failed to write to file: Error: EACCES: permission denied, open 'image.jpg’14 May 19:11:07 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:12 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:17 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:22 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:27 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:32 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:37 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:42 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:47 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:52 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:11:57 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:02 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:07 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:12 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:17 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:22 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:27 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:32 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:37 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:42 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:47 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:52 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:12:57 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:02 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:07 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:12 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:17 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:22 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:27 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:32 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:37 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:42 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:47 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:52 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:13:57 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:02 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:07 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:12 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:17 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:22 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:27 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:32 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:37 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:42 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:47 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:52 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:14:57 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:02 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:07 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:12 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:17 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:22 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:27 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:32 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:37 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:42 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:47 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:52 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:15:57 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:16:02 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:16:07 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:16:12 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found14 May 19:16:17 - [error] [ping:f2f9771f.7cb348] ENOENT ping command not found
don’t take care about the errors about the file to write, this is normal.But as you can see, there are many ENOENT.
Now, I kill Node-red, and then, I restart it as admin, via the command line :
source code here
admin@axcf2152:~$ kill -9 1295admin@axcf2152:~$ node-red14 May 19:23:44 - [info]
Welcome to Node-RED===================
14 May 19:23:45 - [info] Node-RED version: v0.20.514 May 19:23:45 - [info] Node.js version: v10.15.314 May 19:23:45 - [info] Linux 4.14.63-rt40-pxc arm LE14 May 19:23:53 - [info] Loading palette nodes14 May 19:24:29 - [warn] rpi-gpio : Raspberry Pi specific node set inactive14 May 19:24:29 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library14 May 19:24:32 - [info] Dashboard version 2.14.0 started at /ui14 May 19:25:04 - [info] Settings file : /opt/plcnext/.node-red/settings.js14 May 19:25:04 - [info] Context store : ‘default’ [module=memory]14 May 19:25:04 - [info] User directory : /opt/plcnext/.node-red14 May 19:25:04 - [warn] Projects disabled : editorTheme.projects.enabled=false14 May 19:25:04 - [info] Flows file : /opt/plcnext/.node-red/flows_axcf2152. json14 May 19:25:05 - [info] Server now running at http://127.0.0.1:1880/14 May 19:25:05 - [warn]
---------------------------------------------------------------------Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentialsfile will not be recoverable, you will have to delete it and re-enteryour credentials.
You should set your own key using the ‘credentialSecret’ option inyour settings file. Node-RED will then re-encrypt your credentialsfile using your chosen key the next time you deploy a change.---------------------------------------------------------------------
14 May 19:25:06 - [info] Starting flows14 May 19:25:11 - [info] [google-action in:Action Request] Listening on port 808 114 May 19:25:13 - [error] [wunderground:fe87b03e.74aa3] No Wunderground API key set14 May 19:25:13 - [info] Started flows14 May 19:25:14 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:14 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:14 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:14 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:14 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:14 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:15 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:15 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:15 - [info] [mqtt-broker:beebotte] Connected to broker: mqtt://mqtt .beebotte.com:188314 May 19:25:15 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:16 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:16 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:16 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:16 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:16 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:17 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:17 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:17 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:17 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:17 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:18 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:18 - [error] [OPCUA-IIoT-Read:… In the local server] Error: Clien t Not Open On Read14 May 19:25:18 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:18 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:18 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:18 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:19 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:20 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:20 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:20 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:20 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:20 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:21 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:21 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:21 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:21 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:22 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:22 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:22 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:22 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:22 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:23 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:23 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:23 - [error] [OPCUA-IIoT-Read:… In the local server] Error: Clien t Not Open On Read14 May 19:25:23 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:23 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:23 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:24 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:24 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:24 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:25:24 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:25 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:25 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:25:33 - [error] [http request:Load JPG image from AXIS] Error: connect EHOSTUNREACH 192.168.1.46:8014 May 19:28:22 - [error] [http request:Load JPG image from AXIS] Error: connect EHOSTUNREACH 192.168.1.46:8014 May 19:28:48 - [info] Stopping flows14 May 19:28:49 - [info] [mqtt-broker:beebotte] Disconnected from broker: mqtt:/ /mqtt.beebotte.com:188314 May 19:28:49 - [info] Stopped flows14 May 19:28:49 - [info] Starting flows14 May 19:28:52 - [info] [google-action in:Action Request] Listening on port 808 114 May 19:28:53 - [error] [wunderground:fe87b03e.74aa3] No Wunderground API key set14 May 19:28:53 - [info] Started flows14 May 19:28:54 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:28:54 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:55 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:55 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:55 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:55 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:28:55 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:28:56 - [info] [mqtt-broker:beebotte] Connected to broker: mqtt://mqtt .beebotte.com:188314 May 19:28:56 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:56 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:56 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:56 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:56 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:28:57 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:28:57 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:57 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:57 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:57 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:57 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:28:57 - [error] [OPCUA-IIoT-Read:… In the local server] Error: Clien t Not Open On Read14 May 19:28:58 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:28:58 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:58 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:58 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:58 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:58 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:28:59 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:28:59 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:59 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:28:59 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:29:00 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:29:00 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:29:01 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:29:01 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:29:01 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:29:01 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:29:01 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:29:02 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:29:02 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:29:02 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:29:02 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:29:02 - [error] [OPCUA-IIoT-Write:send to local server] Error: Client Not Open On Wirte14 May 19:29:02 - [error] [OPCUA-IIoT-Read:…in the local server] Error: Client Not Open On Read14 May 19:29:06 - [error] [http request:Load JPG image from AXIS] Error: connect EHOSTUNREACH 192.168.1.46:80
As you can see, only some errors with opcUA at the beginning, and then, no error of the ping, and of course, it works fine.
Quiet strange, don’t you think?
Then, i also tried to run the re-install of the ping node via the command line, as admin, with the option --unsafe-perm But I get the same problem with the ping
Hello again. After a while, I restart my tests with nodered. Now, i have installed node.js from the plcnextstore, then node-red, and then I followed the GUIX blog quiet recent on the blogs list. Now, nodered starts correctly with the file in init.d. And as admin, as necessary. But unfortunately, afer about one small minute, it crashes. But if I start it manually with a simple command in the terminal, nodered works correctly. attached you will find the nodered log of its startup. Can you tell me if you find some error? The last start of nodered is manual. everything works fine Te before last start of nodered has been launched by the start_nodered file in init.d. Do you find any information wich should show why iy crashes? Does it exist some other log file of nodered or the 2152 that could help to find the reason of the crash when nodered is started automatically?
node-red.pdf