From nobody Mon Nov 04 04:39:26 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 4Xhf0y4fngz5c7kX for ; Mon, 04 Nov 2024 04:40:50 +0000 (UTC) (envelope-from kpn@neutralgood.org) Received: from gunsight1.NeutralGood.ORG (gunsight1.neutralgood.org [206.196.19.100]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "gunsight1.neutralgood.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xhf0x5SS6z4cwG for ; Mon, 4 Nov 2024 04:40:49 +0000 (UTC) (envelope-from kpn@neutralgood.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of kpn@neutralgood.org designates 206.196.19.100 as permitted sender) smtp.mailfrom=kpn@neutralgood.org; dmarc=none Received: from gunsight1.neutralgood.org (localhost [127.0.0.1]) by gunsight1.NeutralGood.ORG (8.18.1/8.18.1) with ESMTPS id 4A44dQe7002563 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Sun, 3 Nov 2024 23:39:26 -0500 (EST) (envelope-from kpn@gunsight1.neutralgood.org) Received: (from kpn@localhost) by gunsight1.neutralgood.org (8.18.1/8.18.1/Submit) id 4A44dQYW002562 for freebsd-ports@freebsd.org; Sun, 3 Nov 2024 23:39:26 -0500 (EST) (envelope-from kpn) Date: Sun, 3 Nov 2024 23:39:26 -0500 From: "Kevin P. Neal" To: freebsd-ports@freebsd.org Subject: Anybody seeing NextCloud crash? Message-ID: 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spamd-Result: default: False [-2.30 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:13649, ipnet:206.196.0.0/19, country:US]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[neutralgood.org]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4Xhf0x5SS6z4cwG X-Spamd-Bar: -- 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 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? -- Kevin P. Neal http://www.pobox.com/~kpn/ "I like being on The Daily Show." - Kermit the Frog, Feb 13 2001