Thread: services and pg_ctl
Hello,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
______________________________________
It seems that in some (recent? all?) versions of the PGDG Redhat/CentOS RPMs pg_ctl and service (init.d) don't play well together.
As an example:
It seems like this is because of pg_ctl and the init.d script using different lockfiles / pidfiles. This can be fixed by doing the following:-bash-4.1$ iduid=26(postgres) gid=26(postgres) groups=26(postgres),500(efm)-bash-4.1$-bash-4.1$ psqlpsql: could not connect to server: No such file or directoryIs the server running locally and acceptingconnections on Unix domain socket "/tmp/.s.PGSQL.5432"?-bash-4.1$-bash-4.1$ pg_ctl startserver starting-bash-4.1$ exitlogout[root@centos6-soe /]#[root@centos6-soe /]# service postgresql-9.4 statuspostgresql-9.4 is stopped
- Making a directory for locks and pid files (in /var/lock/subsys and /var/run) and setting it to be owned by postgres
- Setting unix_socket_directories in postgresql.conf to use the lock directory by default.
- Setting external_pid_file in postgresql.conf to use the /var/run directory by default
- Setting the init.d script to write the lockfile in the same way pg_ctl does
Is this something that could change in the future (or is there a reason this is a bad idea)? I'm happy to provide diffs to get to a working state if that helps.
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
______________________________________
The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.