Crashing Apache port

[The Doctor]

On Tue, Apr 02, 2019 at 05:14:29PM -0700, Jack L. wrote:
> Are you using php? Does php -v result in a crash?
>

Yes I use php and
No crash.

> On Tue, Apr 2, 2019 at 1:54 PM Jonathan Chen <jonc at chen.org.nz> wrote:
> >
> > On Wed, 3 Apr 2019 at 09:40, The Doctor <doctor at doctor.nl2k.ab.ca> wrote:
> > [...]
> > > Just recompiled and still crashing
> > >
> > > [Tue Apr 02 14:38:55.791536 2019] [core:notice] [pid 33235:tid 34380963840] AH00052: child pid 33933 exit signal Segmentation fault (11)
> > > [Tue Apr 02 14:38:55.791603 2019] [core:notice] [pid 33235:tid 34380963840] AH00052: child pid 33891 exit signal Segmentation fault (11)
> > > [Tue Apr 02 14:38:57.804771 2019] [core:notice] [pid 33235:tid 34380963840] AH00052: child pid 33972 exit signal Segmentation fault (11)
> > > [Tue Apr 02 14:38:57.804874 2019] [core:notice] [pid 33235:tid 34380963840] AH00052: child pid 33950 exit signal Segmentation fault (11)
> > > [Tue Apr 02 14:38:59.807646 2019] [core:notice] [pid 33235:tid 34380963840] AH00052: child pid 33971 exit signal Segmentation fault (11)
> > > [Tue Apr 02 14:39:01.823498 2019] [core:notice] [pid 33235:tid 34380963840] AH00052: child pid 33949 exit signal Segmentation fault (11)
> > > [Tue Apr 02 14:39:07.847344 2019] [core:notice] [pid 33235:tid 34380963840] AH00052: child pid 34034 exit signal Segmentation fault (11)
> > > [Tue Apr 02 14:39:08.854887 2019] [core:notice] [pid 33235:tid 34380963840] AH00052: child pid 33970 exit signal Segmentation fault (11)
> > > [Tue Apr 02 14:39:12.882163 2019] [core:notice] [pid 33235:tid 34380963840] AH00052: child pid 34097 exit signal Segmentation fault (11)
> > > [Tue Apr 02 14:39:12.882248 2019] [core:notice] [pid 33235:tid 34380963840] AH00052: child pid 34051 exit signal Segmentation fault (11)
> > >
> > > And I did do the above as requested.
> > > >
> >
> > My guess is that one of the mod*.so files in
> > /usr/local/libexec/apache24 is out of date. Check the timestamps on
> > the files to make sure that they look reasonably up to date. Aside
> > from that, make sure that all other LoadModule references in
> > non-standard locations are also inspected and have been recompiled for
> > FreeBSD 12.
> >
> > Aside from that, I wouldn't have a clue.
> >

That is what did the trick.  Flush the modules and the dependencies.

> > Cheers.
> > --
> > Jonathan Chen <jonc at chen.org.nz>
> > _______________________________________________
> > freebsd-ports at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!