From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qt1-x843.google.com (mail-qt1-x843.google.com [IPv6:2607:f8b0:4864:20::843]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id A3BBB1F463 for ; Wed, 11 Sep 2019 17:36:33 +0000 (UTC) Received: by mail-qt1-x843.google.com with SMTP id r15so26238002qtn.12 for ; Wed, 11 Sep 2019 10:36:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=/fD+1bBnFPbSF/w/STObbzl2uRPeBnI57/1HtymY2p4=; b=bYXoz3yWZOQ4KL/Cyuy692BmLunwZJU+3v+r/xpstVOYqyr4uXAE3EX6jV0F577/4K hyWSZCgws8E0y1fR5tEj5DxP3QBp0p87wkeavcU1gkljhwIHXlAR3tGuOo7Jz1nwLbRG 03VVPm2KN4ZXYytrWlOVFeRDQzv4MwvmRL+2c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=/fD+1bBnFPbSF/w/STObbzl2uRPeBnI57/1HtymY2p4=; b=p/e860ewz9kR5hsZAHno2PPCb70azsL8Wgixq6WkcXhUHE0ss/H4ivvzulvQHTxjeg pyHpohP1DmnPHMnWNuWqUjOJLqHIS9lZ/pzKDC3ustRTajVLtLNBYYUzXk0jNTe2XM+D Sz8qlG/Ao5XasV6lxZRMdpTC6LuQFOP1lM2JUrYs6cwgclaGGPugWLNtSRN1ad27U+7k drWuvFczt5dOeZQARATzddSjt36K6mbROcforyOLwg7GOLHQ9H37lzAmm4KKSEEvtUJa FAIqRxS8VCOmtj9W0ficC0K7b37g59D1eXHW/2QK19n0cuGq8CvlzsSY/GABSq59D851 j3pg== X-Gm-Message-State: APjAAAXtCH6j3cnc9uTN9UERr146qcSofFseZ983MIhDak5+GrTHCUOH Y5wLvD7hiWZex9+sOQYHDEK/gg== X-Google-Smtp-Source: APXvYqwaaatQOEU5qHL9/wnDr9tQ6cUfqVtedDpfnDnkApOIRckTDSE1tO2Ed1exUWm7To4TuPfN4A== X-Received: by 2002:ac8:6746:: with SMTP id n6mr36555745qtp.128.1568223392715; Wed, 11 Sep 2019 10:36:32 -0700 (PDT) Received: from pure.paranoia.local ([87.101.92.157]) by smtp.gmail.com with ESMTPSA id 1sm10490022qko.73.2019.09.11.10.36.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 11 Sep 2019 10:36:32 -0700 (PDT) Date: Wed, 11 Sep 2019 13:36:28 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: httpd 502s [was: trying to figure out 100% CPU usage in nntpd...] Message-ID: <20190911173628.GA14147@pure.paranoia.local> Mail-Followup-To: Eric Wong , meta@public-inbox.org References: <20190908104518.11919-1-e@80x24.org> <20190908105243.GA15983@dcvr> <20190909100500.GA9452@pure.paranoia.local> <20190909175340.u5aq4ztfzukko7zb@dcvr> <20190910083820.GA8018@pure.paranoia.local> <20190910181224.urhyoo6av7mhjs67@dcvr> <20190911022215.GA309@dcvr> <20190911102436.GA21959@pure.paranoia.local> <20190911171250.vqqpaeb7sn34hv3s@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190911171250.vqqpaeb7sn34hv3s@dcvr> User-Agent: Mutt/1.12.1 (2019-06-15) List-Id: On Wed, Sep 11, 2019 at 05:12:50PM +0000, Eric Wong wrote: > Konstantin Ryabitsev wrote: > > To give some more data points, downgrading to f4f0a3be still shows a > > number of /tmp/PerlIO* (deleted) entries, but the number of pipes stays > > the same over time. If I switch to the latest master, the number of > > broken pipes grows steadily following each git pull (in the hundreds > > after 10 minutes of running). > > Thanks for that info, did those deleted entries eventually go > away (perhaps after several minutes)? They don't appear to go away -- since 10:23 UTC earlier today, they accumulated over 2,400 entries: # ls -al /proc/{2103,2104,2105,2106}/fd | grep deleted | wc -l 2427 # ls -al /proc/{2103,2104,2105,2106}/fd | grep pipe | wc -l 26 Curiously, I also have this datapoint that may or may not be making things more confusing. :) # ls -al /proc/{2103,2104,2105,2106}/fd | grep deleted | awk '{print $8}' | sort | uniq -c 695 10:24 356 10:27 843 14:45 175 14:46 6 14:50 372 17:19 4 17:20 11 17:23 So, they appear to show up in chunks and hang around together. For nginx configs, this is the relevant part: server { listen *:80 default_server; proxy_buffering off; location ~ ^(.*/(HEAD|info/refs|objects/info/[^/]+|git-(upload|receive)-pack))$ { proxy_pass http://localhost:8080; proxy_read_timeout 90; proxy_connect_timeout 90; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $http_x_forwarded_proto; proxy_set_header X-Forwarded-Port $server_port; } } When setting up lore, I also considered serving git via git-http-backend instead of passing it via public-inbox-httpd -- the only reason we didn't try that was because it complicated SELinux bits a bit. Can you think of a reason why we shouldn't server git requests directly via git-http-backend? Thanks for your help. -K