From nobody Fri May 12 03:35:26 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QHZCv4ctlz4BQpd for ; Fri, 12 May 2023 03:35:39 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHZCv337cz40Wb for ; Fri, 12 May 2023 03:35:39 +0000 (UTC) (envelope-from pprocacci@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oi1-x231.google.com with SMTP id 5614622812f47-3940f546923so2549143b6e.2 for ; Thu, 11 May 2023 20:35:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683862538; x=1686454538; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Y4EMU+Uw4Xx2OoMMuwr0SGYbbXzmbr+rJQ+dnIHLjR0=; b=hEYBEC4bm5zzXjzjLg8mzvRKD+CcZ/onZcPyO9mKpB/ZRs6R0Z7ojHD5h/A4NrIxJr OQBjfkzF5NotW9Mt52rGVzkiW1BZ3vkXTpEG7gBtAYsB7kRaiaXNs/DdiYDf1I1Fjofh SxBOX/siKuexSs5nRpjHNsSlm6EmCv7rgtHP1cwppYGCGat5Igz2MhMD6S9WaztTR5G8 ziR4eZD+LhMEtchmC6G1cJzuwQnKLpAzHUwIprBch0bB1ghYkAlz7PHnTSI/SFswMKg9 34eGQsg/Tw4Q1q3AWzJ3nkc41Ffpc6NtNxMxJ4ZWkX4+PNNpQJzScunI3xbHP5KtT1JD ONEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683862538; x=1686454538; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Y4EMU+Uw4Xx2OoMMuwr0SGYbbXzmbr+rJQ+dnIHLjR0=; b=ikngB6vx1FdcG8g7u96GkiuwzG6h8UWYdrMZ03J8QLDuG4xnLrXsXqvbMECdfkNG5O tei9c+/OIuBJeK254Onk8RVC9gN4rVqHfKCmjw+MjsDvTtnC5kCrzZZ26uNcf2jFfAFH lu3Gngyo6bljnnnGfFmMcSS8QFsvyBhK3boMP2IAD8T/tzrClSAP93UG2B9KT8X7JWmv axFDL+PhDfT6mq9i8Ah7VTADWSqwV7pOMlCgBFmdXfS9i7cloBnV9ztCmDjmvt6DqddV UdAcAWKXsF+V0rlW8vlhYJDIotvGDMj2pkW8juRpJXVMIL8GBJoPj6zTkVHZOEsTV/1i npZA== X-Gm-Message-State: AC+VfDyd4+DpZHWUaoYDbZQJ4rfNW3LIx1cllq18k+qewgIuktGaKAx/ TV1sn8N++rdnujX0B0hADAZxJKqIm8TRha72ig== X-Google-Smtp-Source: ACHHUZ6HTOYH5WG32GHpe/O2DFJ1ZAH9230qdCsy4evYgfjFigWwE7DYvs3PigaZ0cnLusQqtrTtkgru28C6mZEuXCc= X-Received: by 2002:a05:6808:628b:b0:394:31c9:2ee2 with SMTP id du11-20020a056808628b00b0039431c92ee2mr3427575oib.40.1683862537836; Thu, 11 May 2023 20:35:37 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: <8264bee7-f13f-a1a1-552a-09fb34973b26@paz.bz> In-Reply-To: <8264bee7-f13f-a1a1-552a-09fb34973b26@paz.bz> From: Paul Procacci Date: Thu, 11 May 2023 23:35:26 -0400 Message-ID: Subject: Re: apache24 reload dies with SIGSEGV To: Jim Pazarena Cc: freebsd-questions@freebsd.org Content-Type: multipart/alternative; boundary="0000000000006b1b7a05fb76cc58" X-Rspamd-Queue-Id: 4QHZCv337cz40Wb X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000006b1b7a05fb76cc58 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, May 11, 2023 at 11:31=E2=80=AFPM Jim Pazarena wrote= : > I just loaded two servers with a fresh 13.2 install . Along with a fresh > install of 2.4.57 Apache . > > both have public IPs > one is https , while the other is not . > > an "./apache24 start" works as expected . It passes the sanity check , > announces Syntax OK , and runs . > > However , if I issue an "./apache24 reload" > it still announces Syntax OK , followed with: > Performing a graceful restart > > but it does not start . > running "dmesg" , I see: > pid xxxx (httpd), jid 0, uid 0: existed on signal 11 > > If I run an ".apache24 start" > it fires up as expected and runs as expected . > > What is a reload doing extra that a start does not do , that could be > causing a SIGSEGV ? > oh yes, a restart works as expected > a reload dies . > > Suggestions would be most appreciated . > > You need to generate a core and run gdb against it getting a backtrace. -- This ultimately would provide you very specifically where it's getting foul'd up. ~Paul --=20 __________________ :(){ :|:& };: --0000000000006b1b7a05fb76cc58 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, May 11, 2023 at 11:31=E2= =80=AFPM Jim Pazarena <fquest@paz.bz> wrote:
I j= ust loaded two servers with a fresh 13.2 install . Along with a fresh
install of 2.4.57 Apache .

both have public IPs
one is https , while the other is not .

an "./apache24 start" works as expected . It passes the sanity ch= eck ,
announces Syntax OK , and runs .

However , if I issue an "./apache24 reload"
it still announces Syntax OK , followed with:
Performing a graceful restart

but it does not start .
running "dmesg" , I see:
pid xxxx (httpd), jid 0, uid 0: existed on signal 11

If I run an ".apache24 start"
it fires up as expected and runs as expected .

What is a reload doing extra that a start does not do , that could be
causing a SIGSEGV ?
oh yes, a restart works as expected
a reload dies .

Suggestions would be most appreciated .



--0000000000006b1b7a05fb76cc58--