Hi, Can anybody please respond to this ?
-Paras On Thu, Aug 13, 2009 at 3:13 PM, Paras Fadte<[email protected]> wrote: > Following is the output of varnishstat -1 . Also ,do I have to restart > varnish when I change the "connect_timeout" parameter ? I had > changed it by telnetting to port 99 and using param.set to set new > value to it. Its currently set to 1 second. > > ./varnishstat -1 > > uptime 63373 . Child uptime > client_conn 634043 10.00 Client connections accepted > client_req 17826332 281.29 Client requests received > cache_hit 9499758 149.90 Cache hits > cache_hitpass 18026 0.28 Cache hits for pass > cache_miss 8306918 131.08 Cache misses > backend_conn 8294978 130.89 Backend connections success > backend_unhealthy 0 0.00 Backend connections not attempted > backend_busy 0 0.00 Backend connections too many > backend_fail 37154 0.59 Backend connections failures > backend_reuse 176 0.00 Backend connections reuses > backend_recycle 4135 0.07 Backend connections recycles > backend_unused 0 0.00 Backend connections unused > n_srcaddr 1128 . N struct srcaddr > n_srcaddr_act 94 . N active struct srcaddr > n_sess_mem 1550 . N struct sess_mem > n_sess 251 . N struct sess > n_object 296920 . N struct object > n_objecthead 297600 . N struct objecthead > n_smf 594501 . N struct smf > n_smf_frag 5072 . N small free smf > n_smf_large 2 . N large free smf > n_vbe_conn 79 . N struct vbe_conn > n_bereq 233 . N struct bereq > n_wrk 129 . N worker threads > n_wrk_create 6518 0.10 N worker threads created > n_wrk_failed 0 0.00 N worker threads not created > n_wrk_max 1689251 26.66 N worker threads limited > n_wrk_queue 0 0.00 N queued work requests > n_wrk_overflow 40268 0.64 N overflowed work requests > n_wrk_drop 0 0.00 N dropped work requests > n_backend 7 . N backends > n_expired 7859618 . N expired objects > n_lru_nuked 122535 . N LRU nuked objects > n_lru_saved 0 . N LRU saved objects > n_lru_moved 6525309 . N LRU moved objects > n_deathrow 0 . N objects on deathrow > losthdr 1395 0.02 HTTP header overflows > n_objsendfile 0 0.00 Objects sent with sendfile > n_objwrite 17776012 280.50 Objects sent with write > n_objoverflow 0 0.00 Objects overflowing workspace > s_sess 634043 10.00 Total Sessions > s_req 17826354 281.29 Total Requests > s_pipe 0 0.00 Total pipe > s_pass 18274 0.29 Total pass > s_fetch 8294976 130.89 Total fetch > s_hdrbytes 7506851578 118455.05 Total header bytes > s_bodybytes 33144737427 523010.39 Total body bytes > sess_closed 101942 1.61 Session Closed > sess_pipeline 0 0.00 Session Pipeline > sess_readahead 0 0.00 Session Read Ahead > sess_linger 0 0.00 Session Linger > sess_herd 17790160 280.72 Session herd > shm_records 1322178282 20863.43 SHM records > shm_writes 48024610 757.81 SHM writes > shm_flushes 1486419 23.46 SHM flushes due to overflow > shm_cont 3563 0.06 SHM MTX contention > shm_cycles 596 0.01 SHM cycles through buffer > sm_nreq 16778276 264.75 allocator requests > sm_nobj 589427 . outstanding allocations > sm_balloc 3745964032 . bytes allocated > sm_bfree 549003264 . bytes free > sma_nreq 0 0.00 SMA allocator requests > sma_nobj 0 . SMA outstanding allocations > sma_nbytes 0 . SMA outstanding bytes > sma_balloc 0 . SMA bytes allocated > sma_bfree 0 . SMA bytes free > sms_nreq 31613 0.50 SMS allocator requests > sms_nobj 0 . SMS outstanding allocations > sms_nbytes 18446744073709550684 . SMS outstanding bytes > sms_balloc 14697712 . SMS bytes allocated > sms_bfree 14698178 . SMS bytes freed > backend_req 8294971 130.89 Backend requests made > n_vcl 1 0.00 N vcl total > n_vcl_avail 1 0.00 N vcl available > n_vcl_discard 0 0.00 N vcl discarded > n_purge 1 . N total active purges > n_purge_add 1 0.00 N new purges added > n_purge_retire 0 0.00 N old purges deleted > n_purge_obj_test 0 0.00 N objects tested > n_purge_re_test 0 0.00 N regexps tested against > n_purge_dups 0 0.00 N duplicate purges removed > hcb_nolock 0 0.00 HCB Lookups without lock > hcb_lock 0 0.00 HCB Lookups with lock > hcb_insert 0 0.00 HCB Inserts > esi_parse 0 0.00 Objects ESI parsed (unlock) > esi_errors 0 0.00 ESI parse errors (unlock) > > > > > > On Thu, Aug 13, 2009 at 2:50 PM, Tollef Fog > Heen<[email protected]> wrote: >> ]] Paras Fadte >> >> | I have tried setting the "first_byte_timeout" value to 300 but still >> | sometimes receive the 503 error . Should I increase the >> | "connect_timeout" value ? would that help ? Its default value is 0.4 >> | seconds >> >> It might help to increase the connect timeout, yes. It would be helpful >> if you posted the output of varnishstat -1 >> >> -- >> Tollef Fog Heen >> Redpill Linpro -- Changing the game! >> t: +47 21 54 41 73 >> _______________________________________________ >> varnish-misc mailing list >> [email protected] >> http://projects.linpro.no/mailman/listinfo/varnish-misc >> > _______________________________________________ varnish-misc mailing list [email protected] http://projects.linpro.no/mailman/listinfo/varnish-misc
