Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZMcIg-0007fP-Nc for pgsql-admin@arkaria.postgresql.org; Tue, 04 Aug 2015 13:30:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZMcIg-0004E9-3x for pgsql-admin@arkaria.postgresql.org; Tue, 04 Aug 2015 13:30:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZMcH3-0002IV-OD for pgsql-admin@postgresql.org; Tue, 04 Aug 2015 13:28:57 +0000 Received: from mbob.nabble.com ([162.253.133.15]) by magus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1ZMcGw-0002x1-DK for pgsql-admin@postgresql.org; Tue, 04 Aug 2015 13:28:56 +0000 Received: from msam.nabble.com (unknown [162.253.133.85]) by mbob.nabble.com (Postfix) with ESMTP id 8C134128E7D8 for ; Tue, 4 Aug 2015 06:29:24 -0700 (PDT) Date: Tue, 4 Aug 2015 06:28:47 -0700 (MST) From: jkilborn To: pgsql-admin@postgresql.org Message-ID: <1438694927835-5860802.post@n5.nabble.com> In-Reply-To: References: <1438692397419-5860795.post@n5.nabble.com> Subject: Re: postgres not deleting trigger file MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -1.2 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Thanks for the reply.=20 I think the problem is permissions. The fact that the pgpool runs as root user, its likely that postgres can=E2=80=99t remove the created trigger fil= e. 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=E2=80=99m having to do this, as I haven=E2= =80=99t 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-del= eting-trigger-file-tp5860795p5860802.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com. --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin