From owner-freebsd-stable@freebsd.org Tue Mar 30 15:41:08 2021 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C6BFC57AC78 for ; Tue, 30 Mar 2021 15:41:08 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: from mail-ed1-f47.google.com (mail-ed1-f47.google.com [209.85.208.47]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F8tvm4Wxcz4v2y; Tue, 30 Mar 2021 15:41:08 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: by mail-ed1-f47.google.com with SMTP id z1so18759010edb.8; Tue, 30 Mar 2021 08:41:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=b+EQ4LsR+DdsGKCC8SA1jgffthd3bjCDG1C+lqNIIow=; b=uPQKAuqNKPJIEjA6flbNJgCmp1mMd+uUJuezUPlbm+6HfOnFVd8RHl78gREWgUK80b LKyFgEtQ9RRx/XSOS823edshqesO1ujLIz1f8a7TZ5TNTWVQtdnSpFXcXajNjgUGvZ5+ PmDXA/c7QzlfnyIdyroqGEPFM2BHolHXuQavUHl1o9fdaJmUF+4FmVwnJev36qLP7RnO KmL0Mif4110hsLALpQLMpNQgBvy5+yWL+0X3JyO3FR/GJV3IiQZEHdJbxo0abTPFuDJ4 Q8bT4akuDnNoci/Ki4suul6eMgbFIMU7we1ztfIQNYqbCghtkaGNQMa1O0LvpbTuInKy 1I/g== X-Gm-Message-State: AOAM533cIKdJH3IMZ9DV9mYpnXYZcOGLSzsGHSdVl/vPkJZiAU3w0pYx /JXEiopJxODlVSwqI3cKSypIbYHnT6c= X-Google-Smtp-Source: ABdhPJzZsX1FSoBihUXcACYELlsYciOKAtHKb1byhqNq1Teh0i4SWbBLXicqNjZqLEXCXcDRbqLYaA== X-Received: by 2002:a05:6402:698:: with SMTP id f24mr19797478edy.262.1617118866836; Tue, 30 Mar 2021 08:41:06 -0700 (PDT) Received: from mail-ed1-f41.google.com (mail-ed1-f41.google.com. [209.85.208.41]) by smtp.gmail.com with ESMTPSA id h13sm11596859edz.71.2021.03.30.08.41.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 30 Mar 2021 08:41:06 -0700 (PDT) Received: by mail-ed1-f41.google.com with SMTP id bf3so18743422edb.6; Tue, 30 Mar 2021 08:41:06 -0700 (PDT) X-Received: by 2002:a50:ee18:: with SMTP id g24mr34669024eds.267.1617118865962; Tue, 30 Mar 2021 08:41:05 -0700 (PDT) MIME-Version: 1.0 References: <94CCFC59-B381-40B1-8F85-F86D87A16B53@cretaforce.gr> In-Reply-To: <94CCFC59-B381-40B1-8F85-F86D87A16B53@cretaforce.gr> From: "Jonathan T. Looney" Date: Tue, 30 Mar 2021 11:40:55 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: FreeBSD 13.0-RC4 and Nginx process "stuck" during restart To: Christos Chatzaras Cc: FreeBSD-STABLE Mailing List , "gjb@freebsd.org" , Konstantin Belousov X-Rspamd-Queue-Id: 4F8tvm4Wxcz4v2y X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Mar 2021 15:41:08 -0000 On Mon, Mar 29, 2021 at 3:57 PM Christos Chatzaras wrote: > Hello, > > > I upgrade from 12.2 to 13.0-RC4 and I notice a strange issue with Nginx. > > When I run "service nginx restart" in some (random) servers it > doesn't complete the restart and it "stucks" at "Waiting for PIDS: 20536." . > > I can kill the 20536 process and then restart completes. > > > procstat -kk 20536: > > PID TID COMM TDNAME KSTACK > 63094 100505 nginx - mi_switch+0xc1 > sleepq_catch_signals+0x2e6 sleepq_wait_sig+0x9 _sleep+0x1be > kern_sigsuspend+0x164 sys_sigsuspend+0x31 amd64_syscall+0x10c > fast_syscall_common+0xf8 > > > I found this commit: > > > https://cgit.freebsd.org/src/commit/?id=dbec10e08808e375365fb2a2462f306e0cdfda32 > > Could this be related? > Yes, it could be related. Because of the timing of when we first saw the behavior, I assumed the trigger for the behavior (which remains unknown) only existed in main. However, it is possible that this behavior is now being triggered in 13.0. Are you able to reliably reproduce this? I was never able to do that. A reliable reproduction may help narrow down the change which triggered this behavior. I can certainly MFC the patch to stable/13. re@ will need to decide whether to admit it to the release branch. Jonathan