Cumulus Support

Posted: **Sun 11 Jun 2023 6:15 am**

Hi. I updated CMX to newest version and NOAA-reports stop working. CMX doesn't create them anymore. With version 3.25.1- build 3244 there was no problem. Last report is 4.6.2023. If i try to regenerate them nothing happens. Any idea whats wrong? I have tried to search what is the problem but i have no idea...

Posted: **Sun 11 Jun 2023 7:37 am**

Please zip up the log file from the MXdiags folder in your installation, and attach it to a reply to this topic.

Posted: **Sun 11 Jun 2023 8:07 am**

Here's the log file

Posted: **Sun 11 Jun 2023 8:58 am**

There are many errors in your errorlog so the NOAA probably are not your only problem.

Please look at this one and as it says 'please edit the file to correct':

Code: Select all

2023-06-11 09.09.37.884 Loading last N hour data from data logs: 11.6.2023 8.30.00
2023-06-11 09.09.37.887 LoadRecent: Attempting to load 7 days of entries to recent data list
2023-06-11 09.09.37.907 Error parsing log file record: Syötemerkkijonon muoto ei ollut kelvollinen.
2023-06-11 09.09.37.907 LoadRecent: Error at line 221 of data\kesä23log.txt : Syötemerkkijonon muoto ei ollut kelvollinen.
2023-06-11 09.09.37.907 Please edit the file to correct the error
2023-06-11 09.09.37.910 LoadRecent: Loaded 0 of 0 new entries to recent database

Then you get the following errors which continue until CMX gives up.

Code: Select all

2023-06-11 09.09.39.302 Normal running
2023-06-11 09.09.39.577 WU Response: OK: OK
2023-06-11 09.09.39.577 End of WU archive upload
2023-06-11 09.09.43.865 Ignoring bad data: outhum = 255
2023-06-11 09.09.44.873 Synchronise: Sensor data changed
2023-06-11 09.09.48.919 Ignoring bad data: outhum = 255
[...]
2023-06-11 09.10.29.305 Ignoring bad data: outhum = 255
2023-06-11 09.10.32.822 Synchronise: Sensor data changed
2023-06-11 09.10.34.330 Ignoring bad data: outhum = 255
2023-06-11 09.10.39.386 Sensor clock  9.09.44 drift = 1 seconds
2023-06-11 09.10.39.386 Synchronisation: No station clock change time found
2023-06-11 09.10.39.387 Stop Synchronising
2023-06-11 09.10.39.387 Ignoring bad data: outhum = 255
2023-06-11 09.10.55.396 Start Synchronising with console
[...]
2023-06-11 09.11.15.366 Ignoring bad data: outhum = 255
2023-06-11 09.11.18.531 PHP[0]: Upload to /realtimegauges.txt: Response code = 500: InternalServerError
2023-06-11 09.11.18.531 PHP[0]: Upload to /realtimegauges.txt: Response text follows:
Error: Cannot create the target file /realtimegauges.txt with this user 

2023-06-11 09.11.19.556 PHP[0]: Upload to /realtime.txt: Response code = 500: InternalServerError
2023-06-11 09.11.19.556 PHP[0]: Upload to /realtime.txt: Response text follows:
Error: Cannot create the target file /realtime.txt with this user

You must have changed something, pulled a plug, changed credentials or whatever.
The installation has changed somewhere and although this does not seem an installation error you might start checking that (did you copy all files correctly?) and possibly re-install the latest version. Check all cables, wifi, credentials etc... and think hard of what you did.

Posted: **Sun 11 Jun 2023 9:03 am**

There was few blackouts so maybe that's on reason..

Posted: **Sun 11 Jun 2023 11:03 am**

Mrc wrote: ↑Sun 11 Jun 2023 9:03 am There was few blackouts so maybe that's on reason..

OK, but than at least we need a logfile without those errors and with an NOAA generation (rollover).
Otherwise the logfile is telling the wrong things or no things at all.

So first you have some work to do.

Posted: **Sun 11 Jun 2023 12:21 pm**

