Well, in the past I've always had pgpool-II running as the postgres user, not root. That's probably why I didn't see any issues at the time. Good luck with this.
On Tue, Aug 4, 2015 at 8:28 AM, jkilborn <jim.kilborn@xxxxxxxx> wrote:
Thanks for the reply.
I think the problem is permissions. The fact that the pgpool runs as root
user, its likely that postgres can’t remove the created trigger file.
I ended up doing two things in my pgp failover_stream.sh script, which
creates the file:
/bin/ssh -T $new_master /bin/touch $trigger_file
/bin/ssh -T $new_master chown postgres $trigger_file
Seems with changing the ownership of the trigger file, postgres can now
delete the file. Not sure why I’m having to do this, as I haven’t seen
anyone else encounter this issue.
Anyway, with these changes, it appears to be working correctly.
Thanks for the response.
-Jim
--
View this message in context: http://postgresql.nabble.com/postgres-not-deleting-trigger-file-tp5860795p5860802.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
