Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
From Cumulus MX version 3 build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since, and has recently released Cumulus MX version 4. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).
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:-
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?
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.
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.
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.
You do not have the required permissions to view the files attached to this post.
mcrossley wrote: ↑Sat 04 May 2024 10:24 pm
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.
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.
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.
You do not have the required permissions to view the files attached to this post.
broadstairs wrote: ↑Sun 05 May 2024 8:55 am
Update:- Solved the locale issue- was a Linux config issue, now both instances say the same.
AndyKF650 wrote: ↑Sun 05 May 2024 5:18 pm
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?
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.
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!
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.