I was mucking about with some new stuff.
Suddenly: host not responding.
Waiting waiting waiting.
Nothing.
Then I get this error:
ui/css/app.min.less' wasn't found
What does that mean?
I powered up another RPI and it is doing the same.
Googleing it doesn't show me anything I can understand at this point.
Further investigation reveals this:
Logged into machine.
cd .node-red
node-red-stop
node-red-start
This is what I am seeing:
14 Apr 10:50:52 - [warn] [function:Button Colour] ** Reset button colours **
pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/sbin/hwclock -r
pam_unix(sudo:session): session opened for user root by (uid=0)
14 Apr 10:50:58 - [info] [udp out:1095c327.4fb3f5] udp ready: 192.168.0.21:6723
pam_unix(sudo:session): session closed for user root
14 Apr 10:51:01 - [info] [mqtt-broker:MQTT host] Connection failed to broker: mqtt://192.168.0.99:1883
pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/sbin/hwclock -r
pam_unix(sudo:session): session opened for user root by (uid=0)
14 Apr 10:51:06 - [info] [mqtt-broker:MQTT host] Connected to broker: mqtt://192.168.0.99:1883
pam_unix(sudo:session): session closed for user root
14 Apr 10:51:08 - [info] [mqtt-broker:MQTT host] Connection failed to broker: mqtt://192.168.0.99:1883
pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/sbin/hwclock -r
pam_unix(sudo:session): session opened for user root by (uid=0)
14 Apr 10:51:15 - [info] [mqtt-broker:MQTT host] Connected to broker: mqtt://192.168.0.99:1883
pam_unix(sudo:session): session closed for user root
pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/sbin/hwclock -r
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/sbin/hwclock -r
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/sbin/hwclock -r
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/sbin/hwclock -r
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
That looks worrying.
Though I think I see a problem and the last part with the COMMAND=/sbin/hwclock -r
is what I was something I was doing.
May have to roll back to an earlier flow.
(Luckily I had made a backup 2 days ago.)
Rolled back and NR seems to start ok.
The errors shown are not there and though MQTT doesn't come up straight away, it does get itself working.
But now I can't get to the NR page for that machine.
Best of my knowledge it is ok otherwise.
Powered down this and got that machine working with display/keyboard.
Booting is painful.
NR loads, but it is slow.
As you can see it has been restarting for reasons unknown.
The machine is a RPI B Single core so it is really running flat out.
I tried a recent back up.
Still fails.
An earlier back up (say from March)
Fails.
Here is some stuff I got from it while I was looking:
Screen shot nothing new really only that it seems to be booting, but then failing and restarting.
The other is just more from the CLI when I start Node-Red
Log1.txt (3.0 KB)
I have finally rolled it back a fair way with dates.
I don't think that matters, but what I can see is a lot of traffic.
I went to one of the main timer parts and I think it has gone mad.
Very quickly I see the default 10 seconds flash up.
But before I can do much else - like press one of those STOP buttons to stop the loop driving the rest of the flow nuts, it suddenly goes to 0.02ms
(See latest picture)
How can I get to the code and maybe stop one of the two blocking nodes I have just near it?