Cumulus Support

I have ticked to upload the graph data files which MX does to 'public_html/cumulus' as can be seen from my settings.
However, randomly / some how / several times a day MX decides to ftp them to the same level as 'public_html' as can be seen below.
Any suggestions?

I've noticed the same thing. Presumably the 'change directory' fails occasionally for some reason, so the uploads go into the home directory. I haven't got around to running with ftp logging on to see what happens.

I could be wrong but shouldn't it be /public_html/cumulus rather than public_html/cumulus?

That is how mine is and it works fine.

It depends on how your hosting is set up. Using an absolute path (starting with a slash) may not necessarily give the result you expect. A relative path is usually safer, because it's clear what the effect should be. I have used the same (relative) path with Cumulus 1 for years successfully, but for some reason with MX there is this occasional problem.

water01 wrote:I could be wrong but shouldn't it be /public_html/cumulus rather than public_html/cumulus?

That is how mine is and it works fine.

I don't believe so, I use that in Cumulus 1 and in several other programs to ftp files. And, most of the time in MX it works just fine.

Steve, not sure if this is relevant but I have the following error for random graph files. This is not reported consistently just randomly through the day.

2015-02-20 06:30:24.971 Error uploading humdatad3.json to humdatad3.json : Timed out trying to read data from the socket stream!

Ok, just checked my server, the time on the last .json files ftp'ed to the wrong directory correspond with the following error.

2015-02-21 06:45:23.528 Error uploading wdirdatad3.json to wdirdatad3.json : Timed out trying to read data from the socket stream!
2015-02-21 06:45:39.760 Error uploading humdatad3.json to humdatad3.json : Timed out trying to read data from the socket stream!

As you were having communication problems at that time, it's reasonable to assume that the 'change directory' was also affected. I'll see if I can rework the code so that it doesn't attempt to do the uploads if the CWD fails.

Steve, could you explain the error for me? 'Error uploading' is obviously between my server and my host but the 'Timed out trying to read data from the socket stream!' is that a local issue?

oh, and 'CWD'?

Perhaps I'm just being a bit slow today...

The 'Timed out...' message is the FTP component saying it isn't getting a response from the FTP server.

CWD = Change Working Directory, it's an FTP command.

Ok, thank you.

I think I know what's happening now. The CWD doesn't fail. It appears that if the ftp connection times out, the ftp client automatically reconnects - which is nice - but unfortunately it means that the working directory is now the 'home' directory, so the remaining uploads go to the wrong place.

I think I will have to change my approach so that it uses the full path for the remote files, and avoids doing the CWD at all. I've asked the author if my theory seems reasonable, and whether he has any better suggestions.

Thanks for the update.

Appears fixed in 3021, been running for 24 hours with all files to correct directory. This was happening several times a day.

To All,

I just installed CumulusMX and having the same error when sending to my ftp.

Error uploading dailytemp.json to /webspace/curtiszmweather.com/cumulus/cumulusmx/daily.json : Timed out trying to read data from the socket stream!

CumulusMX Ver: 3.0.0 b3029

P.S. CumulusMX doesn't like IE 11. running it in Chrome
OS = Windows 10

Note: Cumulus 1.9.4 uploads to my ftp just fine.

Please assist...Thank you.