After fixing the corrupted line in monthly logfile you can try to generate the noaa report manually using the regenerate report button on monthly report view. No need to wait overnight for rollover.

The other errors about failed php upload for realtime.txt and realtimegauges.txt should not affect report generation. I’m not familiar about the php upload feature details, but the error suggests a problem with the path settings, since it tries to generate files to the server root instead of current directory.

Posted: **Tue 20 Jun 2023 8:07 am**

Hi All,
My Noaa-Reports have also stopped being uploaded, I am also getting these errors.

023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAYR2023.txt: Response code = 500: InternalServerError
2023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAYR2023.txt: Response text follows:
Error: Cannot create the target file /public_html/Reports/NOAAYR2023.txt with this user branksom

2023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAMO0623.txt: Response code = 500: InternalServerError
2023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAMO0623.txt: Response text follows:
Error: Cannot create the target file /public_html/Reports/NOAAMO0623.txt with this user branksom

I have also noticed in the MXdiags file I am getting this Error: TimeStamp is out of date
Data TS = 1687238629
Server TS = 1687238647

This started yesterday 19/06/2023 I have not made any changes.

I have uploaded my MXdiags for your info. I hope you can sort this problem out for me, does anyone have any ideas please.

MXdiags.rar

Posted: **Tue 20 Jun 2023 8:30 am**

The 500 internal error and ” Error: Cannot create the target file /public_html/Reports/NOAAYR2023.txt with this user branksom” states very clearly that your webserver denies the upload. If this has worked for you with php until now, the problem most likely is some php security mechanism on webserver that is blocking it. Webserver logs might give a clue.

However if noaa report upload never has worked for you with php, you probably have not changed your path correctly. Point number 5 in the configuration wiki. Unfortunately I’m not using php currently, so I cannot give a bulletproof example.

https://www.cumuluswiki.org/a/PHP_Uploads#Configuration

Posted: **Tue 20 Jun 2023 8:49 am**

SamiS wrote: ↑Tue 20 Jun 2023 8:30 am The 500 internal error and ” Error: Cannot create the target file /public_html/Reports/NOAAYR2023.txt with this user branksom” states very clearly that your webserver denies the upload. If this has worked for you with php until now, the problem most likely is some php security mechanism on webserver that is blocking it. Webserver logs might give a clue.

However if noaa report upload never has worked for you with php, you probably have not changed your path correctly. Point number 5 in the configuration wiki. Unfortunately I’m not using php currently, so I cannot give a bulletproof example.

https://www.cumuluswiki.org/a/PHP_Uploads#Configuration

Have you missed this in my message “This started yesterday 19/06/2023 I have not made any changes”?

So I need to get Intouch with my host server, HostPresto? Is that correct?

Posted: **Tue 20 Jun 2023 10:21 am**

M1DUL wrote: ↑Tue 20 Jun 2023 8:07 am Hi All,
My Noaa-Reports have also stopped being uploaded, I am also getting these errors.

023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAYR2023.txt: Response code = 500: InternalServerError
2023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAYR2023.txt: Response text follows:
Error: Cannot create the target file /public_html/Reports/NOAAYR2023.txt with this user branksom

2023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAMO0623.txt: Response code = 500: InternalServerError
2023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAMO0623.txt: Response text follows:
Error: Cannot create the target file /public_html/Reports/NOAAMO0623.txt with this user branksom

I have also noticed in the MXdiags file I am getting this Error: TimeStamp is out of date
Data TS = 1687238629
Server TS = 1687238647

This started yesterday 19/06/2023 I have not made any changes.

I have uploaded my MXdiags for your info. I hope you can sort this problem out for me, does anyone have any ideas please.

MXdiags.rar

It is not just your NOAA reports, your PHP upload does not work given the errors (like below) in your MXdiags:

Code: Select all

2023-06-20 08:44:24.442 PHP[191]: Error uploading to realtime.txt
2023-06-20 08:44:24.442 PHP[191]: Error uploading to realtime.txt - Exception Type: System.Net.Http.HttpRequestException
Message: An error occurred while sending the request.
Inner Exception... 
Exception Type: System.Net.WebException
Message: The request was aborted: Could not create SSL/TLS secure channel.


