Re: Fixed site exec & tar BUT have a problem with 2 min timeout: Connection closed

From: Bela Lubkin (belal_at_sco.com)
Date: 10/19/04

  • Next message: Magda Hewryk: "Re: Fixed site exec & tar BUT have a problem with 2 min timeout: Connection closed" 
    Date: Mon, 18 Oct 2004 23:27:23 GMT
To: scomsc@xenitec.ca

    Magda Hewryk wrote:

    > Adjusting define MAX_GARGV 1000' in popen.c to a higher number solved
    > the problem of having all files included into the tarball file. This
    > works like a charm now!
    >
    > Now I have a timeout issue. I've increased all possible timeouts in
    > ftpaccess file but when runnign "quote site exec tar --gzip -cf
    > tarball1.tar.gz *.tif" command the user is timed out. Always after 2
    > min user is timed out.
    > However, the command is still running on the server and the tarball
    > file is completely increaed with all the *.tif files.
    >
    > User gets the message "Connection closed by remote host".
    > How can I fix this? Any help? All setups I've done in ftpaccess are
    > not helping.
    >
    > I've tested the connection with mget command and the regular wuftpd
    > (with no site exec) can stay open more than 10 min (tested with mget
    > with huge files).
    >
    >
    > Any hint how can I solve this issue?

    > =======================
    > # mnh To keep alive TCP connection
    > keepalive yes
    >
    > # mnh To keep idle for 2700 sec (45 min). Default is 900 sec (15
    > min.)
    > timeout idle 2700
    >
    > # mnh How long the daemon will wait for some activity on the data
    > connection (default 1200 sec)
    > timeout data 3600
    > timeout maxidle 3600
    > timeout RFC931 3600
    > timeout connect 3600

    Testing with mget of huge files tests something else. As long as it's
    doing continuous data transfer, ftpd won't think it's idle at all.

    There are two timeouts in the source which default to 2 minutes:

      unsigned int timeout_accept = 120; /* Accepting data connection: 2 minutes */
      unsigned int timeout_connect = 120; /* Establishing data connection: 2 minutes */

    You've reset "connect" to an hour; try "accept" as well.

    If changing it in the config file doesn't work, maybe you've put the
    config file in the wrong place. Try changing the defaults in the source
    (timeout.c). To figure out precisely which timeout you're hitting, try
    setting each of the defaults to a different multiple of 30 seconds:

      unsigned int timeout_idle = 30;
      unsigned int timeout_maxidle = 60;
      unsigned int timeout_data = 90;
      unsigned int timeout_rfc931 = 120;
      unsigned int timeout_accept = 150;
      unsigned int timeout_connect = 180;

    Run that version of the daemon; do your "site exec"; see how long it
    runs before timing out. That tells you which timeout it was hitting.
    Then put all back to normal except that one.

    Or figure out where it's looking for the config file. The wuftpd that
    comes with OSR5 looks for /etc/ftpaccess; but your compile may be using
    a different path.

    >Bela<

  • Next message: Magda Hewryk: "Re: Fixed site exec & tar BUT have a problem with 2 min timeout: Connection closed"

    Relevant Pages