Cumulus Support

Randomly noticed my station wasn't uploading the other day. Getting the following errors. I can ping the WLIP, but can't get to the webpage for some reason. I can see the logger on the network via the firmware tool though. Happened right around 6PM the one day, time doesn't seem to be afactor though.

2020-09-09 17:55:00.957 Writing log entry for 9/9/2020 5:55:00 PM
2020-09-09 17:55:00.958 Written log entry for 9/9/2020 5:55:00 PM
2020-09-09 17:55:00.961 Writing today.ini, LastUpdateTime = 9/9/2020 5:55:00 PM raindaystart = 2.1 rain counter = 2.1
2020-09-09 17:55:00.963 Updating CWOP
2020-09-09 17:55:09.036 Reading reception stats
2020-09-09 17:55:10.287 SendLoopCommand: Starting - LPS 2 1
2020-09-09 17:55:11.553 SendLoopCommand: Starting - LOOP 50
2020-09-09 17:56:47.406 SendLoopCommand: Starting - LPS 2 1
2020-09-09 17:56:48.673 SendLoopCommand: Starting - LOOP 50
2020-09-09 17:58:25.031 SendLoopCommand: Starting - LPS 2 1
2020-09-09 17:58:26.256 SendLoopCommand: Starting - LOOP 50
2020-09-09 18:00:00.990 Hour changed:18
2020-09-09 18:00:00.991 Calculating sunrise and sunset times
2020-09-09 18:00:00.991 Sunrise: 06:28:42
2020-09-09 18:00:00.991 Sunset : 19:15:03
2020-09-09 18:00:00.992 Tomorrow sunrise: 06:29:47
2020-09-09 18:00:00.992 Tomorrow sunset : 19:13:15
2020-09-09 18:00:00.994 Writing log entry for 9/9/2020 6:00:00 PM
2020-09-09 18:00:00.995 Written log entry for 9/9/2020 6:00:00 PM
2020-09-09 18:00:00.998 Writing today.ini, LastUpdateTime = 9/9/2020 6:00:00 PM raindaystart = 2.1 rain counter = 2.1
2020-09-09 18:00:01.000 Updating CWOP
2020-09-09 18:00:03.133 SendLoopCommand: Starting - LPS 2 1
2020-09-09 18:00:04.372 SendLoopCommand: Starting - LOOP 50
2020-09-09 18:00:08.200 InitTCP: Connecting to the station
2020-09-09 18:02:00.007 *** Data input appears to have stopped
2020-09-09 18:02:22.440 OpenTcpPort: Error - Connection timed out
2020-09-09 18:02:25.560 OpenTcpPort: Error - No route to host
2020-09-09 18:02:28.680 OpenTcpPort: Error - No route to host
2020-09-09 18:02:31.800 OpenTcpPort: Error - No route to host
2020-09-09 18:02:34.920 OpenTcpPort: Error - No route to host
2020-09-09 18:02:34.921 InitTCP: Failed to connect to the station, waiting 30 seconds before trying again
2020-09-09 18:03:00.008 *** Data input appears to have stopped

Noticed it today and rebooted the console/logger... got this error...

2020-09-11 12:04:46.761 InitTCP: Connecting to the station
2020-09-11 12:04:49.630 InitTCP: Flushing input stream
2020-09-11 12:04:56.215 InitTCP: Connection confirmed
2020-09-11 12:04:56.216 InitTCP: Connecting to the station
2020-09-11 12:04:57.237 InitTCP: Flushing input stream
2020-09-11 12:05:00.594 *** Data input appears to have stopped
2020-09-11 12:05:01.660 InitTCP: Connection confirmed
2020-09-11 12:05:01.661 SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.
2020-09-11 12:05:01.676 InitTCP: Connecting to the station
2020-09-11 12:05:02.679 InitTCP: Flushing input stream
2020-09-11 12:05:07.102 InitTCP: Connection confirmed
2020-09-11 12:05:07.103 Reading reception stats
2020-09-11 12:05:07.839 SendLoopCommand: Starting - LPS 2 1
2020-09-11 12:05:09.103 SendLoopCommand: Starting - LOOP 50
2020-09-11 12:05:13.418 LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2020-09-11 12:05:15.961 LOOP: Receive error - System.IO.IOException: Unable to read data from the transport connection: Operation on non-blocking socket would block. ---> System.Net.Sockets.SocketException: Operation on non-blocking socket would block
at System.Net.Sockets.Socket.Receive (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags) [0x00016] in <4e15bbae9d7043d8afd6cfd50bd9bd5a>:0
at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x00065] in <4e15bbae9d7043d8afd6cfd50bd9bd5a>:0
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x000ac] in <4e15bbae9d7043d8afd6cfd50bd9bd5a>:0
at CumulusMX.DavisStation.GetAndProcessLoopData (System.Int32 number) [0x002fe] in <d97b46a9374140afa4f3f7719413e0ab>:0
2020-09-11 12:05:15.962 LOOP: Reconnecting to station
2020-09-11 12:05:15.963 InitTCP: Connecting to the station


Also after a reboot of the pi, another unhandled exception...

