Cumulus will NOT FTP! HELP!

[steve]

And where is that supposed to be coming from - one of the files in your earlier screenshot of the 'files' tab?

[William Grimsley]

Um, yeah, I think so. Both of the screenshots in my last post, were from the ajax-dashboard.php file which is in one of the fields on the "Files" tab.

[steve]

It seems odd that your graphs and the realtime.txt file are being uploaded, but that file apparently not. Are you sure it's not the problem that David suggested, that the file isn't on your PC at the place you've configured it?

If you still think it's an FTP problem, turn on ftp logging and look at ftplog.txt.

[William Grimsley]

Ah, sorry. I just remembered, Cumulus doesn't need to process and FTP that file! I don't know why it was there, as the ajax-dashboard.php file, didn't exist in that folder!

Ok, I turned on ftp logging, for a few minutes.

I've attached the ftplog.txt file.

[steve]

The only error in there is that you don't have an 'images' folder:

17:38:14:718 FTP Command: CWD images
17:38:14:719 05280450 TriggerDataSent 1056
17:38:14:759 FTP Response: 550 Can't change directory to images: No such file or directory
17:38:14:759 >|550 Can't change directory to images: No such file or directory|

But as you don't seem to have an issue with the graphs, I assume that's not a problem. The two PHP files aren't mentioned in the log so I assume you've removed them from the config.

I can't offer any more help than that. Cumulus is doing everything you're telling it to do.

[William Grimsley]

Strange....Well, the ajax-dashboard.php file was only used when I needed <#tags> to be processed in the file, but then I found PHP tags to replace them, so I didn't need the file to be processed and FTPed by Cumulus!

Ken?

[William Grimsley]

Problem fixed! FINALLY!

The CU-tags.txt file (which Cumulus was trying to process and FTP) was not in the C:\Cumulus folder! So, I had to put the CU-tags.txt file back in the C:\Cumulus folder! As a result, the NOT CURRENT's went to CURRENT's, the records tables started updating, and the update bar started updating, too! Hooray!

[scotta1980]

iam also getting the same problem keeps saying FTP Error: FTP component not connected but it was working ok but suddenly stoped working how do you fix it
it is updating the realtime files ok but thats all
thanks

[steve]

Turn on ftp logging and look at ftplog.txt for errors.

[scotta1980]

i have switched on ftp logging but cant see any errors this is what i get

15:48:39:019 ! HighLevelAsync 0
15:48:39:019 02F69B50 Socket handle created 804
15:48:39:019 TWSocket will connect to 69.16.227.189:21
15:48:39:034 02F69B50 TriggerDataSent 804
15:48:39:394 FTP Response: 220 (vsFTPd 2.2.2)
15:48:39:409 >|220 (vsFTPd 2.2.2)|

15:48:39:409 FTP Session Connected, code = 0
15:48:39:409 ! HighLevelAsync 0
15:48:39:409 FTP Command: USER mm3lso
15:48:39:409 02F69B50 TriggerDataSent 804
15:48:39:628 FTP Response: 331 Please specify the password.
15:48:39:628 >|331 Please specify the password.|

15:48:39:628 ! HighLevelAsync 0
15:48:39:628 FTP Command: PASS
15:48:39:628 02F69B50 TriggerDataSent 804
15:48:39:925 FTP Response: 230 Login successful.
15:48:39:925 >|230 Login successful.|

15:48:39:925 ! HighLevelAsync 0
15:48:39:925 ! HighLevelAsync done
15:48:39:972 Getting directory listing
15:48:39:972 FTP Command: PWD
15:48:39:972 02F69B50 TriggerDataSent 804
15:48:40:175 FTP Response: 257 "/"
15:48:40:175 >|257 "/"|

15:48:40:988 ! HighLevelAsync 0
15:48:41:050 FTP Command: PORT 192,168,1,68,8,246
15:48:41:113 02F69B50 TriggerDataSent 804
15:48:41:300 FTP Response: 200 PORT command successful. Consider using PASV.
15:48:41:300 >|200 PORT command successful. Consider using PASV.|

