Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pl0BL-000288-Oz for pgsql-general@arkaria.postgresql.org; Sat, 08 Apr 2023 04:28:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pl0BK-0007za-Bg for pgsql-general@arkaria.postgresql.org; Sat, 08 Apr 2023 04:28:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pl0BJ-0007zR-B4 for pgsql-general@lists.postgresql.org; Sat, 08 Apr 2023 04:28:06 +0000 Received: from resqmta-c1p-024062.sys.comcast.net ([2001:558:fd00:56::7]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pl0BG-0004hc-8s for pgsql-general@lists.postgresql.org; Sat, 08 Apr 2023 04:28:03 +0000 Received: from resomta-c1p-023267.sys.comcast.net ([96.102.18.232]) by resqmta-c1p-024062.sys.comcast.net with ESMTP id l01vpTcrRGdaml0BCpsJqu; Sat, 08 Apr 2023 04:27:58 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1680928078; bh=jFhbKE6zLJgunxnSyonlzAo9MS8ywThQMcMcJxr5xdM=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type:Xfinity-Spam-Result; b=Wbpt5ZXLPeYs9eLEFj4aUBnVtQKJmg74de7xQABey52r1SgqE+jTO0QQNWbupMx0C jL3MV98NON7yZq3ZEyXBB8C55TS0bsIEBHZGWtBiaxp1KPYnIXfg/nc0ETyFOgV4ha Z/KMbf1mDU4HEMTrWtGG9yhUAoqZ3nYnM38/DLSd3+BpvlLtAbmyP+ymgj08Lw3JCf L3Pk8XMN7b+zmQW/2fpOhXnCooTBxHNCGc3gIkV93dDrOf+xsFU915CoxaJZm4Ofal MQp62+HN+yFroI40Nd62pNB8K/xXl8dWIo5zJP73Zwkqx4Y147oBPSu9S071sOH8aY bE2rHwjrlWdmQ== Received: from R9N0YC2TC3.localdomain ([98.63.186.20]) by resomta-c1p-023267.sys.comcast.net with ESMTPA id l0B9prOWr5oOrl0BApWnbf; Sat, 08 Apr 2023 04:27:58 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedvhedrvdejiedgkedtucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedtudenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvvefufhffjgfkfgggtgfgsehtqhertddtreejnecuhfhrohhmpeflvghrrhihucfuihgvvhgvrhhsuceoghhsihgvvhgvrhhsudelsegtohhmtggrshhtrdhnvghtqeenucggtffrrghtthgvrhhnpedtieelheduledtiefgteelfeelfeeftefgudduueeuveevhffffffhudejteegffenucfkphepleekrdeifedrudekiedrvddtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheptfelpfdtjgevvdfvveefrdhlohgtrghlughomhgrihhnpdhinhgvthepleekrdeifedrudekiedrvddtpdhmrghilhhfrhhomheptgihsggvrhdrhhhunhhkohestghomhgtrghsthdrnhgvthdpnhgspghrtghpthhtohepfedprhgtphhtthhopehtghesvghvohhlvhhishdrohhrghdprhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlsehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrghdprhgtphhtthhopehsuhhpphhorhhtsehtvghlihhumhdrihho X-Xfinity-VMeta: sc=-100.00;st=legit Received: by R9N0YC2TC3.localdomain (Postfix, from userid 503) id 7B7591675F23; Fri, 7 Apr 2023 23:27:55 -0500 (CDT) From: Jerry Sievers To: Thorsten Glaser Cc: Telium Technical Support , pgsql-general@lists.postgresql.org Subject: Re: pg_ctlcluster is not stopping cluster References: <010001875dd4ebe6-ba96b71f-2461-45da-ab24-0abf56f56f4f-000000@email.amazonses.com> <1c1a4fe5-ffe3-5d8d-294c-e9c177decca@evolvis.org> Date: Fri, 07 Apr 2023 23:27:55 -0500 In-Reply-To: <1c1a4fe5-ffe3-5d8d-294c-e9c177decca@evolvis.org> (Thorsten Glaser's message of "Sat, 8 Apr 2023 00:49:30 +0200 (CEST)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thorsten Glaser writes: > On Fri, 7 Apr 2023, Telium Technical Support wrote: > >>Notice: extra pg_ctl/postgres options given, bypassing systemctl for stop > >>it might be 13. Coincidentally, there is a postmaster.pid file in a >>directory OTHER than the data directory: >> >>/var/lib/postgresql/15/main/postmaster.pid >> >>(and notice the 15). Is this a clue? > > Maybe the pidfile is written into the cluster version-based directory > instead of the data directory. Best figure out what exactly writes the > pidfile, whether systemd is used for starting (which would of course be Some distros in their wrapper foo, I believe including Debian use this setting to put a PID file under /var/run/postgresql IIRC but YMMV... external_pid_file (string) Specifies the name of an additional process-ID (PID) file that the server should create for use by server administration programs. This parameter can only be set at server start. > a prime suspect as it says it=E2=80=99s explicitly not used for stopping)= , etc. > > Maybe this is indeed a bug in whatever determines the pidfile path, > perhaps not; is it supposed to live within the data directory? > > bye, > //mirabilos