Cumulus Support

Recently Godaddy.com has had some significant problems with their hosting which affected ftp, among other things. It appears now that for my hosting account they have gotten things back to the "pre-meltdown" point, though others are still having problems.

The problem that I've been having for the last month or two is with inconsistent realtime.txt upload intervals...or at least that's what I take as being. I have my update interval set for 15 seconds. But while watching the data on my Cumulus/Saratoga-template website update I might see the first update at 15 seconds (sometimes 30 seconds), the next will be 30 seconds, the next 30 seconds, every now and then it will go back to 15 seconds, then maybe to 35 seconds, and may even stretch out to 60 seconds. No rhyme or reason (that my ignorant eyes can spy) but the most frequently used interval is 30 seconds.

I've attached (I think) the zipped up diags along with a few of the ftp files that might(?) shed some light on this...filename beeweather.zip. I did see in one of the files in the diags folder some 500 errors at the bottom of the file...but I'm ignorant as to what to do with it.

I'm still running v194/b1079 so if I need to update the software (I know I need to, but this version is running so nicely ) before getting feedback I understand.

Thanks,
Ed

It's taking slightly longer than 15 seconds (most of the time) to upload realtime.txt and your three other files. So the next upload slot gets missed and your interval becomes 30 seconds. If you change to 20 seconds, you might get a more even interval, but basically the ftp server and/or your connection to it can't cope with a 15 second upload interval for the files you are sending.

The 426 and 500 errors are problems with the ftp server or the connection to it.

As an aside, I note from the diags file that you have this issue: http://wiki.sandaysoft.com/a/FAQ#Cumulu ... t_start_up

I've deleted your attachment as it contained passwords (in cumulus.ini).

Thanks for the feedback, Steve. I've seen other's who have uploaded their Cumulus.ini files and that you took care of (removed the file) and I always thought..."I'd never do that!". Oh well, just goes to show me never to say that, eh? Thanks for removing it for me...I guess it was time for an overall password change anyhow.

I went ahead and changed Cumulus to have the same archive interval as the VP2 console and it seems to make Cumulus faster to start up. Thanks for pointing that out to me.

The ftp/upload interval is still giving me fits, though. I've tinkered with the interval time and even if I kick it up to 25 seconds I still might get somewhere between 15 and 60 second intervals, though it seems like the majority settle in around 30 seconds. I moved the interval time up to 45 seconds and it seemed to hit on 54 seconds.

As for the files that I've been uploading, it looks like I was still uploading two sets of SS gauges...I think when I was installing the gauges and finally overcame some problems and got them working (the problem being between my ears, not the gauges) I was afraid to remove the original gauge upload that I started with. Regardless, I removed the first instance of the ss-gauge file (was using a different file name) from the upload list. *Also*, I was apparently uploading two different system status files...I culled the unused one of those, also.

********UPDATE!!!!!!!*********
Stopping those two files from being processed and uploaded appears to have fixed the problem!!! I actually have the upload interval set at 14 seconds and it's hitting on 14-15 seconds probably 95% of the time now and 30 seconds very rarely!!!!

When you mentioned about the system not having enough time to upload the realtime.txt file and the "other three files" I wasn't sure exactly which "other" files you were referring to. It did remind me, though, that back when I was getting the SS gauges working and also tinkering with the system info page that I had left a couple of extra files uploading (being ignorant...and a little dumb) I left those files uploading as I didn't want to risk "something" not getting that data that might be needing it. I never got around to checking and seeing if those older files were really needed or not...apparently they weren't and actually caused a problem by leaving them there.

My problem was self-induced.

Thanks for getting me headed in the right direction, Steve!!!

Ed