Another MXdiags Zip File Attached b3235

[jwpetrov]

Hello all:

There appears to be an issue with SFTP load timings clashing. On line 13230 of the 20230413-004640.txt referencing a problem with threading. This causes the CMX to crash and stop sending files to the web server.

First part of error message: Probable I/O race condition detected while copying memory. The I/O package is not thread safe by default.

Jed

[HansR]

It also occurs in the the last logfile (20230418-080406.txt) on line 480 (only once)
and in file 20230413-004640.txt many times etc... but not in the files prior to that.

So what did you change?

[jwpetrov]

Hans:

As near as I can determine on the latest MXdiag that I sent wasn't running very long. I shutdown and restarted CMX because the Realtime gauges were not updating even though I didn't change anything in the Cumulus.ini file. It could have been that one I/O error on line 480 that caused the problem. In the evening there was the scrolling message and the red status dot on the Gauges page that stated the "station was down" and the gauges weren't updating. This had been going on for a number of hours (as stated in the message) before I realized it was happening. That's why I shutdown CMX and restarted, which resolved the Realtime issue. The latest MXdiag file (which is not included) has a timestamp of 2023-04-18 22:25:17 and shows no errors as of 2023-04-19 21:24:51.

Perhaps this is also worth mentioning that CMX is running on a spare laptop and other than checking the website and writing forum messages isn't running other programs. For now, it's dedicated to running CMX.

Hope that answers your questions and thank you for asking them.

Jed

[HansR]

Jed,

I was wondering if you changed things to Windows (an automatic update or so) because an error like this can't be there out of the blue while prior to that moment no errors were found. It almost seems like some hardware failure or error in the OS (which seems to be Win 8 - NT 6.2.9200.0 - and not Win 10 like stated in your profile).

Anyway, this seems deep in the code somewhere, maybe in a library so I pass this on to Mark.

[water01]

which seems to be Win 8 - NT 6.2.9200.0 - and not Win 10 like stated in your profile

That is Windows 10 22H2 Hans mine says exactly the same, Microsoft doesn't maintain that very well!!

[HansR]

which seems to be Win 8 - NT 6.2.9200.0 - and not Win 10 like stated in your profile

That is Windows 10 22H2 Hans mine says exactly the same, Microsoft doesn't maintain that very well!!

My search on google gave a Win 8 for NT 6.2 but I believe anybody who claims otherwise

[water01]

2023-04-19 16:08:19.169 Cumulus MX v.3.25.0 build 3241
2023-04-19 16:08:19.204 Platform: Win32NT
2023-04-19 16:08:19.205 OS version: Microsoft Windows NT 6.2.9200.0
2023-04-19 16:08:19.220 Current culture: English (United Kingdom) [en-GB]
2023-04-19 16:08:19.220 Running as a 64 bit process

WinVer gives "Version 22H2 (OS Build 19045.2788)".

Here it is, easy mistake as MS is bad at maintaining this area, recall a version of Windows 7 that said it was Windows 2000!!

Notice it also says Win32 NT when it is running a 64 bit process!!

[HansR]

Well we're getting pretty much off topic here but it is not me who made the Windows version ambiguous.
See this page and the notes on it.

[jwpetrov]

Hello all:

Looks like you figured out the Windows version. I’ve been traveling today and haven’t been able to pay attention to emails.

As of 01:15 UTC on 21 Apr 2023 the station is still up. Can’t check the log until later.

Thanks all for looking into this.

Jed

[mcrossley]

I'll take a look at this - as the error message implies it seems to be a concurrency issue, though I thought the interval and real time uploads used their own different instances of SFTP objects, so some deeper investigation may be required.