2023-06-20 08:44:24.442 PHP[191] Retrying upload to realtime.txt
2023-06-20 08:44:24.460 PHP[191]: Error uploading to realtimegauges.txt
2023-06-20 08:44:24.460 PHP[191]: Error uploading to realtimegauges.txt - Exception Type: System.Net.Http.HttpRequestException
Message: An error occurred while sending the request.
Inner Exception... 
Exception Type: System.Net.WebException
Message: The request was aborted: Could not create SSL/TLS secure channel.

You will have to review your PHP upload (maybe it's the provider). And the public_html almost certainly shuld not be part of the NOAA path in your CMX configuration. But the PHP and the NOAA configs are two different things. Check the PHP upload first.

The timestamp out of date is a consequence of a timeout because it connects badly. Not important right now.

Posted: **Tue 20 Jun 2023 3:45 pm**

Hello HansR,

Thank you for replying to my message, I have been getting those SSL/TLS errors for quite some time, I did make a post on here. viewtopic.php?t=21174 about my problem, but nobody could get to the bottom of it. Here is my Upload.php file, maybe you can see what is wrong with it. I would appreciate your help enormously.

upload.rar

Many Thanks for your help.

Posted: **Tue 20 Jun 2023 4:13 pm**

Hi,
I can't open the .rar file but it appear you are using PHP for uploads.

Code: Select all

2023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAMO0623.txt: Response code = 500: InternalServerError
2023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAMO0623.txt: Response text follows:
Error: Cannot create the target file /public_html/Reports/NOAAMO0623.txt with this user branksom

As Hans indicated the public_html should not be part of the Upload folder name and likely just Reports

Whenever I change my Upload settings between FTP and PHP I have to change the NOAA settings Upload folder from public_html/cumulusmx/Reports to just cumulusmx/Reports
And similar for the Extra web files.

Enjoy,
Paul

Posted: **Tue 20 Jun 2023 4:54 pm**

PaulMy wrote: ↑Tue 20 Jun 2023 4:13 pm Hi,
I can't open the .rar file but it appear you are using PHP for uploads.
Code: Select all
2023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAMO0623.txt: Response code = 500: InternalServerError
2023-06-20 00:00:00.859 PHP[Int]: Upload to /public_html/Reports/NOAAMO0623.txt: Response text follows:
Error: Cannot create the target file /public_html/Reports/NOAAMO0623.txt with this user branksom
As Hans indicated the public_html should not be part of the Upload folder name and likely just Reports

Whenever I change my Upload settings between FTP and PHP I have to change the NOAA settings Upload folder from public_html/cumulusmx/Reports to just cumulusmx/Reports
And similar for the Extra web files.

Enjoy,
Paul

Hi Paul,
Thank you for your reply to my message, I have changed my NOAA settings Upload folder from public_html/Reports to just Reports it seems to be working now. But still getting quite a few intermittent problems with SSL/TLS Errors.

Posted: **Tue 20 Jun 2023 5:16 pm**

M1DUL wrote: ↑Tue 20 Jun 2023 3:45 pm Hello HansR,

Thank you for replying to my message, I have been getting those SSL/TLS errors for quite some time, I did make a post on here. viewtopic.php?t=21174 about my problem, but nobody could get to the bottom of it. Here is my Upload.php file, maybe you can see what is wrong with it. I would appreciate your help enormously.

upload.rar

Many Thanks for your help.

I compared your upload.php with mine and I see no difference so that is all OK.

I understand that now your NOAA reports are working so if you get too many errors on upload it most likely is a thing with your provider. Some tuning needed there. If your realtime frequency is lower than 15 or 30 seconds consider changing that first. Providers don't like high frequencies on these upload channels (nor do they on the FTP channels btw). High frequencies always are a riks for provider problems.

Cumulus Support

NOAA-reports stop working

NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working

Re: NOAA-reports stop working