From nobody Thu Nov 14 21:07:20 2024 X-Original-To: freebsd-ports@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 4XqCQk0kbtz5d8pj for ; Thu, 14 Nov 2024 21:07:26 +0000 (UTC) (envelope-from andriy.gapon@uabsd.com) Received: from sender-op-o18.zoho.eu (sender-op-o18.zoho.eu [136.143.169.18]) (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 4XqCQj4Gh5z4DZ8 for ; Thu, 14 Nov 2024 21:07:25 +0000 (UTC) (envelope-from andriy.gapon@uabsd.com) Authentication-Results: mx1.freebsd.org; none ARC-Seal: i=1; a=rsa-sha256; t=1731618441; cv=none; d=zohomail.eu; s=zohoarc; b=ZSWAaLgXYFyvyLd5vcrkkX2yzBKaCT16y/vyc4l1jP/bpieewCZ6bZh2HdsxHYLhvMnG9o9rvt4KzX04BSydQZq/D4BqJ5Hzo9/hYY6nWXLELPXJmx7QTeF7HBQv1376eTtslXWuwQn6MxHMGUSW25mJ2sHywDDNyCUg5yBeUBk= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu; s=zohoarc; t=1731618441; h=Content-Type:Content-Transfer-Encoding:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To:Cc; bh=5vlyY4OwerS20n1MTZ0Yr+lY0SkK72v8gqfrH9srKEo=; b=j2IfC/NqKSJQiPOGOE+YGgxv0obTdIM+9H+S8qA5Ohm9Y+bKWbDSjxXJ0bPlNsU8Q1UKuEiePECee8WglJSeYOt6jFRJnD914SR4+8iVXQlS3U28suHQ5aFTdgw4+ItdSA/4OuWEICw8+tMLDflVn+t2ZDqpteJxVeCUXNAoA6w= ARC-Authentication-Results: i=1; mx.zohomail.eu; spf=pass smtp.mailfrom=andriy.gapon@uabsd.com; dmarc=pass header.from= Received: by mx.zoho.eu with SMTPS id 1731618440841998.6735637193065; Thu, 14 Nov 2024 22:07:20 +0100 (CET) Message-ID: <9b8b89b6-ca2a-481f-9d76-7b6c1af89ff3@FreeBSD.org> Date: Thu, 14 Nov 2024 23:07:20 +0200 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Anybody seeing NextCloud crash? To: Ronald Klop , "Kevin P. Neal" , freebsd-ports@freebsd.org References: Content-Language: en-US From: Andriy Gapon In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ZohoMailClient: External X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:41913, ipnet:136.143.168.0/23, country:CH] X-Rspamd-Queue-Id: 4XqCQj4Gh5z4DZ8 X-Spamd-Bar: ---- On 14/11/2024 14:29, Ronald Klop wrote: > 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 > > > 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. > > I'm not sure if there are other reasons for SIGILL. I recently learned about another reason and it's an instruction like ud2 on x86 that can be inserted by a compiler for one reason or another (e.g., because of an assert). But not in this case, I think. Kevin correctly identified a (super)set of packages responsible for the problem. The issue is known and it should be fixed in ports already. See: https://cgit.freebsd.org/ports/commit/?id=1876b07e4fcf269a1c57ac401ab57e4337bcf465 https://github.com/aous72/OpenJPH/releases/tag/0.18.0 > It helps if you could share what FreeBSD version your are running and on what > architecture. > > The output of 'uname -a' gives this. > > /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="GenuineIntel"  Id=0x406e3  Family=0x6  Model=0x4e  Stepping=3 > > Features=0x1783fbff > > Features2=0xdeda2203 >   AMD Features=0x28100800 >   AMD Features2=0x121 >   Structured Extended > Features=0x842421 >   Structured Extended Features3=0x10000400 >   TSC: P-state invariant > > 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. > > 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. > >> >> 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? -- Andriy Gapon