Page 1 of 1

Cumulusmx sudden upload problem

Posted: Sun 19 May 2024 6:11 pm
by jsel
I have two Davis Vantage Pro weather stations one runs on a Pi Zero the other on a Pi Zero 2. Both are running Bullseye. Both have been working for years without problems
Both were running V3279, and upload to different directories in my webspace at Fasthosts. Both stopped displaying new data after 2205 on 23rd April. I had made no changes.
Using Filezilla, (on a Win PC), I can see that both are still uploading every 5 minutes, but the file left is filename.jsontmp instead of filename.json

Looking at the pi log I can see the attempt to upload a file is either
Error renaming /htdocs/cumulusmx/filename.jsontmp to /htdocs/cumulusmx/filename.json : Code : 553 Message : target name already exists (/htdocs/cumulusmx/filename.json
Or some files simply
Upload of /htdocs/cumulusmx/filename.json failed

The same happens with txt files i.e txttmp

As it has happened to both at the same time, the common element would seem to be ftp to Fasthosts
However using Filezilla on a Win PC I can ftp file updates with the same name with no problems i.e test.htm
Result I am baffled as to what has happened, any ideas please
Thanks
John

Re: Cumulusmx sudden upload problem

Posted: Sun 19 May 2024 7:17 pm
by mcrossley
If you have any xxxxtmp files on your FTP server, delete them and see if that helps.

Re: Cumulusmx sudden upload problem

Posted: Mon 20 May 2024 8:56 am
by jsel
Mark
deleted all the xxx.xxxtmp files on the server, but the next cumulus upload and they just reappeared with nthe same cumulus log error messages. I am sure it must be something to do with the server (Fasthosts), but cant imagine what
John

Re: Cumulusmx sudden upload problem

Posted: Mon 20 May 2024 9:00 am
by freddie
You could try unchecking "Enable FTP rename" under Settings -> Internet Settings -> General Settings to see if that helps. Could be your hosting provider has disallowed this feature?

Re: Cumulusmx sudden upload problem

Posted: Mon 20 May 2024 10:21 am
by jsel
Freddie many thanks for that suggestion, it solved the problem on both my stations. Clearly Fasthosts made a change to their servers the night my updates stopped, will see what their support says about it
Thanks
John