NodeRed service automattically stopping on Cerbo GX

I am running NodeRed on Cerbo GX, and after a few hours of it running OK, the service (on the underlying Venus OS) is stopped.

I can confirm something is stopping it by connecting via SSH and running the following command:

ls -la /service/node-red-venus

which has the output:

drwxr-xr-x    4 root     root           120 Feb 24 12:19 .
drwxr-xr-x   33 root     root           860 Feb 24 12:19 ..
-rw-r--r--    1 root     root             0 Jan 28 13:26 down
drwxr-xr-x    3 root     root           100 Feb 24 12:19 log
-rwxr-xr-x    1 root     root           217 Jan 28 13:26 run
drwx------    2 root     root           120 Feb 24 12:19 supervise

Notice there is a file there called “down”, with this file present it is instructing the NodeRed service to stop running. When I delete that file, NodeRed starts to run for a few hours, but eventually something puts that “down” file back there. I am not using any CLI commands that would stop the NodeRed service.

What is also unusual about this “down” file is, that is always has the same timestamp.

Does anyone know what might be stopping the service?

Further information:

Command svstat /service/node-red-venus outputs something like

/service/node-red-venus: down 4047 seconds

I am starting to discover a bit more. The “down” file seems to be added, each time I restart the device via the “Remote Console”.

I have NodeREd enabled

So I don’t know why anything would want to be turning the service off by putting the “down” file there.