Content-Type: multipart/alternative;
 boundary="------------qZGaSoSUtO4ecD7aXw0pHRKB"
Message-ID: <cf469e46-b3e9-48eb-8fe4-810fd2ed4397@orange.fr>
Date: Sun, 31 May 2026 18:47:03 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: BUG #19502: unix_socket_group doesn't work anymore
To: pgsql-bugs@lists.postgresql.org
References: <19502-7f29e169bb2eda2c@postgresql.org>
Content-Language: fr, en-GB, en-US
From: Pierre Juhen <pierre.juhen@orange.fr>
In-Reply-To: <19502-7f29e169bb2eda2c@postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/cf469e46-b3e9-48eb-8fe4-810fd2ed4397%40orange.fr>
Precedence: bulk

This is a multi-part message in MIME format.
--------------qZGaSoSUtO4ecD7aXw0pHRKB
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Please forget this stupid question.

I forgot a usermod to allow postgres to be in the palin user group

Shame on me.

Pierre

Le 31/05/2026 à 16:41, PG Bug reporting form a écrit :
> 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:
>
> 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 « /var/run/postgresql/.s.PGSQL.5432 » : Opération non permise
> 2026-05-30 23:59:27.178 CEST [5163] ATTENTION:  n'a pas pu créer la socket
> de domaine Unix dans le répertoire « /var/run/postgresql »
> 2026-05-30 23:59:27.180 CEST [5163] LOG:  n'a pas pu initialiser le groupe
> du fichier « /tmp/.s.PGSQL.5432 » : Opération non permise
> 2026-05-30 23:59:27.180 CEST [5163] ATTENTION:  n'a pas pu créer la socket
> de domaine Unix dans le répertoire « /tmp »
> 2026-05-30 23:59:27.180 CEST [5163] FATAL:  n'a pas pu créer les sockets 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
>
>
--------------qZGaSoSUtO4ecD7aXw0pHRKB
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><font face="Carlito">Please forget this stupid question.</font></p>
    <p><font face="Carlito">I forgot a usermod to allow postgres to be
        in the palin user group</font></p>
    <p><font face="Carlito">Shame on me.</font></p>
    <p><font face="Carlito">Pierre</font></p>
    <div class="moz-cite-prefix">Le 31/05/2026 à 16:41, PG Bug reporting
      form a écrit :<br>
    </div>
    <blockquote type="cite"
      cite="mid:19502-7f29e169bb2eda2c@postgresql.org">
      <pre wrap="" class="moz-quote-pre">The following bug has been logged on the website:

Bug reference:      19502
Logged by:          Pierre Juhen
Email address:      <a class="moz-txt-link-abbreviated" href="mailto:pierre.juhen@orange.fr">pierre.juhen@orange.fr</a>
PostgreSQL version: 16.3
Operating system:   Linux
Description:        

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 « /var/run/postgresql/.s.PGSQL.5432 » : Opération non permise
2026-05-30 23:59:27.178 CEST [5163] ATTENTION:  n'a pas pu créer la socket
de domaine Unix dans le répertoire « /var/run/postgresql »
2026-05-30 23:59:27.180 CEST [5163] LOG:  n'a pas pu initialiser le groupe
du fichier « /tmp/.s.PGSQL.5432 » : Opération non permise
2026-05-30 23:59:27.180 CEST [5163] ATTENTION:  n'a pas pu créer la socket
de domaine Unix dans le répertoire « /tmp »
2026-05-30 23:59:27.180 CEST [5163] FATAL:  n'a pas pu créer les sockets 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


</pre>
    </blockquote>
  </body>
</html>

--------------qZGaSoSUtO4ecD7aXw0pHRKB--