FS#31436 - [php-fpm] PrivateTmp=true in systemd unit file breaks phpPgAdmin

Attached to Project: Arch Linux
Opened by Paul Gideon Dann (giddie) - Thursday, 06 September 2012, 09:54 GMT
Last edited by Pierre Schmitz (Pierre) - Tuesday, 19 March 2013, 18:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The default unit file for php-fpm has PrivateTmp=true, which means that php-fpm is unable to see the Postgresql socket at /tmp/.s.PGSQL.5432, and therefore phpPgAdmin can't see Postgresql. Hopefully, Postgres will move this socket to somewhere under /var/tmp at some point, but in the meantime I suggest removing PrivateTmp=true from the unit file.

Additional info:
* php-fpm 5.4.6-1
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Tuesday, 19 March 2013, 18:45 GMT
Reason for closing:  Fixed
Comment by Dan McGee (toofishes) - Thursday, 06 September 2012, 18:01 GMT
We could probably build with the socket in a different place. I need to poke at what other distros do in regard to this; I'm hoping Fedora has already solved this problem. It does seem like something that would be better located in /run.
Comment by Dave Reisner (falconindy) - Thursday, 06 September 2012, 18:13 GMT
http://pkgs.fedoraproject.org/cgit/postgresql.git/tree/postgresql-var-run-socket.patch
Comment by Pierre Schmitz (Pierre) - Monday, 18 March 2013, 09:31 GMT
I would consider placing a socket into /tmp a bug, so I am not going to alter the php unit file.
Comment by Paul Gideon Dann (giddie) - Monday, 18 March 2013, 10:02 GMT
This was fixed quite a while back now. The socket is now placed in /run/php-fpm/php-fpm.sock, and Postgresql's socket is at /run/postgresql/.s.PGSQL.5432.

Loading...