15:48:41:300 ! HighLevelAsync 0
15:48:41:316 FTP Command: NLST
15:48:41:316 02F69B50 TriggerDataSent 804
15:48:41:644 ! Data Session requested
15:48:41:644 02F6A310 Socket accepted 916
15:48:41:644 02F6A310 TCustomWSocket.Shutdown 1 624
15:48:41:644 ! Data Session opened
15:48:41:644 FTP Response: 150 Here comes the directory listing.
15:48:41:644 >|150 Here comes the directory listing.|

15:48:41:644 ! Data Session closed
15:48:41:644 ! Next3GetAsync
15:48:41:644 02F6A310 TCustomWSocket.Shutdown 1 916
15:48:41:941 FTP Response: 226 Directory send OK.
15:48:41:941 >|226 Directory send OK.|

15:48:41:941 ! Next3GetAsync
15:48:41:941 ! HighLevelAsync 0
15:48:41:941 ! HighLevelAsync done
15:48:42:066 Uploading standard files
15:48:42:144 FTP Command: TYPE A
15:48:42:159 02F69B50 TriggerDataSent 804
15:48:42:331 FTP Response: 200 Switching to ASCII mode.
15:48:42:331 >|200 Switching to ASCII mode.|

15:48:43:159 Deleting index.htmtmp
15:48:43:159 FTP Command: DELE index.htmtmp
15:48:43:159 02F69B50 TriggerDataSent 804
15:48:43:300 FTP Response: 250 Delete operation successful.
15:48:43:300 >|250 Delete operation successful.|

15:48:44:159 Uploading C:\Cumulus\web\index.htm to index.htmtmp
15:48:44:159 ! HighLevelAsync 0
15:48:44:159 FTP Command: PORT 192,168,1,68,8,248
15:48:44:159 02F69B50 TriggerDataSent 804
15:48:44:316 FTP Response: 200 PORT command successful. Consider using PASV.
15:48:44:316 >|200 PORT command successful. Consider using PASV.|

15:48:44:316 ! HighLevelAsync 0
15:48:44:316 FTP Command: STOR index.htmtmp
15:48:44:316 02F69B50 TriggerDataSent 804
15:49:14:347 ! Aborting
15:49:14:363 FTP Session Closed
15:49:14:363 ! HighLevelAsync 0
15:49:14:363 ! Abort detected
15:49:14:363 ! HighLevelAsync done
15:49:14:363 02F6A310 TCustomWSocket.Shutdown 1 908
15:49:14:363 Renaming index.htmtmp to index.htm
15:49:14:363 ! HighLevelAsync 0
15:49:14:363 FTP Error: FTP component not connected
15:49:14:363 Aborting
15:49:14:363 ! Aborting

[steve]

The transfers are timing out; the server isn't responding within 30 seconds, so the transfer gets aborted:

15:48:44:316 02F69B50 TriggerDataSent 804
15:49:14:347 ! Aborting
15:49:14:363 FTP Session Closed

You're using active FTP mode; you could try what the server is suggesting, and try using passive FTP mode. That's in the internet settings in Cumulus.

[scotta1980]

thanks Steve that worked just UN ticked the use active ftp mode and delete before upload and all started working again this only happened since updating to the new 1.9.4 build 1061 but all working again thanks

[kingqueen]

Having soldered together my own temporary USB cable, I've got the weather station working and I'm playing with Cumulus. Which is a pretty amazing piece of software, Steve, as no doubt you know! A lot to read and get my head around though. I'm also thoroughly impressed by the support you're providing on these fora.

It appears to take 1 minute 15 seconds to upload the relevant files via FTP for each update, uploading about a quarter of a megabyte in the process. According to the log, there's just under a second's delay before each RNTO and each upload. Is this normal behaviour, not to worry about, and sensible pacing to stop taking up my upstream bandwidth, or is there something I have likely done wrong?

~Thanks ever so

KQ

[steve]

It appears to take 1 minute 15 seconds to upload the relevant files via FTP for each update, uploading about a quarter of a megabyte in the process. According to the log, there's just under a second's delay before each RNTO and each upload. Is this normal behaviour, not to worry about, and sensible pacing to stop taking up my upstream bandwidth, or is there something I have likely done wrong?

It's just the way FTP works, it's a very inefficient protocol. There are lots of protocol interactions taking place just to transfer a single file, and there are a lot of files to upload.

[steve]

Another point worth mentioning is that FTP in Cumulus runs as a background thread, which will slow it down somewhat.