Cumulus Support

Been using cumulus a while now, had it installed on this pc till I got my server up and running, then just migrated it across. Anyhow it run fine for a while and now it seems to throw this error every few days or so, If I reboot the server or restart cumulus it will run ok till it throws the error again.

I/O error 32 is a "sharing violation" affecting file cumuluswebtags.txttmp (the temporary file which Cumulus will create when processing the cumuluswebtags.txt file that you've asked it to process). Most likely cause is anti-virus or something similar.

never thought of the installed AV being the cause and it's the only thing I never looked at, I'll add the cumuluswebtags.txttmp to the AV ignore list and see what happens, Thanks for the help steve

well the error is back, been back a few weeks on/off, still same error, a system reboot fixes the error for a day or so then it starts again failing every 2hr's roughly

Are you doing anything else with the cumuluswebtags.txt file other than getting Cumulus to do a realtime ftp upload with it? Could you show a screenshot of the Files tab in your internet settings?

Can you upload the latest bugreport.txt file so I can see if it's exactly the same?

Apologies for the late reply, it's exactly the same error as previous. The only difference (after you suggested it might be the AV ) is that I added cumulus and cumulus toolbox to the ignore list in my AV, it was working ok then the error started back up,I've got an inkling that it could be because I run my own server and both these programs are on it and I haven't added that part to the AV ignore.

You need to make sure you set the entire Cumulus directory hierarchy to be ignored, and not just the executable. Your machine running Cumulus is actually running XP rather than Vista as in your profile, is that correct?

Aye the server is running WinXp Pro (sorry forgot to state that),both cumulus + cumulus toolbox hierarchy are all ignored by the AV, It's cert a strange one as a reboot fixes the error for a day then it re-occurs with a vengeance and at other times it can run a few days without throwing the error, I'm wondering if it could be time related, as cumulus is set to upload to 3 sites, weather underground is set to upload every 15min and rapid fire (just un-ticked 15min ), pws is set to 25min and aprs is set to 20min, realtime is set at 9sec, I'll try anything to fix it

And the only thing you're doing (intentionally) with that cumuluswebtags.txt file is realtime upload?

Just out of curiosity ... your Cumulus is processing the file 'cumuluswebtags.txt' ... how do you have that operation setup in Cumulus - a screen shot of the the 'Internet Settings/Files' windows ('Configuration' pull down menu -> 'Internet' option -> 'Files' tab) could offer some indication/information...

as you can see the only file is webtags, realtime is selected, nothing else is being done to the file,

Those settings don't match the bug report, and I don't really understand what you're trying to achieve with them.

You have 'binary' set but it's not a binary file (but as it happens that doesn't really matter here as it only affects ftp).
You don't have 'process' set but the crash was in the code which processes the web tags.
You don't have 'ftp' set, so (with 'process' not being set) all Cumulus is doing here is making a direct copy of a file.

I think that you must have previously had the 'process' option set?

None of this helps explain the problem, though. Cumulus is trying to open the cumuluswebtags.txttmp temporary file for writing, and Windows says that something else has the file open already.

You haven't given a full path for the output file, so you're relying on the Cumulus working directory being set up correctly. It's better to give a full path name. That might actually be related to the problem...

I changed the settings after I added the programs to AV ignore list, as i wasn't certain if these were the problem or adding to it. But seeing as the problem still exists it wasn't these settings. The binary setting was how I read Toolbox needed setting up (unless I read it wrong)

steve wrote:You haven't given a full path for the output file, so you're relying on the Cumulus working directory being set up correctly. It's better to give a full path name. That might actually be related to the problem...

So if I follow correctly it should be the full remote address to the cumulus/webtags in the remote name column? or where you meaning in the local file names column? as it is the full path in that section

You need the full path for the remote file; either a location on your PC if you're just copying, or a full path on the ftp server if you're using ftp. I'm not sure where the Toolbox comes into it? The binary setting is for the ftp to the server (within Cumulus).

toolbox is why cumulus crashes, if I leave the toolbox off it will run flawless for days/weeks even, but as soon as I start toolbox if throws the afore mentioned error.