Error writing to Dayfile

[Hillbilly]

Hi

My weather site has been down for a couple of days as my webhost moved servers. It's taken 2 days to get the correct ftp path established. Finally, everything is back working again - almost.

My Dayfile has not been written to for the past two nights. From the Cumulus log:
20/03/2011 00:00:00.202 : === Day reset, today = 20
20/03/2011 00:00:00.202 : === Day reset for 19/03/2011
20/03/2011 00:00:00.202 : Error writing dayfile.txt: I/O error 32
20/03/2011 00:00:00.202 : Copy the following data into dayfile.txt
20/03/2011 00:00:00.202 : 19/03/11,27.0,45,10:40,2.9,07:23,10.8,14:33,1027.1,00:03,1034.0,11:33,0.0,00:00,0.0,0.0,299.7,21.5,10:48,63,14:36,95,00:01,0.00,0.0,10.8,14:33,7.6,14:33,-0.7,07:29,0.0,00:00,0.2,07:29,5.8,00:01,1.6,07:09
20/03/2011 00:00:00.202 : Error closing dayfile.txt: I/O error 103

I've attached two Cumulus logs, showing this and the previous night. They are also full of the repeated ftp error messages so a lot of junk to wade through unfortunately. I can't see anything obviously wrong in my dayfile, but I am past any sensible analysis after the fun and games of the last couple of days It can't be a coincidence.

[steve]

It's not a problem with the contents of the file, it's a 'sharing violation'. Something else on your system has the file locked so Cumulus can't write to it.

Are you uploading dayfile.txt as an extra file? I suppose it would be possible that it's actually the ftp component in Cumulus which has the file locked, because of the errors, but I don't think the ftp component locks files anyway (it certainly doesn't need to).

[Hillbilly]

Hi Steve, Toolbox uploads the dayfile to my webserver at 00:15 every day but this has all run without a problem until now. Perhaps it was Toolbox repeatedly trying to overwrite the file on my webserver which was also failing with the wrong ftp path.

I've just done a manual upload of the dayfile using Toolbox which worked OK. So Ii guess I will see what happens overnight and post if any more errors.

Thanks for the pointer.

[mcrossley]

I started getting these errors recently after running for a year+ without them. I excluded the Cumulus folders (and Cumulus process) from my AV program and the have gone away again.

[Hillbilly]

OK thanks Mark. I'll give that a go too.

Thanks for prompt replies Steve and Mark, as ever.