Date: Mon, 28 Jun 2021 23:34:44 +0200 From: Michael Gmelin <freebsd@grem.de> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: 14-CURRENT: www/nextcloud: php occ/web access : Segmentation fault Message-ID: <E4291D3E-460E-4C95-9A10-30C5E4B59B4A@grem.de> In-Reply-To: <20210628223951.12230942@thor.intern.walstatt.dynvpn.de> References: <20210628223951.12230942@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 28. Jun 2021, at 22:41, O. Hartmann <ohartmann@walstatt.org> wrote: >=20 > =EF=BB=BF-----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 >=20 > Hello, >=20 > we ran into serious trouble here with an www/nextcloud installation on a r= ecent 14-CURRENT > (FreeBSD 14.0-CURRENT #23 main-n247612-e6dd0e2e8d4: Mon Jun 28 18:08:20 CE= ST 2021 amd64). > Ports tree is up to date and ports are built via traditional "make". Port w= ww/nextcloud, all > mod_ ports and even every php-* port (php74 is installed and default) has b= een recompiled > within the last two weeks via "portmaster -f". >=20 > The phenomenon occured back a couple of weeks, when access from the web vi= a cjromoum and/or > firefox reported out of the sudden "Secure Connection Failed". I checked t= he Apache > 2.4 server's certificate (self signed,never had been an issue so far), but= there seems no > issue to exist. > It got very strange when I tried to perfom an upgrade and/or check via >=20 > cd /usr/local/www/nextcloud > su -m -c "/usr/local/bin/php ./occ upgrade" >=20 > Whenever I access occ, I receive an @"Segmentation fault". > The I checked the server's error log and I found for each access of the ne= xtcloud instance an > entry like >=20 > [Tue Jun 01 06:04:40.667026 2021] [core:notice] [pid 81123:tid 34374492160= ] AH00052: child pid > 24598 exit signal Segmentation fault (11) >=20 > Well, I'm out of ideas, it seems nextcloud, php or apache ar all in combin= ation do have a > serious problem hard to come by with 14-CURRENT (another instance running o= n 12.2-RELENG > doesn't have any issues). >=20 > Can someone hint me to what to do track this nasty error? >=20 > Thanks in advance, >=20 Do you have a minimal setup to reproduce? Could you try building all ports a= gainst OpenSSL from ports? -m > oh >=20 > - --=20 > O. Hartmann >=20 > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs= . 4 BDSG). > -----BEGIN PGP SIGNATURE----- >=20 > iHUEARYKAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCYNozlwAKCRA4N1ZZPba5 > Rx2nAPwNf9014LCwIKdjN1lxdiESP0daa97tqvFsZiOM8OgpmAD+M6pmqlCVG6TE > HyuCprAwjwvP9zxov3BDaVmJRI3ZpAw=3D > =3Dz4d+ > -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E4291D3E-460E-4C95-9A10-30C5E4B59B4A>