NR runs, but not

General
21

Everything you have done has been and is outstanding. I just misunderstood what I was reading.

Thanks to all for the assistance and getting me clear of this problem.

22

node-red does not log there by default. In fact the 'correct' command to use is
sudo journalctl -f -u nodered
which is what node-red-log uses.

23

Yes you are right of course, I'm getting confused with another service which has it's own log.

24

Hey Colin,
Just for clarity on the initial post I sent (for future reference), as I was thinking through what I had tried in working to understand what was going on, I realize I failed to indicate that when that strange issue presented

Starting as a systemd service.
nodered.service: Succeeded.

.. I had at that time then exited (ctrl-C) and ran HTOP to view current processes and there was no instance of node running.

I thought I'd mention this because your (good) thinking that I might have gotten that result because I instigated node-red-start when an instance was already running, I don't think that was the case.

I guess I'm still curious as to how I ended up with such situation (all is fine now).

Again, thank you (and to dceejay and knolleaery) for your always very useful insights and assistance.

25

Exited from what? If you exit from node-red-start then that will have left node-red running.
Exactly how did you determine in htop that node-red was not running?

26

The command sudo systemctl enable nodered.service does not start node-red when you run it. It enable the service to autostart. So if you reboot or node-red crashes, the system will restart it.

But you have to run node-red-start or reboot in order to start Node-RED running.

27

@StrongTown did use node-red-start, but the output stopped after the starting message, almost certainly because it was already running. See the first post.

28

I did use node-red-start as I had previously stopped NR because I had changed the context directory in setting.js and wanted to effect the change (I do have NR set to run at boot, but inconsequential here). Here are the events:

> node-red-stop
[Note] NR stopped as expected, normal notification. CLI prompt returned.
> node-red-start

Use   node-red-stop                          to stop Node-RED
Use   node-red-start                         to start Node-RED again
Use   node-red-log                           to view the recent log output
Use   sudo systemctl enable nodered.service  to autostart Node-RED at every boot
Use   sudo systemctl disable nodered.service to disable autostart on boot
 
To find more nodes and example flows - go to http://flows.nodered.org
 
Starting as a systemd service.
nodered.service: Succeeded.

[Note} At this point I thought it was booting normally and waited. Figuring it was just working on something I went to do something else and 15 mins later the (log) screen (still active in terminal) had not changed. So here is what I typed next (and results):

> ctrl-c (to exit NR log mode)
> node-red-stop
> HTOP (there was no node process running anywhere in this output)
> ctrl-c (to exit HTOP)
> node-red-start

I ended up back at the same log screen (see above) where NR simply sits idle (forever it seems) at:

nodered.service: Succeeded.

Hope this provides more clarity. Again, not wanting to beat this to death, just curious as to what could have put NR into this mode and to make the point that I don't think a previous instance of NR process was running to cause it.

29

It seems you are right. What happens if you stop node red then run
node-red

Did you set the log level to trace? I think I suggested that earlier.

30

I have yes but I'll have to wait now to see if this re-occurs.

31

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.