RasPi WiFi going down when I stop NR

[Trying_to_learn]

I must be going mad, but this has me confused big time.

(Back - back story)

I have replaced a RPZ(W) with a 3B+. But it is on WiFi.

I think now it has done it a couple of times.

Today I was updating some nodes and NR needed to be restarted after their update.

Done, I ssh into the machine.

cd .node-red
node-red-stop

And it just stopped. DEAD.

Opened another shell.

Tried to ping the machine. no path to machine.

Locked up.

From stopping NODE-RED?

Someone?

[jbudd]

Is there any clue in /var/log/syslog (or /var/log/syslog.1) around the time of death?

What does vcgencmd get_throttled show?

[Trying_to_learn]

syslog

.json
Jan 22 10:41:24 TelePi Node-RED[382]: 22 Jan 10:41:24 - [warn] Flows file name not set. Generating name using hostname.
Jan 22 10:41:24 TelePi Node-RED[382]: 22 Jan 10:41:24 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
Jan 22 10:41:24 TelePi Node-RED[382]: 22 Jan 10:41:24 - [info] User directory : /home/pi/.node-red
Jan 22 10:41:24 TelePi Node-RED[382]: 22 Jan 10:41:24 - [info] Context store  : 'default' [module=memory]
Jan 22 10:41:24 TelePi Node-RED[382]: 22 Jan 10:41:24 - [info] HTTP Static    : /home/pi/.node-red/public
Jan 22 10:41:24 TelePi Node-RED[382]: 22 Jan 10:41:24 - [info] Settings file  : /home/pi/.node-red/settings.js
Jan 22 10:41:24 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:23 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:23 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:23 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:23 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:23 TelePi Node-RED[382]: 22 Jan 10:41:23 - [info] Dashboard version 2.26.2 started at /ui
Jan 22 10:41:23 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:23 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:22 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:22 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:22 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:22 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:22 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:22 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:41:22 TelePi systemd-timesyncd[346]: Synchronized to time server for the first time 130.217.74.62:123 (2.debian.pool.ntp.org).
Jan 22 10:17:35 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:17:35 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93
Jan 22 10:17:35 TelePi dhcpcd[433]: wlan0: received approval for 192.168.0.93

Machine power reset 10:40 local time.
Not much to see.

vcgencmd.....

This is my effort at looking at it.

Yes, originally when I swapped the board it was problematic.
That was because it was a supply for a ZERO and I replaced it with a 3B+.

RasPi 2.5A supply now working fine.

To reassure myself - and you:
When I first swapped the machine, it would boot but I saw the flashing LED.
I opened that page and quite a few were RED and thumbs down.

So it does work.
I'm a bit proud of myself for that and it does actually work.

[Colin]

@Trying_to_learn

So it does work.
I'm a bit proud of myself for that and it does actually work

Is everything ok now?

If not, then you showed us syslog when you start node-red but not when you stop node red and the machine dies.

[Trying_to_learn]

All is good now - yes.

The syslog I posted was when it was running and at 10:41 (local) I did the command.

Ok, I may have cropped it badly.

But I didn't see anything around the time of it happening that stuck out.

I had to pull the power plug and hard reset it.
It rebooted and was fine.

It just confuses me what when I stopped NR it (the Pi) dropped the WiFI.

Oh, to also add/qualify.

When I did the node-red-stop
It started saying Node-Red was stopping but it never returned to the prompt.
So maybe NR wasn't stopped and why it isn't shown in the syslog.

(Sorry.)

[Colin]

@Trying_to_learn

It just confuses me what when I stopped NR it (the Pi) dropped the WiFI.

Well if you showed us the relevant part of syslog we might be able to suggest what happened. It is the bit before the restart we need to see, not the bit after it.

[Trying_to_learn]

I shall try to do that soon.

I am about to replace that with (yet) another Pie. Waiting for new one to arrive. (Case)

So if I remember to, I will stop node-red rather than shutting it down and look at the syslog when it reboots.

[jbudd]

I wondered if it might be power supply issue but your Machine health dashboard shows no undervoltage.

It might be worth having an ssh connection open and running htop before you stop Node-red, to give an indication of CPU and memory use before it crashes.

[Trying_to_learn]

Thanks.

The power supply is ok. Originally it was a problem as it was for a Zero, and this is a 3B+

Now with the bigger supply all that side is ok.

[Bobo]

Have you actually checked (monitored) your wifi signal strength? If you are pushing the limits then events like these can sometimes be attributed to poor signal, especially on the 2.4 network which can become quite crowded.

[Trying_to_learn]

Thanks Bobo.

I hope this isn't the problem as there is only .... 2 (maybe 3) meters between the WAP and the Pi, and 1 thin brick wall.

[Trying_to_learn]

Oh, something I just realised....

Sorry folks. Busy day. New RasPi arrived, 'n' all.

So the new RasPi is to replace the one which died when I stopped NR.

I was going to stop NR before swapping them and..... forgot.

Powered down the old one.
Took out SD card.
Built new machine (new box/case) (and board)
Put in SD card, hooked up some jumper wires to an LED strip.

Booted.
All good.

(Just realised I am now talking about another machine.)
Argh.

Sorry.

But the new card is working fine.
I don't want to lock it up as it is headless and hard to reset/restart if it goes off reservation when I stop Node-Red.

I'm sure that in the future I will be needing to install newer nodes in NR and will require NR to be restarted.