public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Christoph Berg <[email protected]>
To: [email protected]
To: Brandon Snider <[email protected]>
To: [email protected]
Subject: Re: pgbouncer packaging issue
Date: Wed, 10 Jan 2018 09:56:59 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CABSshC2iCU9+DeT8vvBXvYzJmMmjYM3CVshccRwDv7Pf-vMYrw@mail.gmail.com>
<[email protected]>
<[email protected]>
On 1/9/18 16:11, Christoph Berg wrote:
> Am 9. Januar 2018 19:59:04 MEZ schrieb Peter Eisentraut <[email protected]>:
>> On 1/9/18 13:47, Brandon Snider wrote:
>>> You're installing /usr/lib/tmpfiles.d/pgbouncer.conf to create the
>>> /var/run/pgbouncer dir, but the permissions on that dir are too
>>> restrictive -- 700 -- for any file to be read by any user except
>>> pgbouncer and root. In my situation, for whatever reason my PHP
>>> implementation can't read unix sockets in /tmp,
>>
>> That might need further explanation.
>
> That's likely systemd at work. By default, each process gets its own /tmp bind-mounted.
Right. After further off-list discussion, the actual bug here is that
pgbouncer should puts its socket into /var/run/postgresql, which is the
standard location on that platform. But that doesn't work because
pgbouncer runs under a separate user and doesn't have permission there.
This has been previously reported on this list.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: pgbouncer packaging issue
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox