Date: Fri, 15 Nov 2024 11:14:26 +0100 From: Moin Rahman <bofh@freebsd.org> To: FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: Anybody seeing NextCloud crash? Message-ID: <734A07EA-44EB-4009-A7E9-082944CC1ABD@freebsd.org> In-Reply-To: <c42e055c-05fe-487f-9818-5951d54d3e1c@FreeBSD.org> References: <ZyhP_kZiW4i-DZcX@neutralgood.org> <c42e055c-05fe-487f-9818-5951d54d3e1c@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_8C3795D1-30C3-4732-A58B-109CC1791B8E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Nov 14, 2024, at 13:29, Ronald Klop <ronald@FreeBSD.org> wrote: >=20 > Op 04-11-2024 om 05:39 schreef Kevin P. Neal: >> I'm seeing a problem with NextCloud's php-fpm instance crashes when = trying >> to handle a request over the web interface. My web server is Apache = 2.4 >> if it matters. The MacOS desktop sync client works just fine, and so = does >> the app from iOS 16 (I have an iPhone 8 that I'm upgrading soon). >> Apache responds with a "Service Unavailable" error page. >> In my /var/log/php-fpm.log I find this: >> [03-Nov-2024 11:06:45] WARNING: [pool www] child 68236 exited on = signal 4 (SIGILL) after 5.975134 seconds from start >=20 >=20 > SIGILL means that an instruction was executed that was not understood = by the CPU. > This can be something like the software using SSE2 instructions and = your CPU does not support that. >=20 > I'm not sure if there are other reasons for SIGILL. >=20 > It helps if you could share what FreeBSD version your are running and = on what architecture. >=20 > The output of 'uname -a' gives this. >=20 > /var/run/dmesg.boot gives information about your CPU. This helps in = determining the supported instructions. > Mine gives this: > CPU: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (2400.14-MHz K8-class = CPU) > Origin=3D"GenuineIntel" Id=3D0x406e3 Family=3D0x6 Model=3D0x4e = Stepping=3D3 > = Features=3D0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE= ,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT> > = Features2=3D0xdeda2203<SSE3,PCLMULQDQ,SSSE3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,= POPCNT,AESNI,XSAVE,OSXSAVE,AVX,RDRAND,HV> > AMD Features=3D0x28100800<SYSCALL,NX,RDTSCP,LM> > AMD Features2=3D0x121<LAHF,ABM,Prefetch> > Structured Extended = Features=3D0x842421<FSGSBASE,AVX2,INVPCID,NFPUSG,RDSEED,CLFLUSHOPT> > Structured Extended Features3=3D0x10000400<MD_CLEAR,L1DFL> > TSC: P-state invariant >=20 > If php-fpm gives a core dump it is also possible to analyze on what = instruction it is failing. I don't know the command on how to do that by = the top of my head. Maybe somebody else can help. >=20 > If you can find out what package update resulted in the crash then you = could ask the package maintainer to compile it for older CPUs by = default. >=20 > Regards, > Ronald. >=20 >=20 >=20 >=20 >> Every time I tried to reload a page on the web site I get a failure = like >> that one. The php-fpm processes are dying. >> I use the checkrestart package after every pkg upgrade and I restart >> anything that gets mentioned. This handy utility isn't foolproof, but >> I've had good luck with it. >> Reinstalling all my packages with pkg upgrade -f changed nothing. >> I rolled back my ZFS dataset to October 30's, rebooted (needed, don't = know >> why), and I have it back up and running now. >> I did "service php_fpm restart" after the bad update, but I forgot to = check >> that everything was still working. That's why I had to rollback so = far -- >> I have SMS messages on my phone that imply it was working on that = date. >> The problem was introduced with one of these updates: >> The following 11 package(s) will be affected (of 0 checked): >> New packages to be INSTALLED: >> openh264: 2.3.0,2 >> openjph: 0.17.0 >> Installed packages to be UPGRADED: >> ffmpeg: 6.1.2_4,1 -> 6.1.2_5,1 >> glib: 2.80.5,2 -> 2.80.5_1,2 >> libheif: 1.18.2_1 -> 1.19.1 >> libnghttp2: 1.63.0 -> 1.64.0 >> libssh2: 1.11.0_1,3 -> 1.11.1,3 >> libvpx: 1.14.1 -> 1.15.0 >> pciids: 20240920 -> 20241024 >> py311-redis: 5.1.1 -> 5.2.0 >> svt-av1: 2.2.0 -> 2.3.0 >> Number of packages to be installed: 2 >> Number of packages to be upgraded: 9 >> I do have my own poudriere setup, but I don't think I have any custom >> settings at this point. I can doublecheck if anyone is curious, = though. >> Anyone else seen this? Or should I file a bug report? >=20 >=20 Just for everyone else in the list, I have gone through some discussion with the original author of the mail and it seems to have some sort of regression with graphics/pecl-imagick. Whenever this php module is loaded php-fpm crashes on at least php82 and maybe later. This module actually may not support php82 and later. Or maybe there was some sort of new regression with some other commits down the line of ImageMagic. Kind regards, Moin --Apple-Mail=_8C3795D1-30C3-4732-A58B-109CC1791B8E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEETfdREoUGjQZKBS+fvbm1phfAvJEFAmc3HwJfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRE Rjc1MTEyODUwNjhEMDY0QTA1MkY5RkJEQjlCNUE2MTdDMEJDOTEACgkQvbm1phfA vJG04Q//dy/KGsMOTeCxpJHGmfb3BeBFts4nIzueJ9g3ujyqOljetYE+VJAcfjyi TDB7pvzjR1/eB8naUrtFNZv5P9Y9M8bhPKtigoIx61EzsPo58XnbXx6Wi59IDKea dsIjRR++reO3bCZ9/hjcJOTq1yXIEKaXy3DeF32wYIkVqGV5jXKuZxLSr0O7jNLd fAzi4rezkmYrpKhMWX+Zhne2bchafGW9WOWpYcimtGfIFn1Z7FqYxYeL4HJm9Qfs EiPsn8VoydO/MLfBkpoJImYOysVVqcFPNWxdQ/QwstfjwYOtTkuHN5Eo9tZfokeb 1s7WZU/0jxoLH4bQR6CkJEaJUEFJeHN2gVPNYX1XhehyPADRGS1SVujEo9u+4dxh CFjbM6M54GtIvDg4C2PhftEQuozVYCyrEgPsOJW5U3VMXb78k3h20EeDksE1AoRA mTf11CM7LA3MzxBYixF219dLe1M28iPWX4JgmD8HdVqOPssGxyZcvPJMDtFn6yG4 LLFpFLRnhN0Ekm2ZJ7qx+R28Bwj5NnBe/IJDFVVEmORcuPhE6YbmaX2unaKMyCoN HC4F4FwaJ7hiIJJyKv3cwu7rh28OEwjyowA7f1FXv66yXPJJteuRrTsIWEGVrZR8 6GlQNoMdrW++LjDHNgwN2tFPh45XQqsw/Pp7xodNjG/O8FBY2A8= =azK8 -----END PGP SIGNATURE----- --Apple-Mail=_8C3795D1-30C3-4732-A58B-109CC1791B8E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?734A07EA-44EB-4009-A7E9-082944CC1ABD>