I am newbie. Can you elaborate on enabling slow logging? Thanks Adi
On Fri, Jan 22, 2016 at 7:58 AM, Alan Carroll <[email protected] > wrote: > I might try enabling slow logging at around 20..25 seconds and see what > part of the transaction is slow enough to cause the client to abort. This > should also help determine if the client aborts are due to the clients or > because the transaction took too long. > > > > On Wednesday, January 20, 2016 5:33 PM, Adi Mallikarjuna Reddy V < > [email protected]> wrote: > > > Hello, > > We are seeing an higher number of ERR_CLIENT_ABORT/200 errors in our usage > of Traffic Server. > > Our primary purpose of traffic server is only to act as Reverse Proxy and > mainly for SSL termination (without caching). > > We are currently using: > > Traffic Server version - 5.3.0 > OS - Red Hat Enterprise Linux Server release 6.5 > > > The following are the configuration parameters: > > CONFIG proxy.config.http.keep_alive_no_activity_timeout_in INT 115 > CONFIG proxy.config.http.keep_alive_no_activity_timeout_out INT 120 > CONFIG proxy.config.http.transaction_no_activity_timeout_in INT 300 > CONFIG proxy.config.http.transaction_no_activity_timeout_out INT 300 > CONFIG proxy.config.http.transaction_active_timeout_in INT 900 > CONFIG proxy.config.http.transaction_active_timeout_out INT 0 > CONFIG proxy.config.http.accept_no_activity_timeout INT 300 > CONFIG proxy.config.http.background_fill_active_timeout INT 120 > CONFIG proxy.config.http.background_fill_completed_threshold FLOAT > 0.500000 > CONFIG proxy.config.http.connect_attempts_max_retries INT 0 > CONFIG proxy.config.http.connect_attempts_max_retries_dead_server INT 3 > CONFIG proxy.config.http.connect_attempts_rr_retries INT 3 > CONFIG proxy.config.http.connect_attempts_timeout INT 320 > CONFIG proxy.config.http.post_connect_attempts_timeout INT 1800 > CONFIG proxy.config.http.down_server.cache_time INT 300 > CONFIG proxy.config.http.down_server.abort_threshold INT 10 > > > Thanks > Adi > > > >
