I try to explain, but understand that English is not my native language.
I shortened your message to those two points which describe the problem.
This warning-message:
- if error-reporting would be set to normal, the messages would not mess up your display.
- The scripts try to load a file which is just being uploaded and those two accesses collide
- You upload the clientraw.txt using FTP every 20 seconds
- The scripts try to load that file every 6-8 seconds on average.
- Every block has a different waiting time, but sometimes they are queued very close to the FTP happening.
- FTP is a relatively slow process which also gives a bigger chance of collision.
==> if you wait long enough a collision is certain to happen
The message will disappear
- The blocks are continually reloaded after so many (3-60) seconds
- When that block is reloaded again and there is no collision, the message will be replaced with the new data.
“Solutions”
You can “enable WD to upload-as-temp-and-rename clientraw.txt”, but I am not familiar on how to do that.
You should consider updating to the April release which will not display unimportant messages
Uploading using FTP every 20 seconds is IMHO to fast,
It seems you are already using the WD-api, consider using that api which uses a fast HTTP upload.
Wim