2020-09-11 12:30:07.368 OpenTcpPort: Error - Connection refused
2020-09-11 12:30:07.368 InitTCP: Failed to connect to the station, waiting 30 seconds before trying again
2020-09-11 12:30:37.368 InitTCP: Connecting to the station
2020-09-11 12:30:37.371 OpenTcpPort: Error - Connection refused
2020-09-11 12:30:37.374 OpenTcpPort: Error - Connection refused
2020-09-11 12:30:37.377 OpenTcpPort: Error - Connection refused
2020-09-11 12:30:37.380 OpenTcpPort: Error - Connection refused
2020-09-11 12:30:37.383 OpenTcpPort: Error - Connection refused
2020-09-11 12:30:37.383 InitTCP: Failed to connect to the station, waiting 30 seconds before trying again
!!! Unhandled Exception !!!

Rebooting both the console and the raspberry pi/cumulusmx seem to be the only way to get the connection back up for now. Not really sure what's going on here. Help?

I'll grab the MXDiags later... forgot to mention versions. v1.15 on the logger, 3.80 on the wireless console and the latest and greatest on cumulus 3.8.3 (b3093) Network connection seems fine for both the pi and logger, regardless of cumulus saying it can't connect.

Well, that will be for Mark when he gets back, but for what it's worth: 1.15 for the logger is - I believe - quite old.

1.1.5 was released in Jan 2020 by the looks of it? Unless I'm missing something.

No, probably me. Confused with the console firmware.
Don't know about the logger.

HansR wrote: ↑Fri 11 Sep 2020 7:58 pm 1.15 for the logger is - I believe - quite old.

You must be thinking of something else - for the IP logger v1.15 (also sometimes written as v1.1.5) is the latest available F/W. TBH I wouldn't expect anything newer to be released now that the IP logger has been discontinued, but you never know - conceivably some new important bug might come to light.

So is this going to be an issue with the davis datalogger or CumulusMX? It seems the only way I can get this to work is to pull the power and batteries from the console, essentially rebooting the datalogger. Then restarting the software on the Pi... then it grabs the archives and starts running normally...

The weatherlinkip can only handle one connection at a time to the device. even when you run a ping, you maybe disconnecting another device or stopping it from reporting back to weatherlink.com. Hense why Davis dropped this device I guess and now has the WLL which will allow multiple connections to the device at the same time. if you are uploading to wl.com and using cumulus to connect make sure CumulusMX disconnects the session using the "Disconnect period" in Station Settings, TCP/IP Settings, Disconnect period.

I do not know the exact requirements of this setting perhaps someone with more knowledge can advise.

Also the Eithernet on the WLIP is 10TX/Half. I would make sure you set the ethernet port on the switch to the same (if you can) and do not ping and open a web browser session, and have cumulus and wl all connecting to thr WLIP at the same time. that is then "4" sessions which it cannot handle.

if you want a better device there is only one. the WLL - WeatherLink Live

Ok solid info... explains why I can't get to the settings page while cumulusmx is running then. I thought it was just me. This also explains why continued troubleshooting with ping wasn't making any sense and was actually likely making the situation worse. What a terrible piece of hardware!

That being said, I'll check the port and set it if I can set it to 10/half... it's a Cisco WS-C2960S-48LPS-L so I should be able to. Honestly unsure of what it's running at now. When I get home I'll check and see if I can get to the config page and turn off wl.com uploads, because I think that's still on.

Shut off CumulusMX last night and waited a few minutes... I was then able to access the WeatherLinkIP device and turn off the WL upload. Waited a few minutes then started back up CumulusMX again with no issues. I'll look into static setting the port speed on the switch tonight, but so far so good.

bab5871 wrote: ↑Tue 22 Sep 2020 12:10 pm Shut off CumulusMX last night and waited a few minutes... I was then able to access the WeatherLinkIP device and turn off the WL upload. Waited a few minutes then started back up CumulusMX again with no issues. I'll look into static setting the port speed on the switch tonight, but so far so good.

good news. not sure how long the disconnect period needs to be. maybe google can offer some advice.

I don't need to send data to weatherlink... not really concerned about it being shut off. Primarily it needs to go to wunderground/cwop, so that's fine. As long as this solves the disconnect issues and unable to reconnect without rebooting the console/logger I'll be happy.

Now that Weatherlink is turned off I don't think you need the Disconnect period setting, and that should help to avoid the connection issue.

However, If you also use WeatherlinIP you can upload to Weatherlink.com and have your data on its map! But is it worth the disconnection frustration

I use 15 seconds disconnect period in CumulusMX (using the WiFiLogger and having it update to 10 sites, including Weatherlink.com). With the WiFiLogger being quite busy for those updates, I do get some disconnection messages but no stoppage or crashes. I think WeatherlinkIP may be less stable than WiFiLogger in sharing access.

Enjoy,
Paul

Ok, had time to set the port speed and duplex tonight. It was auto before, now hard set to 10 half. Hopefully this fixes any issues. Thanks for all the info, I'll check in in a few days and let you know if there's any issues!

Hardware is Gigabit Ethernet, address is 6c50.4df1.6e88 (bia 6c50.4df1.6e88)
MTU 1500 bytes, BW 10000 Kbit/sec, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 10Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:01, output hang never
Last clearing of "show interface" counters never

Port Name Status Vlan Duplex Speed Type
...
Gi1/0/8 connected 1 half 10 10/100/1000BaseTX