Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wU12Y-000tbt-1J for pgsql-bugs@arkaria.postgresql.org; Mon, 01 Jun 2026 11:42:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wU12X-009w2Y-0s for pgsql-bugs@arkaria.postgresql.org; Mon, 01 Jun 2026 11:42:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wThMd-007iTP-1T for pgsql-bugs@lists.postgresql.org; Sun, 31 May 2026 14:42:07 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wThMb-00000000QmP-0ahR for pgsql-bugs@lists.postgresql.org; Sun, 31 May 2026 14:42:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=FIEpSCxavA4Chkxc0qx11yNrc1uL/vaqIrdjTEFWNeY=; b=uodqsabb5kJiCEtrrMa96Mwz6R XyBurhBaAgAkFNs/TVmRcyHadDeIPSKpIdnMHN9vOUjlm1F/1746jKzdCQL4H9HsJLz4kvPEpS7yO HlsNBV1rEhXONfwRHTDLbkYGLcVkkLM4azLvo1jGc0hcINwQPacchgYd1DhvqdNPuUZ9pQ+B3Ir6S T8dRnxXtxSS/TLFIWB97u79v9rLKYpvJDUvp0SpNnqsfUTCAJS6Ubi0/C7eHXTFIQpsGejVUkt2sr metwktFuFkFca2tY5fHsDzBC2KesOpwz5fAKKlxGosx8u+JFoVdciV2I4Xk2VhjboGPk8G0wwHDjc P8DGeE4g==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wThMZ-001NGn-1h for pgsql-bugs@lists.postgresql.org; Sun, 31 May 2026 14:42:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wThMZ-00358E-07 for pgsql-bugs@lists.postgresql.org; Sun, 31 May 2026 14:42:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19502: unix_socket_group doesn't work anymore To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: pierre.juhen@orange.fr Reply-To: pierre.juhen@orange.fr, pgsql-bugs@lists.postgresql.org Date: Sun, 31 May 2026 14:41:15 +0000 Message-ID: <19502-7f29e169bb2eda2c@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19502 Logged by: Pierre Juhen Email address: pierre.juhen@orange.fr PostgreSQL version: 16.3 Operating system: Linux Description: =20 Hi, I developped an application on Alma Linux 9 and PostgreSQL 13. I want to maintain it up to date, and try to "port" it to Alma Linux 10 and PostgreSQL 16.13 Previously the appplication run under the identity of a plain user. The Unix socket (/var/run/postgresql/.s.PGSQL.5432) was owned by postgres and the group was that plain user one. Now, postgreSQL refuses to launch with the following error : 2026-05-30 23:59:27.178 CEST [5163] LOG: n'a pas pu initialiser le groupe du fichier =C2=AB /var/run/postgresql/.s.PGSQL.5432 =C2=BB : Op=C3=A9ration= non permise 2026-05-30 23:59:27.178 CEST [5163] ATTENTION: n'a pas pu cr=C3=A9er la so= cket de domaine Unix dans le r=C3=A9pertoire =C2=AB /var/run/postgresql =C2=BB 2026-05-30 23:59:27.180 CEST [5163] LOG: n'a pas pu initialiser le groupe du fichier =C2=AB /tmp/.s.PGSQL.5432 =C2=BB : Op=C3=A9ration non permise 2026-05-30 23:59:27.180 CEST [5163] ATTENTION: n'a pas pu cr=C3=A9er la so= cket de domaine Unix dans le r=C3=A9pertoire =C2=AB /tmp =C2=BB 2026-05-30 23:59:27.180 CEST [5163] FATAL: n'a pas pu cr=C3=A9er les socke= ts de domaine Unix Translated by google in english : 2026-05-30 23:59:27.178 CEST [5163] LOG: Could not initialize the group for the file '/var/run/postgresql/.s.PGSQL.5432': Operation not permitted 2026-05-30 23:59:27.178 CEST [5163] WARNING: Could not create the Unix domain socket in the directory '/var/run/postgresql' 2026-05-30 23:59:27.180 CEST [5163] LOG: Could not initialize the group for the file '/tmp/.s.PGSQL.5432': Operation not permitted 2026-05-30 23:59:27.180 CEST [5163] WARNING: Could not create the socket Unix domain in the "/tmp" directory 2026-05-30 23:59:27.180 CEST [5163] FATAL: Could not create Unix domain sockets If I comment unix_socket_group in postgresql.conf, the system starts without any problem. The postgres heading process has got the right chown capability (cap_chown) I don't undestand what append. The same problem occurs with my development machine (Fedora 44 and and PostgreSQL 18.3). Recent changes in the kernel ? Any help would be welcome. Thanks, Pierre