meteohub.de

Maybe this it is not only a "provider" problem"
2015-12-24 02:12:46 Error: Could not delete old public_html/weather28/uploadMB/tagMB.txt ,
so could not rename public_html/weather28/uploadMB/mb_tagMB.txt to that: remote delete failed
Searching this forum returns multiple discussions that error "Could not delete old - - - remote delete failed", all end in "Provider problem"

Another user is stopping installing its Meteobridge so I offered to test his situation.
1. It is not the "delete" part as the same message occurs when there is NO old file present
2. It is not the rename part as I used an ftp program to do exactly the same
a. upload a file as tempxx
b. optional delete old file
c. rename old file.
and the Macintosh FTP program works the same way when modifying a file, first a "save-filename" file and then replace the old file.

It is not an ownership problem?
I used the same credentials in the FTP program, in Meteobridge and in a browser.

The only difference I can find between this "no-delete" site and other 4 sites which are accepting Meteobridge uploads:
The 4 sites have a file Owner name xxx and a different Group name yyy
The files with the error have Owner and Group with the same name.

Could that be the problem? The FTP program has no problem with it but maybe Meteobridge needs those two names to be different?

Wim

Meteobridge uses ncftp. Did you try with this? It might simplify drilling down to the root cause.
When everything fails I could insert a switch not to use the nice ncftp feature to
"upload as a temp name and then rename to target name when upload is fine".

admin wrote:Meteobridge uses ncftp. Did you try with this? It might simplify drilling down to the root cause.
When everything fails I could insert a switch not to use the nice ncftp feature to
"upload as a temp name and then rename to target name when upload is fine".

Removing this feature "upload as temp" will make things even worse.
For Leuven I changed this year from upload as .php to upload as .txt so I can cope with incomplete uploads.
But most uploads still occur as .php and an incomplete upload will result in nasty PHP parse errors and even sometimes no page display at all.

I will try the ncftp client today and see if i can find out more.

And to all a pleasant Christmas,

Wim

admin wrote:Meteobridge uses ncftp. Did you try with this? It might simplify drilling down to the root cause.
When everything fails I could insert a switch not to use the nice ncftp feature to
"upload as a temp name and then rename to target name when upload is fine".

@admin
I used the mac version of ncftp
Did passive mode => upload file.txt as file.txt.tmp => delete file.txt => rename file.txt.tmp as file.txt
The console list is attached, I added blank lines for readability..
All worked as it should.

I do not know what ncftp commands are used by Meteobridge. Could you please post them so I can check them also?

EDIT 12:00
The problem seems to occur inside the Meteobridge when the settings for FTP are used from the bottom part.
It works OK with ftp://user:pass@ftp.website.info:21/public_html/weather28/uploadMB/tagsMBproblem.txt
and not without the ftp credentials on the same line: /public_html/weather28/uploadMB/tagsMBproblem.txt

I will check another site with similar problems also as soon as i get access to it.

Wim