Sleeping CMXv4?

[Dador]

Hi,

since version 4022 I have a problem with cumulus. Well, it seems to go to sleep/freeze and cannot wake up. During this time, it does not connect to the station, does not download data or send to the server. No errors appear on the console. Additionally, the Ctrl+C closing function does not work, I just have to close the window with the close button.

Today the arrest took place at 00:35. Attached is the MXdiags file.

It's just a report. Although maybe there is some temporary solution.

[Dador]

Interesting things also happen with the average 24-hour temperature.

1. Time 00:35, CMXv4 goes to sleep, TempAvg24Hrs records a sudden increase.
2. Restarting CMX fetches data from the WifiLogger memory, which draws the temperature but not the derived one, which in this case is THWXindex.

I notice this jump in the TempAvg24Hrs value every time data is downloaded from the logger memory. As if CMX did not take this data into account in subsequent calculations. Hence the sudden jump and distortion in the result.

[HansR]

There is a server issue apparently which starts at 00h31:

Code: Select all

2024-05-17 00:31:55.354 Realtime[139]: Warning, a previous cycle is still processing local files. Skipping this interval.

It fails to reinitialise the connection after sleeping for 20 seconds many times.

Then the world changes and it does the following every minute:

Code: Select all

2024-05-17 00:35:08.490 InitTCP: Connecting to the station
2024-05-17 00:35:08.493 InitTCP: Flushing input stream
2024-05-17 00:35:13.059 InitTCP: Connection confirmed
2024-05-17 00:35:13.059 SendLoopCommand: Starting - LPS 2 1
2024-05-17 00:35:14.073 SendLoopCommand: Starting - LOOP 50
2024-05-17 00:35:16.144 RealtimeReconnect: Realtime ftp attempting to reinitialise the connection
2024-05-17 00:35:16.144 RealtimeFTPLogin: Attempting realtime FTP connect to host pogodarybnik.pl on port 21
2024-05-17 00:35:16.144 RealtimeFTPLogin: Attempting realtime FTP connect to host pogodarybnik.pl on port 21
2024-05-17 00:36:08.466 InitTCP: Connecting to the station
2024-05-17 00:36:08.474 InitTCP: Flushing input stream
2024-05-17 00:36:13.040 InitTCP: Connection confirmed
2024-05-17 00:36:13.040 SendLoopCommand: Starting - LPS 2 1
2024-05-17 00:36:14.047 SendLoopCommand: Starting - LOOP 50
2024-05-17 00:37:08.468 InitTCP: Connecting to the station
2024-05-17 00:37:08.471 InitTCP: Flushing input stream
2024-05-17 00:37:13.022 InitTCP: Connection confirmed
2024-05-17 00:37:13.022 Reading reception stats
2024-05-17 00:37:13.538 SendLoopCommand: Starting - LPS 2 1
2024-05-17 00:37:14.549 SendLoopCommand: Starting - LOOP 50

until 5h02. No entries in the logfile afterwards until shutdown at 8h33 by you.

I would suggest Mark to take a look at this one.

[Dador]

Yes, I have problems connecting to the server due to the very low threshold of simultaneous connections = 5!

However, in earlier versions CMX fought valiantly for access to data, now it quickly gives up

[water01]

The MXDiag file doesn't really tell us much. Could you put Debug logging and Data logging on (Program Settings > Logging Options) and run it until goes to sleep and then post the MXdiags file.

Have you checked that your USB devices have NOT got power saving mode ticked?

[Dador]

The MXDiag file doesn't really tell us much. Could you put Debug logging and Data logging on (Program Settings > Logging Options) and run it until goes to sleep and then post the MXdiags file.

Sure, no problem.

Have you checked that your USB devices have NOT got power saving mode ticked?

No, no changes here. Everything is as usual.

[water01]

No, no changes here. Everything is as usual.

But please check as there has been cases where Windows updates have reset the Power Saving options to on and if USB detects no usage it puts the connection to sleep, and as you are using a logger that would not be good.

[Dador]

Ok, I managed to save what happens in CMX when it freezes.

At about 11:24 I reset the main router. The file shows what happened until CMX was disabled.
The last realtime.txt update on the server is 11:25:35.
Interestingly, I never saw a connection loss message in this version.
There was such a prompt earlier. Something like - "data is not available for 30 seconds." in red colour.

[mcrossley]

The FTP reconnect code is leaving something to be desired, it was the same in v3.

I'll have to investigate the "unknown host" (Nieznany host) error, which would seem to be a DNS issue where it is caching the "address not found" from when the network went down. Maybe there is some way of forcing the FTP client to refresh the DNS.

[ConligWX]

you seem to be having connectivity issues too,is something else accessing that logger as well as cumulusmx?

