You are not logged in.
I am trying to get the simplest tFTPGet to work. I fill in all of the server info, user, password, remote file, local file, etc.. When I run the job, it pauses for a second, and then shows complete. No errors. But no file either.
I can use the exact same parameters in another ftp client (FileZilla) adn everything works fine.
Question: is there a log written somewhere that I could look for to see what the problem could be that tFTPGet is having?
You will find a checkbox called 'Print message' in tFTPGet-->Advanced Settings.
Select it and you will get return value if all you set are correct like this.
[statistics] connecting to socket on port 3889 [statistics] connected file [abc.txt] downloaded successfully. [statistics] disconnected
This is a way to test whether this component works fine.
Thanks pedro - but even with that checkbox ticked, here is what my output looks like:
Starting job LoadLinkShareFTP at 09:21 07/05/2012.
[statistics] connecting to socket on port 3339
Job LoadLinkShareFTP ended at 09:21 07/05/2012. [exit code=0]
I discovered by stepping thru in debug that the tFTPGet component first verifies that the file to be downloaded actually exists on the ftp host first. Which is great, but this particular ftp host has this strange arrangement where the files that you see in the folders are not REALLY the files to download - they have an extra part on the filename, but when you do a get, you're supposed to leave that extra part off, and then the server will dynamically create the REAL file for you.
I guess it's so that the ftp host can support "get on demand" where the file doesn't have to exist and take up space until someone requests it.
So tFTPGet really is doing its job, but I wonder if there's a way to tell it to not worry if the file is there or not, and just do the get?
Thanks again for listening
No, active mode made no difference.
What I ended up doing was: I'm now using a community-contributed component from the Talend Exchange called tFTPGetFile - it doesn't check if the file exists on the ftp site before doing the get, so it works great.
Thanks for looking this over anyway.