Your best friend for file transfer.

Fetch application logoFetch

Problems with mirroring (4 posts)

  • Started 10 years ago by jkick
  • Latest reply 10 years ago from jkick
  • jkick Member

    When using the mirror command to update a large file on our website, I keep getting the same message when it's is about 75% through with the update. The message is: Fetch could not put "mf1824c103-L.JPG" because the FTP Server dropped the connection. mf1824c103-L.JPG is a picture file in our shopping cart and sometimes the same thing happens with a different file, but always one of the pictures we have. I can upload and download the entire shopping cart without dropping the connection so I'm confused as to why this happens during mirroring.

    The Fetch transcript reads:
    RPUT_CHECKING_DATE: Local file mf1824c102-s.gif modified 08/15/2007 02:56 PM Remote file mf1824c102-s.gif modified 08/15/2007 02:56 PM, no need to upload
    MDTM mf1824c103-L.JPG
    421 No Transfer Timeout (300 seconds): closing control connection.
    RPUT_CHECKING_DATE: Local file mf1824c103-L.JPG modified 08/15/2007 02:56 PM Remote file mf1824c103-L.JPG modified 08/14/2007 07:56 PM, unsure of time zone, will upload
    TYPE I
    ftp_store_setup: 2,-30014 (state == RPUT_SETTING_UP)
    ABOR
    send_cmd():con_conn->Putline() returns 2,-50

    Any help is appreciated.

    Posted 10 years ago #

  • Scott McGuire Administrator

    Hi,

    I am not sure either why you would run into this problem when mirroring, when a regular upload of the same folder works. I will check with my co-workers and let you know if we have any thoughts.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 10 years ago #

  • Scott McGuire Administrator

    Hi,

    We believe the problem is that your server is set to drop connections if there is no activity after 5 minutes.

    When you use the Mirror command, Fetch can go a long time without actually uploading anything if not many files on your website have changed. But checking to see if files need uploading or not is not instantaneous, and so what happens is Fetch opens the connection to the server, spends 5 or more minutes finding out which files need uploading, and during that time the server closes the connection because no transfers took place.

    Unfortunately, for technical reasons, Fetch cannot reconnect in the middle of a Mirror operation, and so you get an error when Fetch actually finds the files that need uploading.

    In contrast, when you're uploading the whole website without using Mirror, there are transfers constantly happening, so the server never drops the connection.

    You could try checking the "Keep connections alive" preference in Fetch and see if that helps, but that preference does not work in all situations. (To find and set that preference, go to the Fetch menu, choose Prefererences, and click the General tab.)

    Otherwise, you should contact your hosting company - the folks who run the server - and ask if they could increase the time on the "no transfer timeout" setting of the server.

    Sorry not to have a better solution for you. Please let us know if you have any questions about the above.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 10 years ago #

  • jkick Member

    I'll try your suggestion and thanks for the explanation.

    Posted 10 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.