Hello Allen, On Fri, Apr 12, 2019 at 06:01:14AM -0400, allenhe wrote: > Hi, > > The Nginx hangs at proxying request body to the upstream server but with no > error indicating what's happening until the client close the font-end > connection. can somebody here help give me any clue? following is the debug > log snippet: > > 2019/04/12 14:49:38 [debug] 92#92: *405 epoll add connection: fd:29 > ev:80002005 > 2019/04/12 14:49:38 [debug] 92#92: *405 connect to 202.111.0.40:1084, fd:29 > #406 > 2019/04/12 14:49:38 [debug] 92#92: *405 http upstream connect: -2 > 2019/04/12 14:49:38 [debug] 92#92: *405 posix_memalign: 0000000001CCA480:128 > @16 > 2019/04/12 14:49:38 [debug] 92#92: *405 event timer add: 29: > 2000:1555051780835 > 2019/04/12 14:49:38 [debug] 92#92: *405 http finalize request: -4, > "/inetmanager/v1/configinfo?" a:1, c:2 > 2019/04/12 14:49:38 [debug] 92#92: *405 http request count:2 blk:0 > 2019/04/12 14:49:38 [debug] 92#92: *405 http run request: > "/inetmanager/v1/configinfo?" > 2019/04/12 14:49:38 [debug] 92#92: *405 http upstream check client, write > event:1, "/inetmanager/v1/configinfo" > 2019/04/12 14:49:38 [debug] 92#92: *405 http upstream request: > "/inetmanager/v1/configinfo?" > 2019/04/12 14:49:38 [debug] 92#92: *405 http upstream send request handler > 2019/04/12 14:49:38 [debug] 92#92: *405 http upstream send request > 2019/04/12 14:49:38 [debug] 92#92: *405 http upstream send request body > 2019/04/12 14:49:38 [debug] 92#92: *405 chain writer buf fl:1 s:323 > 2019/04/12 14:49:38 [debug] 92#92: *405 chain writer in: 0000000001CB5498 > 2019/04/12 14:49:38 [debug] 92#92: *405 writev: 323 of 323 > 2019/04/12 14:49:38 [debug] 92#92: *405 chain writer out: 0000000000000000 > 2019/04/12 14:49:38 [debug] 92#92: *405 event timer del: 29: 1555051780835 > 2019/04/12 14:49:38 [debug] 92#92: *405 event timer add: 29: > 600000:1555052378841 > 2019/04/12 14:50:17 [debug] 92#92: *405 http run request: > "/inetmanager/v1/configinfo?" > 2019/04/12 14:50:17 [debug] 92#92: *405 http upstream check client, write > event:0, "/inetmanager/v1/configinfo" > 2019/04/12 14:50:17 [info] 92#92: *405 epoll_wait() reported that client > prematurely closed connection, so upstream connection is closed too while > sending request to upstream, client: 202.111.0.51, server: , request: "GET > /inetmanager/v1/configinfo HTTP/1.1", upstream: > "http://202.111.0.40:1084/inetmanager/v1/configinfo", host: > "202.111.0.37:1102" > 2019/04/12 14:50:17 [debug] 92#92: *405 finalize http upstream request: 499
According to the log, request (323 bytes) is sent to the upstream server, but no response is sent back within the given time period. -- Roman Arutyunyan _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx