Raspberry crashs after Deploy - Resolved

General
1

First, I original posted this issue on the Raspberry forum thinking I was looking at problem with Raspberry OS. But as continue testing I wondering if issue was with node-red, So here is my problem.

First little on my configuration, so individuals will understand now got to were I am. I have two raspberry's....

Raspberry1 (crashing) Node-red, Mosquitto client.... node-red running home alarm systems (garage door opener/sensors, cameras, motion sensor etc.)
Raspberry2 Node-red, Mosquitto Broker.... node-red is running integration of stereo, tv, media server etc.

Both Raspberry's running node-red version 3.0.2, Raspberry OS version 10(Buster)

To help track when then Raspberry1 crashes I added script in crontab to warn me when ever the system reboots and script to log Raspberry temperatures and check for throttling... System is running around 61C but no throttling is occurring.

I then continue testing node-red flows on Raspberry2.... Total unexpectedly every time I request node-red to deploy changes on Raspberry2.... Raspberry1 would crash.....

The only thing in common between the two Raspberry's is the Mosquitto broker.....

But why would Raspberry2 cause Raspberry1 to crash????

If anyone got any ideas please let me know...

2

Welcome to the forum @mark31

Run, in a command window,
node-red-log
Which will show you the node red log. Leave that window open and make node red crash. Hopefully the log will show something useful.

Copy/paste the log here, not screenshot please.

3

I have now realised that you are saying that the pi reboots.
If that is the case then you can look in /var/log/syslog after it reboots and scroll back to the start of the reboot and you should see why it rebooted.

[Edit] Are you running the PIs off good quality power supplies?

4

I have been looking at the syslog for several days now there is there is no pattern (that I see) except the message:

"raspberry1 systemd-modules-load[116]: Inserted module 'i2c_dev'

that shows up just prior:

raspberry1 kernel: [ 0.000000] Booting Linux on physical CPU 0x0

some time they will be consecutive messages, other times not. On crashes with messages separating the two messages listed above, number of messages varies depending on each individual crashes. I attach section from one crash... I am hoping another set of eyes will see something...

Jul 8 14:06:47 raspberry1 pulseaudio[843]: E: [alsa-sink-bcm2835 HDMI 1] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Jul 8 14:10:01 raspberry1 CRON[8026]: (pi) CMD (/usr/bin/mosquitto_pub -h 192.168.1.226 -m $(vcgencmd measure_temp) -r -t status/raspberry1 -u yeibqbxp -P "Mx-CWr_xrycZ" -p 1883)
Jul 8 14:10:01 raspberry1 CRON[8027]: (pi) CMD (/usr/bin/mosquitto_pub -h 192.168.1.226 -m $(vcgencmd get_throttled) -r -t status/raspberry1 -u yeibqbxp -P "Mx-CWr_xrycZ" -p 1883)
Jul 8 14:13:34 raspberry1 systemd[1]: session-10.scope: Succeeded.
Jul 8 14:13:59 raspberry1 kernel: [ 2755.104247] OF: overlay: WARNING: memory leak will occur if overlay removed, property: /soc/i2c@7e804000/status
Jul 8 14:14:20 raspberry1 systemd[1]: session-9.scope: Succeeded.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped target Timers.
Jul 8 14:14:28 raspberry1 systemd[1]: apt-daily-upgrade.timer: Succeeded.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped Daily apt upgrade and clean activities.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping Session 4 of user pi.
Jul 8 14:14:28 raspberry1 systemd[1]: Condition check resulted in Turns off Raspberry Pi display backlight on shutdown/reboot being skipped.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped target RPC Port Mapper.
Jul 8 14:14:28 raspberry1 systemd[1]: systemd-rfkill.socket: Succeeded.
Jul 8 14:14:28 raspberry1 systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping Session 6 of user pi.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping NFS status monitor for NFSv2/3 locking....
Jul 8 14:14:28 raspberry1 systemd[1]: Removed slice system-bthelper.slice.
Jul 8 14:14:28 raspberry1 systemd[1]: apt-daily.timer: Succeeded.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped Daily apt download activities.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping Authorization Manager...
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Jul 8 14:14:28 raspberry1 systemd[1]: logrotate.timer: Succeeded.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped Daily rotation of log files.
Jul 8 14:14:28 raspberry1 systemd[1]: systemd-tmpfiles-clean.timer: Succeeded.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Jul 8 14:14:28 raspberry1 systemd[1]: Unmounting RPC Pipe File System...
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped target Sound Card.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped target Graphical Interface.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping Disk Manager...
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping Light Display Manager...
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped target Multi-User System.
Jul 8 14:14:28 raspberry1 systemd[1]: gldriver-test.service: Succeeded.
Jul 8 14:14:28 raspberry1 systemd[699]: run-rpc_pipefs.mount: Succeeded.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped Check for v3d driver.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped target Login Prompts.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping Mosquitto MQTT v3.1/v3.1.1 Broker...
Jul 8 14:14:28 raspberry1 udisksd[409]: udisks daemon version 2.8.1 exiting
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping OpenBSD Secure Shell server...
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping Node-RED graphical event wiring tool...
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping dphys-swapfile - set up, mount/unmount, and delete a swap file...
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping AnyDesk...
Jul 8 14:14:28 raspberry1 systemd[1]: Stopping rng-tools.service...
Jul 8 14:14:28 raspberry1 systemd[1]: rpi-eeprom-update.service: Succeeded.
Jul 8 14:14:28 raspberry1 systemd[1]: Stopped Check for Raspberry Pi EEPROM updates.
Jul 8 14:14:36 raspberry1 systemd-modules-load[110]: Inserted module 'i2c_dev'
Jul 8 14:14:36 raspberry1 kernel: [ 0.000000] Booting Linux on physical CPU 0x0
Jul 8 14:14:36 raspberry1 kernel: [ 0.000000] Linux version 5.10.103-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1529 SMP Tue Mar 8 12:21:37 G$

5

Problem located in flow on raspberry2.

The flow in question was designed to toggle a power relay for raspberry 1, if the raspberry 1 stopped responding. For some reason the flow is now sending toggle command on every deploy command.

As some one had suggested, I was beginning to think the OS on the SD card was corrupted in some way...

6

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