V4 RC #2 issues

[broadstairs]

I am also seeing the errors when checking the upload compression which worked before but this instance is not doing any uploads however it carries on no problem as it is not uploading. The compression test worked OK on the previous RC#1. I'll wait to try this on my other instance as that is uploading.

The other strange thing is I see this, which does not appear to cause any issues:-

Code: Select all

2024-05-04 22:02:35.261 Current culture: English (Botswana) [en-BW]

which I only just noticed and this happened on RC#1 as well, strange thing is the other instance gets this right as UK English and both instances run on the same Linux PC, so where does CMX obtain this from?

Stuart

[mcrossley]

Is the compression test the same as the HTTPS Certificate issue reported on the other thread? i.e. have you temporarily enabled the advanced option to ignore certificate errors?

MX reads the culture name directly from the current culture being used.

Code: Select all

{CultureInfo.CurrentCulture.DisplayName} [{CultureInfo.CurrentCulture.Name}]

[ConligWX]

I'm only seeing Current Culture as en-GB here.

Code: Select all

2024-05-04 17:44:59.168 Command line: /CumulusMX/CumulusMX.dll -service 
2024-05-04 17:44:59.168 Cumulus MX v.4.0.0 build 4021
2024-05-04 17:44:59.168 Platform       : Linux
2024-05-04 17:44:59.169 OS Description : Ubuntu 24.04 LTS
2024-05-04 17:44:59.169 Current culture: English (United Kingdom) [en-GB]

[Stigian]

Hi,

Couple of errors every 5 min. interval. Just enabled the advanced option "Ignore PHP certificate errors" as a workaround.

Code: Select all

2024-05-05 07:40:00.469 TestPhpUploadCompression: Error -
2024-05-05 07:40:00.469 TestPhpUploadCompression: Error -  - Exception Type: System.AggregateException
Message: One or more errors occurred. (The SSL connection could not be established, see inner exception.)
Inner Exception...
Exception Type: System.Net.Http.HttpRequestException
Message: The SSL connection could not be established, see inner exception.
Inner Exception...
Exception Type: System.Security.Authentication.AuthenticationException
Message: The remote certificate was rejected by the provided RemoteCertificateValidationCallback.

[AndyKF650]

Hi Mark

Following on from Paul's comment I also had upload errors expressing through the attempted realtime uploads. Initially I thought that I had not uploaded the upload.php file to my host so I reset that and uploaded it again, this did not help. After reading Paul's work around I set the ignore php certificate errors to ignore and all seems to work OK.

I have attached the current MXDiags file for info.

[broadstairs]

Is the compression test the same as the HTTPS Certificate issue reported on the other thread? i.e. have you temporarily enabled the advanced option to ignore certificate errors?

MX reads the culture name directly from the current culture being used.

Code: Select all

{CultureInfo.CurrentCulture.DisplayName} [{CultureInfo.CurrentCulture.Name}]

Yes the error is the same as the other thread. I have not applied the bypass as this instance is not uploading.

I can see an issue with the locale in Linux itself but I don't understand why one instance gets GB and the other gets BW. Displaying the locale in Linux does show a mix of both so I need to fix that first.

I'll wait for a fix for the HTTPS thing before I install on my uploading instance.

Stuart

Update:- Solved the locale issue- was a Linux config issue, now both instances say the same.

[AndyKF650]

Hi Mark

I have run V4 RC #2 since about 8am today and apart from the upload issue, as previously reported, everything else on my site appears to be working as normal.

One of the parameters I also measure is the number of CMX processes running on the RPi and with the previous release candidate this averaged 25 to 28 processes. This release the number of processes has decreased to 17 to 20 which must be a win. I have attached my file on this for those that are interested.

[mcrossley]

Update:- Solved the locale issue- was a Linux config issue, now both instances say the same.

One of the parameters I also measure is the number of CMX processes running on the RPi and with the previous release candidate this averaged 25 to 28 processes. This release the number of processes has decreased to 17 to 20 which must be a win. I have attached my file on this for those that are interested.

That's good to know, I changed the HTTP client code in this release from the legacy (.Net Framework) to the new .NET way of doing things, I wonder if that has made the difference?

[HansR]

I get the following in the logfile (once):

Code: Select all

2024-05-05 15:15:08.467 Windy: ERROR - Response = InternalServerError: 
2024-05-05 15:15:08.467 Alarm (HTTP Upload): Triggered, value = True, threshold = 0, Message = Windy: HTTP response - InternalServerError
2024-05-05 15:15:11.564 Alarm (HTTP Upload): Trigger cleared, value = False

This however does not show in the console Utils/Latest Errors (which still shows no errors).
As an alarm is raised and this is recorded as an error i.s.o. a warning I would expect it to be in the list on the console.

[water01]

Running on Windows 10, Synology NAS and Windows 11 with absolutely no issues since it was released.

It's a winner!!

Also using the Alternative Interface on all 3 no problems.

[The Dalek Hunter]

Just upgraded to RC#2.

Apart from the PHP upload problem all is running ok on my M2 Mac mini.

I like the look AI2 !

[mcrossley]

I get the following in the logfile (once):

Code: Select all

2024-05-05 15:15:08.467 Windy: ERROR - Response = InternalServerError: 
2024-05-05 15:15:08.467 Alarm (HTTP Upload): Triggered, value = True, threshold = 0, Message = Windy: HTTP response - InternalServerError
2024-05-05 15:15:11.564 Alarm (HTTP Upload): Trigger cleared, value = False

This however does not show in the console Utils/Latest Errors (which still shows no errors).
As an alarm is raised and this is recorded as an error i.s.o. a warning I would expect it to be in the list on the console.

I made most (with some inconsistency) failures in third-party uploads Warnings rather than Errors because they do not affect the core functioning of MX. I have sort of reserved Error for things that affect MX working in some way. Critical means it is pretty serious and probably stops MX functioning meaningfully.

Alarms are raised for all third-party uploads iirc, I set a threshold on mine so it takes a few errors to trigger an alarm, but the default is to trigger on the first.

As i said when I introduced this alert level system, I had to go through many (upward of a thousand+) error messages and make a decision on each, some will be wrongly categorised as I didn't deliberate much over each one!

[HansR]

@Mark: very clear. Thank you.

[Dador]

I finally abandoned CMXv3.

The latest release of CMXv4 does not bring any errors for me.

- memory consumption is even lower than in CMXv3 (10 ~ 60 MB);
- using select-a-period is fast and without major CPU and memory load.

[richard_newberry]

Hi,

Couple of errors every 5 min. interval. Just enabled the advanced option "Ignore PHP certificate errors" as a workaround.

Code: Select all

2024-05-05 07:40:00.469 TestPhpUploadCompression: Error -
2024-05-05 07:40:00.469 TestPhpUploadCompression: Error -  - Exception Type: System.AggregateException
Message: One or more errors occurred. (The SSL connection could not be established, see inner exception.)
Inner Exception...
Exception Type: System.Net.Http.HttpRequestException
Message: The SSL connection could not be established, see inner exception.
Inner Exception...
Exception Type: System.Security.Authentication.AuthenticationException
Message: The remote certificate was rejected by the provided RemoteCertificateValidationCallback.

Getting the same issue.