Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qteFs-00DN5t-Ll for pgsql-admin@arkaria.postgresql.org; Fri, 20 Oct 2023 01:24:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qteFq-00AOPV-Ij for pgsql-admin@arkaria.postgresql.org; Fri, 20 Oct 2023 01:24:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qteFp-00AOOH-Mo for pgsql-admin@lists.postgresql.org; Fri, 20 Oct 2023 01:24:46 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qteFl-001dZd-Kb for pgsql-admin@lists.postgresql.org; Fri, 20 Oct 2023 01:24:45 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 362B15C093A; Thu, 19 Oct 2023 21:24:40 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Thu, 19 Oct 2023 21:24:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= quadratum-braccas.com; h=cc:content-type:content-type:date:date :from:from:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to; s=fm2; t=1697765080; x=1697851480; bh=7S E+3yziS19ugSc1VytNbO4Fy0FBO3NQsv4mD5/r7VY=; b=yf/X7EzJbYi1WXLcMl Nj1Z/VLxNp54Uu7Y4ISpJ9S19cFuevhilKDNxw4pYvw3FdVBK0VQFF2bnWYR17Ob 0AisGWZjxLKYfq4vBnv39zw/HUuET5elDNVGfpjfMziobTDAWwkyIpqv5s1nVQnI Xgi50ttGdGalFK1rAR4tLfsiiRU2ykBiP18Vc0KGHSyfQD2cI35WvuI+tE78+tOK lRjtBPc62Kwx7KCD9yq8xn6lUPBGnxhIN3DEzCzg3nFLonNsTsdH1tPDVELXB2b6 z3Pef5F0RUNZbskl+7IdxXiIHW/bXoRm8uYuoaxhKKMJ0EKfeRpjAncFiIFDSllg 3Ddg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1697765080; x=1697851480; bh=7SE+3yziS19ugSc1VytNbO4Fy0FBO3NQsv4 mD5/r7VY=; b=muwNE6cI+PGdYAGokILVLjkcQZgrkQUMhcaG2KmkxCcJVmSs6Fg z4tkIi/SxsatNVI+ohxTEBNRcFgsUdTcjc2I/+0RsPIe4JyrjTRwnGmPVRZEUJMN vpczTzR7n18GFFYp9INQRZusOLLKu70iHSsrGLf4ly6N5hQ6EgBRbMKUEiL/nsAY bFMEBoERS31sdTIBMBjeH3/AqXfsWnu/M1ygm6SygEQ82YTjRW3tYVTofvEGhVj4 rs6ew4lgQs4U5KaVf3HILec0D2ILXEU6ECFZnaPODpfnubn+PXxFNVf7Ybk4D9NS VeyyBFTSlMAxw/5foZhyfjtXxg78IGwWiqg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrjeejgdeghecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptgfkffggfgfvhffusegrtderredtvd ejnecuhfhrohhmpefusghosgcuoehssghosgesqhhurggurhgrthhumhdqsghrrggttggr shdrtghomheqnecuggftrfgrthhtvghrnhepkefhvdekfeeliefgteehuedttdelueetue eihfevvddvteettdekkeehgfeigfeknecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepshgsohgssehquhgrughrrghtuhhmqdgsrhgrtggtrghsrd gtohhm X-ME-Proxy: Feedback-ID: i374947ac:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 19 Oct 2023 21:24:39 -0400 (EDT) Content-Type: multipart/alternative; boundary="------------ByjU74qhqoFql2FO9WuXz0wX" Message-ID: Date: Thu, 19 Oct 2023 19:24:37 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Pgsql-admin Content-Language: en-US From: Sbob Subject: using pg_ctl over ssh hangs List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------ByjU74qhqoFql2FO9WuXz0wX Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit All I am wanting to run pg_ctl as a command over ssh, however when I pass start it hangs until I do a Ctl-C This works fine: $ node3=172.16.171.132 $ ssh -T postgres@${node3} "/usr/pgsql-14/bin/pg_ctl -D /var/lib/pgsql/14/data stop" waiting for server to shut down.... done server stopped $ I am immediately returned to a command prompt However , this does not return me to a command prompt until I do a Ctl-C: $ node3=172.16.171.132 $ ssh -T postgres@${node3} "/usr/pgsql-14/bin/pg_ctl -D /var/lib/pgsql/14/data start" waiting for server to start....2023-10-19 19:23:42.947 MDT [2053] LOG:  redirecting log output to logging collector process 2023-10-19 19:23:42.947 MDT [2053] HINT:  Future log output will appear in directory "log". done server started ^C $ Thanks in advance --------------ByjU74qhqoFql2FO9WuXz0wX Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

All


I am wanting to run pg_ctl as a command over ssh, however when I pass start it hangs until I do a Ctl-C


This works fine:

$ node3=172.16.171.132
$ ssh -T postgres@${node3} "/usr/pgsql-14/bin/pg_ctl -D /var/lib/pgsql/14/data stop"
waiting for server to shut down.... done
server stopped
$

I am immediately returned to a command prompt

However , this does not return me to a command prompt until I do a Ctl-C:


$ node3=172.16.171.132


$ ssh -T postgres@${node3} "/usr/pgsql-14/bin/pg_ctl -D /var/lib/pgsql/14/data start"
waiting for server to start....2023-10-19 19:23:42.947 MDT [2053] LOG:  redirecting log output to logging collector process
2023-10-19 19:23:42.947 MDT [2053] HINT:  Future log output will appear in directory "log".
done
server started

^C
$



Thanks in advance


--------------ByjU74qhqoFql2FO9WuXz0wX--