From nobody Fri May 12 05:48:06 2023 X-Original-To: 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 4QHd8m59PPz4BYn0 for ; Fri, 12 May 2023 05:48:08 +0000 (UTC) (envelope-from fquest@paz.bz) Received: from emailh.ca (emailh.ca [23.235.65.100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHd8l5kdXz4Dk7 for ; Fri, 12 May 2023 05:48:07 +0000 (UTC) (envelope-from fquest@paz.bz) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of fquest@paz.bz designates 23.235.65.100 as permitted sender) smtp.mailfrom=fquest@paz.bz; dmarc=none Received: from 254-68-235-23.gwaiicomm.com ([23.235.68.254] helo=[192.168.1.9]) by emailh.ca with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pxLdN-000OCz-4F; Thu, 11 May 2023 22:48:05 -0700 Message-ID: <026e3b63-0a7f-e8e9-d41d-1b03f8ac729d@paz.bz> Date: Thu, 11 May 2023 22:48:06 -0700 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 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: apache24 reload dies with SIGSEGV To: questions@freebsd.org Content-Language: en-US From: Jim Pazarena Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-1.08 / 15.00]; FAKE_REPLY(1.00)[]; NEURAL_HAM_MEDIUM(-0.93)[-0.925]; NEURAL_HAM_SHORT(-0.50)[-0.502]; NEURAL_HAM_LONG(-0.35)[-0.354]; R_SPF_ALLOW(-0.20)[+ip4:23.235.65.64/26]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:852, ipnet:23.235.64.0/20, country:CA]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DMARC_NA(0.00)[paz.bz]; TO_DN_NONE(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QHd8l5kdXz4Dk7 X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On 2023-05-11 8:46 PM, Paul Procacci wrote: > > > On Thu, May 11, 2023 at 11:35 PM Paul Procacci > wrote: > > > > On Thu, May 11, 2023 at 11:31 PM 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 > -- > __________________ > > :(){ :|:& };: > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267435 > > > As a follow up to my brief comment and given the bug report above (last > comment in particular), you don't happen to be running apache with > mod_php and ASLR are you? > > ~Paul > How about that . I do indeed . My symptoms described in that bugzilla are not quite the same tho . I can avoid the reload and switch to a restart . Not optimal , but it works . Then I can wait to follow if this bugzill ais acted on . Thanks for the reply .