I have setup a raspberry pi installation of the latest CumulusMX release and it is creating the standard files OK.
However, I am having difficulty uploading the webfiles to a web server using the inbuilt MX ftp facility.
Attached are 2 log files :
ftplog.txt - Output log file when using ftp. Apart from file realtimegauges.txt all files failed to upload with the message "Could not get file size"
mxdiag.txt - Diagnostic file from folder MXdiag when using sftp. Files failed to upload with message "Cannot access a disposed object - Object name: Renci.SshNet.sftpclient.
In both cases I had the permissions to the upload folder set to 777.
When manually uploading the files using the Winscp ftp client set to sftp I did not experience any problems.
Any help/suggestions would be appreciated.
David Anderson
Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
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
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
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
MX Upload to webserver problem
Moderator: mcrossley
-
- Posts: 39
- Joined: Thu 03 Dec 2009 8:33 am
- Weather Station: Davis Vantage Pro 2
- Operating System: Windows 7
MX Upload to webserver problem
You do not have the required permissions to view the files attached to this post.
-
- Posts: 2477
- Joined: Wed 08 Jun 2011 11:19 am
- Weather Station: Davis Vantage Pro 2 + Ecowitt
- Operating System: GNU/Linux Ubuntu 22.04 LXC
- Location: Alcaston, Shropshire, UK
- Contact:
Re: MX Upload to webserver problem
As you are connecting okay with SFTP have you tried setting MX to use SFTP rather than FTP? It could be that your hosting service doesn't allow FTP - many are moving to SFTP or FTPS only.
- mcrossley
- Posts: 12766
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: MX Upload to webserver problem
If you switch on debug logging we will get some more info in the logs.
But the basic problem is - "Error uploading web/index.htm to /index.htm : Permission denied"
But the basic problem is - "Error uploading web/index.htm to /index.htm : Permission denied"
-
- Posts: 39
- Joined: Thu 03 Dec 2009 8:33 am
- Weather Station: Davis Vantage Pro 2
- Operating System: Windows 7
Re: MX Upload to webserver problem
Attached is a session with debug logging. You will notice that realtimegauges.txt is being created and uploaded every minute without error - I have checked that it does actually arrive at the webserver. I cannot explain the message "permission denied" when index.htm is uploaded as the destination folder has 777 permissions AND the realtimegauges.txt file is uploaded to the same folder without error. Could you please explain the meaning of the "Cannot access a disposed object" message against each of the other Standard Files.
You do not have the required permissions to view the files attached to this post.
- mcrossley
- Posts: 12766
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: MX Upload to webserver problem
Yes the realtime SFTP is logging OK, and uploading the realtimegauges.txt file OK.
The interval SFTP is logging in OK, but the first file it tries to upload (/index.htm) fails with the permission denied error.
At this point Cumulus disposes of the SFTP client because I found trying to determine all the possible failure modes and correct action to take for each was too complex. So on first failure it aborts, and waits for the next upload cycle. Not clever I know, and it could be better I know but t is what it is for now.
My catch for the SFTP being disposed is wrong - I'll fix that for the next release.
The basic problem remains, the SFTP client does not have permissions to write to /index.htm
You probably need to check the server logs to find the reason why.
The interval SFTP is logging in OK, but the first file it tries to upload (/index.htm) fails with the permission denied error.
At this point Cumulus disposes of the SFTP client because I found trying to determine all the possible failure modes and correct action to take for each was too complex. So on first failure it aborts, and waits for the next upload cycle. Not clever I know, and it could be better I know but t is what it is for now.
My catch for the SFTP being disposed is wrong - I'll fix that for the next release.
The basic problem remains, the SFTP client does not have permissions to write to /index.htm
You probably need to check the server logs to find the reason why.
-
- Posts: 374
- Joined: Sun 27 Feb 2011 5:13 pm
- Weather Station: Ecowitt HP2551 & GW1100
- Operating System: Raspberry Pi OS
- Location: Kangasala, Finland
Re: MX Upload to webserver problem
Maybe a dumb question, but why there is a / in front of the failing filename, but not in the realtimegauges.txt that is sent succesfully? Some glitch / typo in Cumulus settings? Another longshot that comes to my mind is the 777-permission. Maybe a server with tight security settings could restict handling of files with full permissions?
- mcrossley
- Posts: 12766
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: MX Upload to webserver problem
The leading slash could be significant. The upload process for realtime files and interval files does treat an empty remote server folder in the settings differently.
So it looks like the upload works to the default "current" remote directory, but the SSH server possibly does not set the root to the upload folder.
A test would be to try setting the remote server folder in the settings to "./" which should force all the files into the default folder.
So it looks like the upload works to the default "current" remote directory, but the SSH server possibly does not set the root to the upload folder.
A test would be to try setting the remote server folder in the settings to "./" which should force all the files into the default folder.