Code: Select all

	Line  192: 2024-05-21 11:24:30.774 OpenTcpPort: Error - Próba przeprowadzenia operacji, wykonywanej przez gniazdo, na nieosiągalnym hoście. 192.168.0.105:22222
	Line  193: 2024-05-21 11:24:31.787 OpenTcpPort: TCP Logger Connect attempt 2
	Line  194: 2024-05-21 11:24:31.788 OpenTcpPort: Error - Próba przeprowadzenia operacji, wykonywanej przez gniazdo, na nieosiągalnym hoście. 192.168.0.105:22222
	Line  195: 2024-05-21 11:24:32.800 OpenTcpPort: TCP Logger Connect attempt 3
	Line  196: 2024-05-21 11:24:32.801 OpenTcpPort: Error - Próba przeprowadzenia operacji, wykonywanej przez gniazdo, na nieosiągalnym hoście. 192.168.0.105:22222
	Line  197: 2024-05-21 11:24:33.813 OpenTcpPort: TCP Logger Connect attempt 4
	Line  198: 2024-05-21 11:24:33.813 OpenTcpPort: Error - Próba przeprowadzenia operacji, wykonywanej przez gniazdo, na nieosiągalnym hoście. 192.168.0.105:22222
	Line  205: 2024-05-21 11:24:34.829 OpenTcpPort: TCP Logger Connect attempt 5
	Line  206: 2024-05-21 11:24:34.830 OpenTcpPort: Error - Próba przeprowadzenia operacji, wykonywanej przez gniazdo, na nieosiągalnym hoście. 192.168.0.105:22222
	Line  216: 2024-05-21 11:24:35.831 OpenTcpPort: TCP Logger connect failed
	Line  218: 2024-05-21 11:24:35.831 OpenTcpPort: TCP Logger Connect attempt 1
	Line  219: 2024-05-21 11:24:35.831 OpenTcpPort: Error - Próba przeprowadzenia operacji, wykonywanej przez gniazdo, na nieosiągalnym hoście. 192.168.0.105:22222
	Line  220: 2024-05-21 11:24:36.843 OpenTcpPort: TCP Logger Connect attempt 2
	Line  221: 2024-05-21 11:24:36.844 OpenTcpPort: Error - Próba przeprowadzenia operacji, wykonywanej przez gniazdo, na nieosiągalnym hoście. 192.168.0.105:22222
	Line  222: 2024-05-21 11:24:37.853 OpenTcpPort: TCP Logger Connect attempt 3
	Line  223: 2024-05-21 11:24:37.854 OpenTcpPort: Error - Próba przeprowadzenia operacji, wykonywanej przez gniazdo, na nieosiągalnym hoście. 192.168.0.105:22222
	Line  224: 2024-05-21 11:24:38.865 OpenTcpPort: TCP Logger Connect attempt 4
	Line  225: 2024-05-21 11:24:38.866 OpenTcpPort: Error - Próba przeprowadzenia operacji, wykonywanej przez gniazdo, na nieosiągalnym hoście. 192.168.0.105:22222
	Line  226: 2024-05-21 11:24:39.878 OpenTcpPort: TCP Logger Connect attempt 5
	Line  227: 2024-05-21 11:24:39.879 OpenTcpPort: Error - Próba przeprowadzenia operacji, wykonywanej przez gniazdo, na nieosiągalnym hoście. 192.168.0.105:22222

then:

2024-05-16 21:17:37.800 Logging interval = 5 mins
2024-05-16 21:17:37.800 Real time interval:enabled, uploads:enabled, (10 secs)
2024-05-16 21:17:37.800 Interval :enabled, uploads:enabled, (10 mins)

logging interval 5mins and 10 minutes?

i suggest set both at 5 minute intervals.

[Dador]

2024-05-16 21:17:37.800 Logging interval = 5 mins
2024-05-16 21:17:37.800 Real time interval:enabled, uploads:enabled, (10 secs)
2024-05-16 21:17:37.800 Interval :enabled, uploads:enabled, (10 mins)

logging interval 5mins and 10 minutes?

i suggest set both at 5 minute intervals.

My settings:

Logging data Davis VP2 - 5 min
Logging data CMX - 5 min
Upload to server (Process) - 10 min
Upload to server (Realtime) - 10 sec.

This setup has been running for a year and a half now. I don't believe this could be a problem.
In another thread they also have similar symptoms.
CMX does not reconnect to Davis after losing network connection.

[ConligWX]

2024-05-16 21:17:37.800 Logging interval = 5 mins
2024-05-16 21:17:37.800 Real time interval:enabled, uploads:enabled, (10 secs)
2024-05-16 21:17:37.800 Interval :enabled, uploads:enabled, (10 mins)

