public inbox for [email protected]
help / color / mirror / Atom feedFrom: James Sewell <[email protected]>
To: [email protected]
Subject: services and pg_ctl
Date: Tue, 28 Jul 2015 18:36:44 +1000
Message-ID: <CANkGpBvJrLfiepjh2dEMqkavfSzyOA+i_ZBuxRKEyo_im4YLmg@mail.gmail.com> (raw)
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-pkg-yum>
Hello,
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:
-bash-4.1$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres),500(efm)
-bash-4.1$
-bash-4.1$ psql
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
-bash-4.1$
-bash-4.1$ pg_ctl start
server starting
-bash-4.1$ exit
logout
[root@centos6-soe /]#
[root@centos6-soe /]# service postgresql-9.4 status
postgresql-9.4 is stopped
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:
1. Making a directory for locks and pid files (in /var/lock/subsys and
/var/run) and setting it to be owned by postgres
2. Setting unix_socket_directories in postgresql.conf to use the lock
directory by default.
3. Setting external_pid_file in postgresql.conf to use the /var/run
directory by default
4. 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
______________________________________
Level 2, 50 Queen St, Melbourne VIC 3000
*P *(+61) 3 8370 8000 *W* www.lisasoft.com *F *(+61) 3 8370 8099
--
------------------------------
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.
view thread (2+ 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]
Subject: Re: services and pg_ctl
In-Reply-To: <CANkGpBvJrLfiepjh2dEMqkavfSzyOA+i_ZBuxRKEyo_im4YLmg@mail.gmail.com>
* 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