WeatherLink IP Stopped Connecting

[DesertRat]

My Cumulus 3.11.4 (build 3133) stopped receiving station data after changing out my Ubiquiti Edge Router and installing a Fortinet 30E. The WeatherLink IP and my pi aren't even plugged directly into the Fortinet. They are plugged into separate dumb Linksys switches on the same LAN that they have always been plugged into. The only thing the Edge Router and now Fortinet provided/provides for this equation is DHCP. The IP lease reservations did not change. The same IP reservations via MAC Addresses were created on the Fortinet. CumulusMX is not sending anything to weatherlink.com. So there should not be anything competing with Cumulus connectivity to the WLIP datalogger. I have tried multiple times powering off the VantagePro2 Console and removing the batteries thus resetting the datalogger. Waiting for the VP2 Console to stop receiving the updated data, then rebooting the pi and then starting CumulusMX via command line using putty/SSH. I have no problems getting to the Cumulus Web GUI on port 8998. I can get to all the setting pages. I can turn logging and debugging on and off in the GUI under Program Settings. I even tried statically assigning the WeatherLink IP to an IP address outside the DHCP scope. It didn't make a difference. No matter what I do, this is what I get over and over in the MXdiags:

2021-06-22 07:08:27.463 SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.
2021-06-22 07:08:27.463 SendLoopCommand: Attempting to reconnect to station
2021-06-22 07:08:27.463 InitTCP: Connecting to the station
2021-06-22 07:08:27.464 OpenTcpPort: TCP Logger Connect attempt 1
2021-06-22 07:08:28.466 OpenTcpPort: TCP Logger reconnected
2021-06-22 07:08:28.466 InitTCP: Flushing input stream
2021-06-22 07:08:28.467 InitTCP: Sending TEST (1) command
2021-06-22 07:08:28.467 InitTCP: TEST (1) received - ''
2021-06-22 07:08:28.467 InitTCP: Sending TEST (2) command
2021-06-22 07:08:28.467 InitTCP: TEST (2) received - ''
2021-06-22 07:08:28.467 InitTCP: Sending TEST (3) command
2021-06-22 07:08:28.467 InitTCP: TEST (3) received - ''
2021-06-22 07:08:28.468 InitTCP: Sending TEST (4) command
2021-06-22 07:08:28.468 InitTCP: TEST (4) received - ''
2021-06-22 07:08:28.468 SendLoopCommand: Reconnected to station
2021-06-22 07:08:28.468 SendLoopCommand: Starting - LPS 2 1
2021-06-22 07:08:28.468 SendLoopCommand: Sending command - LPS 2 1, attempt 1
2021-06-22 07:08:28.468 SendLoopCommand: Wait for ACK
2021-06-22 07:08:28.469 WaitForACK: Starting
2021-06-22 07:08:31.048 WaitForAck: 1 Error - Unable to read data from the transport connection: Operation on non-blocking socket would block.

Before I blow away my pi installation and start over, what could I be missing here?

[PaulMy]

CumulusMX is not sending anything to weatherlink.com.

Cumulus does not send any data to Weatherlink.com!
In normal WLIP logger and CumulusMX running, the disconnect settings in CumulusMX would allow for the WLIPlogger to connect to CumulusMX, and WLIPlogger send to Weatherlink.com. But you would need to have the correct settings in WLIPlogger including IPaddress so it can send to Weatherlink.com, and you would then also use that IPaddress in CumulusMX settings as well.

Enjoy,
Paul

[freddie]

My money would be on your router causing the problem. Possibly blocking the particular Comms required to your weather station. @mcrossley will be able to advise a bit better than me, but I think it's a particular protocol that is being blocked.

[DesertRat]

My money would be on your router causing the problem. Possibly blocking the particular Comms required to your weather station. @mcrossley will be able to advise a bit better than me, but I think it's a particular protocol that is being blocked.

The router isn't the issue. Like I mentioned in my original post. The router doesn't handle their local LAN traffic. They are sitting on the same LAN connected to dumb Linksys switches. The router would be an issue, if I couldn't send the data to CWOP and Wunderground outbound to the Internet.

FYI, I also have a separate console with another Weatherlink IP connecting directly to weatherlink.com. That setup is on the same dumb switches and going outbound through the router. No problems there. I'm only having this issue with CumulusMX and a different Weatherlink IP. (Paul didn't understand that in my case, I'm just not sending data to weatherlink.com on my CumulusMX setup)

Freddie, You have given me an idea though. I may turn off weatherlink.com temporarily on the other WLIP and point CumulusMX at it and see if can get station data from it. That would at least eliminate a bad WLIP on the problematic side.

[DesertRat]

No go on the other Weatherlink IP. Same connection errors for both WLIP on CumulusMX 3.11.46 (build 3133). It was worth a shot. It does tell me that the problem lies with my pi CumulusMX install though.

[freddie]

The router doesn't handle their local LAN traffic.

Is the dumb switch connected to the router? What do the two devices have set as gateway?

[DesertRat]

The router doesn't handle their local LAN traffic.

Is the dumb switch connected to the router? What do the two devices have set as gateway?

The IP loggers use the LAN address on the router. The dumb switches don't have configurations for gateway. They are auto uplink. The LAN side of the router is passive for local LAN traffic.

[DesertRat]

Well just to make sure the new router wasn't part of the problem, which I was 98% sure it wasn't, I put the old router back in place and everything else like it was before. Problem still present. Something in my Cumulus installation is corrupt.

[DesertRat]

Well after seriously considering throwing Cumulus out with the bath water and moving on to something else. In desperation, I took another Pi out of the drawer, because everyone has a half a dozen of those laying around right? I flashed it with Mark's CMX Pi Image and then unzipped 3.11.4 (b3133) over the top. However, even with a fresh image, I was having the same issue. I started configuring the VP2Pro station in the GUI for the 2nd time. Yes, I flashed a SD card twice. I stumbled upon this in the Davis settings: Set the Davis Logger interval to match Cumulus MX interval

WARNING: This will clear all data from your logger if it is invoked.

If the Davis logger interval does not match the Cumulus interval, set it to match.

Requires a restart of Cumulus MX

I thought what the heck, at this point I don't have anything to lose. So I checked the box and saved the settings. I issued the restart CMX command on the Pi and then I tailed the latest active file in MXdiags. Well what do you know, the logger started ignoring its Archives and purged itself. Once it finished, with the purge CMX started receiving current data from the console/VP2Pro. I am back in business. This is the first time I have seen this issue and hope I never see it again.

[mcrossley]

It does sound like the IP Logger had got itself into some sort of corrupted state. It does happen v. v. occasionally (same with the USB logger) and the reset of the logging interval which resets all its internal pointers seems to clear it out.