logging interval 5mins and 10 minutes?

i suggest set both at 5 minute intervals.

CMX does not reconnect to Davis after losing network connection.

So what type of Davis logger are you using? I've never had issues with the WLL, USB or WeatherlinkIP. thought he last one can be an issue if you are accessing it with other apps at the same time.

[mcrossley]

I have found the issue with the FTP reconnect, fixed in the next build.

You will see in the log file above that the FTP does actually reconnect, but because a flag to say the reconnection was in progress was being prematurely reset, another reconnection attempt is started which immediately disconnects it again. That process repeats and gets worse.

[Dador]

2024-05-16 21:17:37.800 Logging interval = 5 mins
2024-05-16 21:17:37.800 Real time interval:enabled, uploads:enabled, (10 secs)
2024-05-16 21:17:37.800 Interval :enabled, uploads:enabled, (10 mins)

logging interval 5mins and 10 minutes?

i suggest set both at 5 minute intervals.

CMX does not reconnect to Davis after losing network connection.

So what type of Davis logger are you using? I've never had issues with the WLL, USB or WeatherlinkIP. thought he last one can be an issue if you are accessing it with other apps at the same time.

WiFiLogger v1

I have found the issue with the FTP reconnect, fixed in the next build.

You will see in the log file above that the FTP does actually reconnect, but because a flag to say the reconnection was in progress was being prematurely reset, another reconnection attempt is started which immediately disconnects it again. That process repeats and gets worse.

Good news to start the day

[Dador]

Version 4.1.0

I disconnected the Internet cable to test whether CMX will return to transmitting data. No connection loss message appeared on the console, but CMX started sending data after turning on the Internet. It's good.

However, another problem arose. As you can see below, this prompt happens every 2 seconds. Restarting CMX did not help. I can't stop this error.
I use Davis + WiFiLogger.

Fix for Davis VP2 consoles losing todays rainfall on a full power cycle

Code: Select all

2024-06-05 13:41:42 -      New values:  RaindayStart = 314,20000000000005, MidnightRainCount = 314,20000000000005, Raincounter = 314,20000000000005
2024-06-05 13:41:42 -  ****Rain counter reset to previous midnight value (VP2 console power cycled?), lost 0 counts
2024-06-05 13:41:40 -      New values:  RaindayStart = 314,20000000000005, MidnightRainCount = 314,20000000000005, Raincounter = 314,20000000000005
2024-06-05 13:41:40 -  ****Rain counter reset to previous midnight value (VP2 console power cycled?), lost 0 counts
2024-06-05 13:41:38 -      New values:  RaindayStart = 314,20000000000005, MidnightRainCount = 314,20000000000005, Raincounter = 314,20000000000005
2024-06-05 13:41:38 -  ****Rain counter reset to previous midnight value (VP2 console power cycled?), lost 0 counts
2024-06-05 13:41:36 -      New values:  RaindayStart = 314,20000000000005, MidnightRainCount = 314,20000000000005, Raincounter = 314,20000000000005
2024-06-05 13:41:36 -  ****Rain counter reset to previous midnight value (VP2 console power cycled?), lost 0 counts
2024-06-05 13:41:34 -      New values:  RaindayStart = 314,20000000000005, MidnightRainCount = 314,20000000000005, Raincounter = 314,20000000000005
2024-06-05 13:41:34 -  ****Rain counter reset to previous midnight value (VP2 console power cycled?), lost 0 counts
2024-06-05 13:41:32 -      New values:  RaindayStart = 314,20000000000005, MidnightRainCount = 314,20000000000005, Raincounter = 314,20000000000005
2024-06-05 13:41:32 -  ****Rain counter reset to previous midnight value (VP2 console power cycled?), lost 0 counts
2024-06-05 13:41:30 -      New values:  RaindayStart = 314,20000000000005, MidnightRainCount = 314,20000000000005, Raincounter = 314,20000000000005
2024-06-05 13:41:30 -  ****Rain counter reset to previous midnight value (VP2 console power cycled?), lost 0 counts
2024-06-05 13:41:28 -      New values:  RaindayStart = 314,20000000000005, MidnightRainCount = 314,20000000000005, Raincounter = 314,20000000000005
2024-06-05 13:41:28 -  ****Rain counter reset to previous midnight value (VP2 console power cycled?), lost 0 counts
2024-06-05 13:41:26 -      New values:  RaindayStart = 314,20000000000005, MidnightRainCount = 314,20000000000005, Raincounter = 314,20000000000005
2024-06-05 13:41:26 -  ****Rain counter reset to previous midnight value (VP2 console power cycled?), lost 0 counts