Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 May 2023 23:35:26 -0400
From:      Paul Procacci <pprocacci@gmail.com>
To:        Jim Pazarena <fquest@paz.bz>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: apache24 reload dies with SIGSEGV
Message-ID:  <CAFbbPui9BgVxpcu2YcFMVu_kSR38D6EPyR6iOxk9FRhZ3dvn0w@mail.gmail.com>
In-Reply-To: <8264bee7-f13f-a1a1-552a-09fb34973b26@paz.bz>
References:  <8264bee7-f13f-a1a1-552a-09fb34973b26@paz.bz>

next in thread | previous in thread | raw e-mail | index | archive | help
--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 <fquest@paz.bz> 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

<div dir=3D"ltr"><div><div dir=3D"ltr"><br></div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 11, 2023 at 11:31=E2=
=80=AFPM Jim Pazarena &lt;<a href=3D"mailto:fquest@paz.bz">fquest@paz.bz</a=
>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I j=
ust loaded two servers with a fresh 13.2 install . Along with a fresh <br>
install of 2.4.57 Apache .<br>
<br>
both have public IPs<br>
one is https , while the other is not .<br>
<br>
an &quot;./apache24 start&quot; works as expected . It passes the sanity ch=
eck , <br>
announces Syntax OK , and runs .<br>
<br>
However , if I issue an &quot;./apache24 reload&quot;<br>
it still announces Syntax OK , followed with:<br>
Performing a graceful restart<br>
<br>
but it does not start .<br>
running &quot;dmesg&quot; , I see:<br>
pid xxxx (httpd), jid 0, uid 0: existed on signal 11<br>
<br>
If I run an &quot;.apache24 start&quot;<br>
it fires up as expected and runs as expected .<br>
<br>
What is a reload doing extra that a start does not do , that could be <br>
causing a SIGSEGV ?<br>
oh yes, a restart works as expected<br>
a reload dies .<br>
<br>
Suggestions would be most appreciated .<br>
<br>
</blockquote></div><br clear=3D"all"></div><div>You need to generate a core=
 and run gdb against it getting a backtrace. -- This ultimately would provi=
de you very specifically where it&#39;s getting foul&#39;d up.<br></div><di=
v><br></div><div>~Paul<br></div><div><span class=3D"gmail_signature_prefix"=
>-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">_________________=
_<br><br>:(){ :|:&amp; };:</div></div></div>

--0000000000006b1b7a05fb76cc58--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFbbPui9BgVxpcu2YcFMVu_kSR38D6EPyR6iOxk9FRhZ3dvn0w>