Try
sudo journalctl -f -u nodered -o cat
Same result. Another instance of Node trying to start
which means it is happening.
kill all node-red and start service (or restart the device)
if it is still happening, something is firing up 2x instances
Achieved. Thank you. Now I have the results of the logs and, indeed, there is no warning of disconnection of the MQTT broker.
With sudo journalctl _PID=494 --no-pager
Jan 02 11:49:16 raspberrypi node-red-pi[494]: 2 Jan 11:49:16 - [info] [StoreNForward:Cola3] Queue now empty
Jan 02 11:49:16 raspberrypi node-red-pi[494]: 2 Jan 11:49:16 - [info] [StoreNForward:Cola1] Queue now empty
Jan 02 11:49:16 raspberrypi node-red-pi[494]: 2 Jan 11:49:16 - [info] [StoreNForward:Cola2] Queue now empty
So StoreNForward nodes are never informed of any disconnection
The exact behaviour is: when I restart the RPI and while it does not connect to wifi, StoreNFroward works as a champ storing data. In the moment MQTT out gets connection, never loses it. It worked in the past, I saw it working. Don't know what's different or changed.
I note that the command running there is node-red-pi, which means that you did not start node-red the same way that it is started by a reboot.
The usual way of stopping and restarting node-red on a pi is to use
node-red-stop
node-red-start
which starts it in the same way as is done by rebooting, and drops you into the log. You can use node-red-reload which does the same thing but which, for reasons which are unclear to me, sometimes misses the beginning of the log.
To see the log for a running system you can use
node-red-log
which effectively does
journalctl -u nodered -f
I suppose node-red-pi is an specific version optimized for RPI. It's the one installed by following Running on Raspberry Pi : Node-RED
Do you think has something to do with connected/disconnected status of MQTT out nodes?
Yes, and it is run by the systemd startup script, so whether you start it using that or starting the systemd script will probably not make any difference to this problem. The running environment will be different however, so it is better to use node-red-start to run it (after node-red-stop if it is already running).
Did you try setting up LWT on NR client ?
It would be a nice confirmation to see if the remote broker reports it as offline, when local wi-fi is turned off.
I am desperate and will pursue any avenue to find the solution but I cannot follow your logic: My MQTT broker is in a server in Ireland, how will it know about a wifi connected or disconnected at my office? I'm not sure but my problems seem to be local and probably related with MQTT out nodes configuration. Let's see what changes if I set up LWT
Because the device will stop sending regular comms to the broker. It can take a few minutes for the broker to detect the disconnect.
LWT messages have been configured as shown in the image,
It is added a new MQTT out node to check Equipo/LWT and a status node to check this MQTT out node. Also, with MyMQTT app in my mobile, I can check messages send to this topic
So if you disconnect the Wi-Fi, does the remote broker now show Equipo/LWT as offline ?
Correct. Even more, I have had the opportunity to restart the remote server and, in the meantime, I saw MQTT nodes indicating disconnected but StoreNForward nodes don't work. So, I have two problems: not detecting local disconnections and the nodes checking status
I'm afraid I'm struggling for ideas now 
Perhaps some smarter than me can help @knolleary @dceejay 
It seems likely it is something to do with your specific setup, as a general bug with MQTT would have been seen by 1000's of users.
You said it did work, but you don't know what changed, I think the only way forward is to try and figure out what did change.
Do you have other working remote sites you can compare with ?
My guess: I was developing in Node-RED v2.x.x and I have an âaccidentâ with both my computer and the RPI and I have to restart in v3.1.1 (importing my *.json backup). Something is different or some of the improvements between versions do not âfit meâ.
Anyway, thanks for your time and effort.
I knew you would "crack" eventually
How did you do the re-build, e.g. were all the custom nodes re installed or just copied ?
If you can post the full log when NR is started up, it may reveal some issue.
There's nothing interesting, in my opinion.
Jan 4 09:05:40 raspberrypi systemd[1]: Started Node-RED.
Jan 4 09:05:40 raspberrypi udisksd[431]: Failed to load the 'mdraid' libblockdev plugin
Jan 4 09:05:40 raspberrypi systemd[1]: Starting /etc/rc.local Compatibility...
Jan 4 09:05:40 raspberrypi systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped.
Jan 4 09:05:40 raspberrypi raspi-config[392]: Checking if shift key is held down:
Jan 4 09:05:40 raspberrypi raspi-config[484]: Device /dev/input/event1 not suitable.
Jan 4 09:05:40 raspberrypi systemd[1]: Starting OpenBSD Secure Shell server...
Jan 4 09:05:40 raspberrypi systemd[1]: Starting Permit User Sessions...
Jan 4 09:05:40 raspberrypi systemd[1]: Started VNC Server in Service Mode daemon.
Jan 4 09:05:40 raspberrypi rngd[499]: rngd 2.2 starting up...
Jan 4 09:05:40 raspberrypi systemd[1]: Started LSB: rng-tools (Debian variant).
Jan 4 09:05:40 raspberrypi systemd[1]: Started /etc/rc.local Compatibility.
Jan 4 09:05:40 raspberrypi systemd[1]: Finished Permit User Sessions.
Jan 4 09:05:40 raspberrypi systemd[1]: Started User Login Management.
Jan 4 09:05:40 raspberrypi rngd[499]: entropy feed to the kernel ready
Jan 4 09:05:40 raspberrypi avahi-daemon[359]: Server startup complete. Host name is raspberrypi.local. Local service cookie is 1948275580.
Jan 4 09:05:40 raspberrypi rpi-eeprom-update[398]: Skipping automatic bootloader upgrade. current 1643121041 >= min 1599135103
Jan 4 09:05:40 raspberrypi systemd[1]: Starting Light Display Manager...
Jan 4 09:05:40 raspberrypi systemd[1]: Starting Hold until boot process finishes up...
Jan 4 09:05:40 raspberrypi ModemManager[477]: <info> ModemManager (version 1.14.12) starting in system bus...
Jan 4 09:05:40 raspberrypi lightdm[505]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Jan 4 09:05:41 raspberrypi systemd[1]: Started Disk Manager.
Jan 4 09:05:41 raspberrypi systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 4 09:05:41 raspberrypi udisksd[431]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jan 4 09:05:41 raspberrypi systemd[1]: Starting Load/Save RF Kill Switch Status...
Jan 4 09:05:41 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 194 (plymouthd).
Jan 4 09:05:41 raspberrypi systemd[1]: Started OpenBSD Secure Shell server.
Jan 4 09:05:41 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 194 (plymouthd).
Jan 4 09:05:41 raspberrypi rpi-eeprom-update[398]: BOOTLOADER: up to date
Jan 4 09:05:41 raspberrypi rpi-eeprom-update[398]: CURRENT: Tue 25 Jan 14:30:41 UTC 2022 (1643121041)
Jan 4 09:05:41 raspberrypi dbus-daemon[361]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.9' (uid=0 pid=483 comm="/usr/sbin/cupsd -l ")
Jan 4 09:05:41 raspberrypi systemd[1]: Finished Hold until boot process finishes up.
Jan 4 09:05:41 raspberrypi rpi-eeprom-update[398]: LATEST: Wed 11 Jan 17:40:52 UTC 2023 (1673458852)
Jan 4 09:05:41 raspberrypi rpi-eeprom-update[398]: RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
Jan 4 09:05:41 raspberrypi rpi-eeprom-update[398]: Use raspi-config to change the release.
Jan 4 09:05:41 raspberrypi rpi-eeprom-update[398]: VL805_FW: Using bootloader EEPROM
Jan 4 09:05:41 raspberrypi rpi-eeprom-update[398]: VL805: up to date
Jan 4 09:05:41 raspberrypi rpi-eeprom-update[398]: CURRENT: 000138a1
Jan 4 09:05:41 raspberrypi rpi-eeprom-update[398]: LATEST: 000138a1
Jan 4 09:05:41 raspberrypi vncserver-x11[509,root]: ServerManager: Server started
Jan 4 09:05:41 raspberrypi systemd[1]: Finished Check for Raspberry Pi EEPROM updates.
Jan 4 09:05:41 raspberrypi systemd[1]: Started Light Display Manager.
Jan 4 09:05:41 raspberrypi raspi-config[392]: No. Switching to ondemand scaling governor.
Jan 4 09:05:41 raspberrypi systemd[1]: Starting Manage, Install and Generate Color Profiles...
Jan 4 09:05:41 raspberrypi systemd[1]: Started Getty on tty1.
Jan 4 09:05:41 raspberrypi systemd[1]: Reached target Login Prompts.
Jan 4 09:05:41 raspberrypi systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).
Jan 4 09:05:41 raspberrypi systemd[1]: Started Modem Manager.
Jan 4 09:05:41 raspberrypi systemd-udevd[179]: Using default interface naming scheme 'v247'.
Jan 4 09:05:41 raspberrypi systemd-udevd[184]: mouse0: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Jan 4 09:05:41 raspberrypi systemd-udevd[191]: event3: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Jan 4 09:05:41 raspberrypi systemd-udevd[187]: event4: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Jan 4 09:05:41 raspberrypi systemd[1]: Started Load/Save RF Kill Switch Status.
Jan 4 09:05:41 raspberrypi systemd-udevd[182]: event0: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Jan 4 09:05:41 raspberrypi systemd-udevd[190]: event1: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Jan 4 09:05:41 raspberrypi systemd[1]: Condition check resulted in Manage Sound Card State (restore and store) being skipped.
Jan 4 09:05:41 raspberrypi dhcpcd-run-hooks[613]: wlan0: starting wpa_supplicant
Jan 4 09:05:41 raspberrypi dbus-daemon[361]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Jan 4 09:05:41 raspberrypi systemd[1]: Starting Save/Restore Sound Card State...
Jan 4 09:05:41 raspberrypi systemd[1]: Started Manage, Install and Generate Color Profiles.
Jan 4 09:05:41 raspberrypi kernel: [ 9.452396] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
Jan 4 09:05:41 raspberrypi systemd[1]: Finished Save/Restore Sound Card State.
Jan 4 09:05:41 raspberrypi systemd[1]: Reached target Sound Card.
Jan 4 09:05:41 raspberrypi dhcpcd[403]: wlan0: connected to Access Point `'
Jan 4 09:05:41 raspberrypi dhcpcd[403]: wlan0: waiting for carrier
Jan 4 09:05:42 raspberrypi systemd[1]: Started CUPS Scheduler.
Jan 4 09:05:42 raspberrypi systemd[1]: Started Make remote CUPS printers available locally.
Jan 4 09:05:42 raspberrypi systemd[1]: Reached target Multi-User System.
Jan 4 09:05:42 raspberrypi systemd[1]: Reached target Graphical Interface.
Jan 4 09:05:42 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jan 4 09:05:42 raspberrypi systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Jan 4 09:05:42 raspberrypi systemd[1]: Finished Update UTMP about System Runlevel Changes.
Jan 4 09:05:42 raspberrypi systemd[1]: Startup finished in 2.155s (kernel) + 7.782s (userspace) = 9.937s.
Jan 4 09:05:42 raspberrypi vncserver-x11[509,root]: ConsoleDisplay: Cannot find a running X server on vt1
Jan 4 09:05:42 raspberrypi vncserver-x11[509,root]: ConsoleDisplay: Found running X server (pid=561, binary=/usr/lib/xorg/Xorg)
Jan 4 09:05:42 raspberrypi systemd[1]: Created slice User Slice of UID 1000.
Jan 4 09:05:42 raspberrypi systemd[1]: Starting User Runtime Directory /run/user/1000...
Jan 4 09:05:42 raspberrypi systemd[1]: Finished User Runtime Directory /run/user/1000.
Jan 4 09:05:42 raspberrypi systemd[1]: Starting User Manager for UID 1000...
Jan 4 09:05:42 raspberrypi vncserver-x11[509,root]: HostedRendezvous: Rendezvous lookup failed: Hosted Bootstrap error: Network failure: Error connecting: getaddrinfo: 'Temporary failure in name resolution' (-3)
Jan 4 09:05:43 raspberrypi systemd[653]: Queued start job for default target Main User Target.
Jan 4 09:05:44 raspberrypi dbus-daemon[361]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.21' (uid=1000 pid=669 comm="/usr/bin/pipewire ")
Jan 4 09:05:44 raspberrypi systemd[653]: Created slice User Application Slice.
Jan 4 09:05:44 raspberrypi dbus-daemon[361]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Jan 4 09:05:44 raspberrypi systemd[653]: Reached target Paths.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Successfully called chroot.
Jan 4 09:05:44 raspberrypi systemd[653]: Reached target Timers.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Successfully dropped privileges.
Jan 4 09:05:44 raspberrypi systemd[653]: Starting D-Bus User Message Bus Socket.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Successfully limited resources.
Jan 4 09:05:44 raspberrypi systemd[653]: Listening on GnuPG network certificate management daemon.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Running.
Jan 4 09:05:44 raspberrypi systemd[653]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Watchdog thread running.
Jan 4 09:05:44 raspberrypi systemd[653]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Canary thread running.
Jan 4 09:05:44 raspberrypi systemd[653]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 4 09:05:44 raspberrypi ModemManager[477]: <info> [base-manager] couldn't check support for device '/sys/devices/platform/scb/fd580000.ethernet': not supported by any plugin
Jan 4 09:05:44 raspberrypi systemd[653]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 4 09:05:44 raspberrypi ModemManager[477]: <info> [base-manager] couldn't check support for device '/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4': not supported by any plugin
Jan 4 09:05:44 raspberrypi systemd[653]: Listening on Multimedia System.
Jan 4 09:05:44 raspberrypi ModemManager[477]: <info> [base-manager] couldn't check support for device '/sys/devices/platform/soc/fe300000.mmcnr/mmc_host/mmc1/mmc1:0001/mmc1:0001:1': not supported by any plugin
Jan 4 09:05:44 raspberrypi systemd[653]: Listening on debconf communication socket.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Successfully made thread 669 of process 669 owned by '1000' high priority at nice level -11.
Jan 4 09:05:44 raspberrypi systemd[653]: Listening on Sound System.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 1 threads of 1 processes of 1 users.
Jan 4 09:05:44 raspberrypi systemd[653]: Listening on D-Bus User Message Bus Socket.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Successfully made thread 670 of process 670 owned by '1000' high priority at nice level -11.
Jan 4 09:05:44 raspberrypi systemd[653]: Reached target Sockets.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 2 threads of 2 processes of 1 users.
Jan 4 09:05:44 raspberrypi systemd[653]: Reached target Basic System.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 2 threads of 2 processes of 1 users.
Jan 4 09:05:44 raspberrypi systemd[1]: Started User Manager for UID 1000.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 2 threads of 2 processes of 1 users.
Jan 4 09:05:44 raspberrypi systemd[1]: Started Session 1 of user gesinne.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Successfully made thread 673 of process 669 owned by '1000' RT at priority 20.
Jan 4 09:05:44 raspberrypi systemd[653]: Started Multimedia Service.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 3 threads of 2 processes of 1 users.
Jan 4 09:05:44 raspberrypi systemd[653]: Starting Sound Service...
Jan 4 09:05:44 raspberrypi systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Jan 4 09:05:44 raspberrypi systemd[1]: Started RealtimeKit Scheduling Policy Service.
Jan 4 09:05:44 raspberrypi systemd[653]: Started D-Bus User Message Bus.
Jan 4 09:05:44 raspberrypi pipewire[669]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Successfully made thread 688 of process 688 owned by '1000' high priority at nice level -11.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 4 threads of 3 processes of 1 users.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 4 threads of 3 processes of 1 users.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 4 threads of 3 processes of 1 users.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Successfully made thread 689 of process 688 owned by '1000' RT at priority 20.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 5 threads of 3 processes of 1 users.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 5 threads of 3 processes of 1 users.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Successfully made thread 690 of process 670 owned by '1000' RT at priority 5.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 6 threads of 3 processes of 1 users.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 6 threads of 3 processes of 1 users.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Successfully made thread 691 of process 670 owned by '1000' RT at priority 5.
Jan 4 09:05:44 raspberrypi rtkit-daemon[674]: Supervising 7 threads of 3 processes of 1 users.
Jan 4 09:05:44 raspberrypi pulseaudio[670]: Failed to find a working profile.
Jan 4 09:05:44 raspberrypi pulseaudio[670]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="platform-fef05700.hdmi" card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=no fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
Jan 4 09:05:44 raspberrypi dbus-daemon[361]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.29' (uid=1000 pid=670 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")
Jan 4 09:05:44 raspberrypi systemd[1]: Condition check resulted in Bluetooth service being skipped.
Jan 4 09:05:44 raspberrypi systemd[653]: Started Sound Service.
Jan 4 09:05:44 raspberrypi systemd[653]: Reached target Main User Target.
Jan 4 09:05:44 raspberrypi systemd[653]: Startup finished in 1.962s.
Jan 4 09:05:46 raspberrypi lightdm[714]: screen 0: 1024x768 269x202 mm 96.46dpi
Jan 4 09:05:46 raspberrypi lightdm[714]: crtc 0: 1024x768 75.03 +0+0 "HDMI-1"
Jan 4 09:05:46 raspberrypi lightdm[717]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Jan 4 09:05:46 raspberrypi systemd[1]: Started Session 3 of user gesinne.
Jan 4 09:05:46 raspberrypi pulseaudio[670]: Failed to find a working profile.
Jan 4 09:05:46 raspberrypi pulseaudio[670]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="platform-fef05700.hdmi" card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=no fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
Jan 4 09:05:46 raspberrypi node-red-pi[488]: 4 Jan 09:05:46 - [info]
Jan 4 09:05:46 raspberrypi node-red-pi[488]: Welcome to Node-RED
Jan 4 09:05:46 raspberrypi node-red-pi[488]: ===================
Jan 4 09:05:46 raspberrypi node-red-pi[488]: 4 Jan 09:05:46 - [info] Node-RED version: v3.1.3
Jan 4 09:05:46 raspberrypi node-red-pi[488]: 4 Jan 09:05:46 - [info] Node.js version: v18.19.0
Jan 4 09:05:46 raspberrypi node-red-pi[488]: 4 Jan 09:05:46 - [info] Linux 6.1.21-v8+ arm LE
Jan 4 09:05:46 raspberrypi systemd[1]: systemd-rfkill.service: Succeeded.
Jan 4 09:05:47 raspberrypi dhcpcd[403]: wlan0: carrier acquired
Jan 4 09:05:47 raspberrypi dhcpcd[403]: wlan0: connected to Access Point `Ingenieria'
Jan 4 09:05:47 raspberrypi kernel: [ 14.777242] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 4 09:05:47 raspberrypi dhcpcd[403]: DUID 00:01:00:01:2b:e4:69:21:2a:ef:ce:db:f4:ae
Jan 4 09:05:47 raspberrypi dhcpcd[403]: wlan0: IAID 01:b2:2e:47
Jan 4 09:05:47 raspberrypi dhcpcd[403]: wlan0: adding address fe80::86d:2705:6697:e936
Jan 4 09:05:47 raspberrypi avahi-daemon[359]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::86d:2705:6697:e936.
Jan 4 09:05:47 raspberrypi avahi-daemon[359]: New relevant interface wlan0.IPv6 for mDNS.
Jan 4 09:05:47 raspberrypi avahi-daemon[359]: Registering new address record for fe80::86d:2705:6697:e936 on wlan0.*.
Jan 4 09:05:47 raspberrypi dhcpcd[403]: wlan0: soliciting an IPv6 router
Jan 4 09:05:47 raspberrypi dhcpcd[403]: wlan0: rebinding lease of 192.168.0.129
Jan 4 09:05:47 raspberrypi dhcpcd[403]: wlan0: probing address 192.168.0.129/24
Jan 4 09:05:48 raspberrypi vncserver-x11[509,root]: HostedRendezvous: Rendezvous lookup failed: Hosted Bootstrap error: Network failure: Error connecting: getaddrinfo: 'Temporary failure in name resolution' (-3)
Jan 4 09:05:48 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.6' (uid=1000 pid=721 comm="/usr/bin/lxsession -s LXDE-pi -e LXDE -w openbox-l")
Jan 4 09:05:48 raspberrypi systemd[653]: Starting Virtual filesystem service...
Jan 4 09:05:49 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Successfully activated service 'org.gtk.vfs.Daemon'
Jan 4 09:05:49 raspberrypi systemd[653]: Started Virtual filesystem service.
Jan 4 09:05:50 raspberrypi node-red-pi[488]: 4 Jan 09:05:50 - [info] Loading palette nodes
Jan 4 09:05:50 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.10' (uid=1000 pid=842 comm="pcmanfm --desktop --profile LXDE-pi ")
Jan 4 09:05:50 raspberrypi systemd[653]: Starting Virtual filesystem service - disk device monitor...
Jan 4 09:05:51 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Jan 4 09:05:51 raspberrypi systemd[653]: Started Virtual filesystem service - disk device monitor.
Jan 4 09:05:51 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.10' (uid=1000 pid=842 comm="pcmanfm --desktop --profile LXDE-pi ")
Jan 4 09:05:51 raspberrypi systemd[653]: Starting Virtual filesystem service - digital camera monitor...
Jan 4 09:05:51 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Jan 4 09:05:51 raspberrypi systemd[653]: Started Virtual filesystem service - digital camera monitor.
Jan 4 09:05:51 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.10' (uid=1000 pid=842 comm="pcmanfm --desktop --profile LXDE-pi ")
Jan 4 09:05:51 raspberrypi systemd[653]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Jan 4 09:05:51 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Jan 4 09:05:51 raspberrypi systemd[653]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Jan 4 09:05:51 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.10' (uid=1000 pid=842 comm="pcmanfm --desktop --profile LXDE-pi ")
Jan 4 09:05:51 raspberrypi systemd[653]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Jan 4 09:05:51 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Jan 4 09:05:51 raspberrypi systemd[653]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Jan 4 09:05:51 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.10' (uid=1000 pid=842 comm="pcmanfm --desktop --profile LXDE-pi ")
Jan 4 09:05:51 raspberrypi systemd[653]: Starting Virtual filesystem service - Apple File Conduit monitor...
Jan 4 09:05:51 raspberrypi dbus-daemon[687]: [session uid=1000 pid=687] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Jan 4 09:05:51 raspberrypi systemd[653]: Started Virtual filesystem service - Apple File Conduit monitor.
Jan 4 09:05:52 raspberrypi dhcpcd[403]: wlan0: leased 192.168.0.129 for 600 seconds
Jan 4 09:05:52 raspberrypi avahi-daemon[359]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.129.
Jan 4 09:05:52 raspberrypi dhcpcd[403]: wlan0: adding route to 192.168.0.0/24
Jan 4 09:05:52 raspberrypi dhcpcd[403]: wlan0: adding default route via 192.168.0.253
Jan 4 09:05:52 raspberrypi avahi-daemon[359]: New relevant interface wlan0.IPv4 for mDNS.
Jan 4 09:05:52 raspberrypi avahi-daemon[359]: Registering new address record for 192.168.0.129 on wlan0.IPv4.
Jan 4 09:05:52 raspberrypi dbus-daemon[361]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.38' (uid=1000 pid=839 comm="lxpanel --profile LXDE-pi ")
Jan 4 09:05:52 raspberrypi systemd[1]: Starting PackageKit Daemon...
Jan 4 09:05:52 raspberrypi PackageKit: daemon start
Jan 4 09:05:53 raspberrypi dbus-daemon[361]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jan 4 09:05:53 raspberrypi systemd[1]: Started PackageKit Daemon.
Jan 4 09:05:55 raspberrypi node-red-pi[488]: 4 Jan 09:05:55 - [info] Dashboard version 3.6.2 started at /ui
Jan 4 09:05:56 raspberrypi node-red-pi[488]: 4 Jan 09:05:56 - [info] Settings file : /home/gesinne/.node-red/settings.js
Jan 4 09:05:56 raspberrypi node-red-pi[488]: 4 Jan 09:05:56 - [info] Context store : 'default' [module=memory]
Jan 4 09:05:56 raspberrypi node-red-pi[488]: 4 Jan 09:05:56 - [info] User directory : /home/gesinne/.node-red
Jan 4 09:05:56 raspberrypi node-red-pi[488]: 4 Jan 09:05:56 - [warn] Projects disabled : editorTheme.projects.enabled=false
Jan 4 09:05:56 raspberrypi node-red-pi[488]: 4 Jan 09:05:56 - [info] Flows file : /home/gesinne/.node-red/flows.json
Jan 4 09:05:56 raspberrypi node-red-pi[488]: 4 Jan 09:05:56 - [info] Server now running at http://127.0.0.1:1880/
Jan 4 09:05:56 raspberrypi PackageKit: refresh-cache transaction /102_eeacadac from uid 1000 finished with success after 3266ms
Jan 4 09:05:56 raspberrypi node-red-pi[488]: 4 Jan 09:05:56 - [info] Starting flows
Jan 4 09:05:57 raspberrypi node-red-pi[488]: 4 Jan 09:05:57 - [info] Started flows
Jan 4 09:05:57 raspberrypi node-red-pi[488]: 4 Jan 09:05:57 - [warn] [modbus-flex-getter:Tarjeta1] Flex-Getter -> Inject while node is not ready for input.
Jan 4 09:05:57 raspberrypi node-red-pi[488]: 4 Jan 09:05:57 - [info] [mqtt-broker:Elastic] Connected to broker: mqtt://52.169.183.190:1883
Jan 4 09:05:57 raspberrypi node-red-pi[488]: 4 Jan 09:05:57 - [info] [StoreNForward:Cola3] Processing messages in queue
Jan 4 09:05:57 raspberrypi node-red-pi[488]: 4 Jan 09:05:57 - [info] [StoreNForward:Cola3] Opened /home/gesinne/cola3 successfully.
Jan 4 09:05:57 raspberrypi node-red-pi[488]: 4 Jan 09:05:57 - [info] [StoreNForward:Cola1] Processing messages in queue
Jan 4 09:05:57 raspberrypi node-red-pi[488]: 4 Jan 09:05:57 - [info] [StoreNForward:Cola1] Opened /home/gesinne/cola1 successfully.
Jan 4 09:05:57 raspberrypi node-red-pi[488]: 4 Jan 09:05:57 - [info] [StoreNForward:Cola2] Processing messages in queue
Jan 4 09:05:57 raspberrypi node-red-pi[488]: 4 Jan 09:05:57 - [info] [StoreNForward:Cola2] Opened /home/gesinne/cola2 successfully.
Jan 4 09:05:57 raspberrypi node-red-pi[488]: 4 Jan 09:05:57 - [warn] [modbus-flex-getter:Tarjeta2] Flex-Getter -> Inject while node is not ready for input.
Jan 4 09:05:58 raspberrypi node-red-pi[488]: 4 Jan 09:05:58 - [info] [StoreNForward:Cola2] Queue now empty
Did you try opening a command window alongside the browser and running node-red-log in the command window, then disconnecting the network and see what appears in the log and the editor?
Yes, some days ago. Only messages related with modbus or storenforward queues; nothing that could have anything to do with connections.
If you repeat that, disconnect the network and leave it for 5 mins and then reconnect the network, what do you see in the log when you reconnect it? Note the time at which you disconnected so we can reference the log timestamps correctly.
