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.96) (envelope-from ) id 1wL58F-001Vy2-0J for pgsql-general@arkaria.postgresql.org; Thu, 07 May 2026 20:15:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wL58C-005uJq-14 for pgsql-general@arkaria.postgresql.org; Thu, 07 May 2026 20:15:36 +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.96) (envelope-from ) id 1wL58B-005uJi-3C for pgsql-general@lists.postgresql.org; Thu, 07 May 2026 20:15:35 +0000 Received: from mail-wm1-x331.google.com ([2a00:1450:4864:20::331]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wL589-000000014NZ-2YcO for pgsql-general@lists.postgresql.org; Thu, 07 May 2026 20:15:35 +0000 Received: by mail-wm1-x331.google.com with SMTP id 5b1f17b1804b1-48d146705b4so15680915e9.3 for ; Thu, 07 May 2026 13:15:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1778184931; x=1778789731; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=V3aBykWk5WxHUn4cHGYJ/zzFxNdADrBRPQRhbVGWvJc=; b=oReEa6RB71nTt+rMzNKwwP901NVS5aw1AlKnCucV9sa87u4wQkUfA0Y0M54i8LfYE0 EtYqp4HxSNRVHkmx+qfT4yDlFBL3lClR9G7zBjaHfbg3a4wew31AiuxC6O5TB/6emUq0 Z4SHaOs+7D0SEXBkZfeP1lVDTujpFDIHxYeXW7EvMGgLujrtwktLJfBpC6QhGM8Rx2SZ OKXVhOJH5zgmZIkjA98L9g24oLaoTfbufEbodNFTSzlusct1RdsLwjR4ob4fenjlxbFF iFtoaCcoR3jhTkmF1zgFCmK2xEApDetWVvWke8A4CV4nEdgRAqCArdfXcso9+QMgDWFP DMag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1778184931; x=1778789731; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=V3aBykWk5WxHUn4cHGYJ/zzFxNdADrBRPQRhbVGWvJc=; b=izeFO286v5+PeOdpVikT5QXaUzyUU7X5z1a/myiTRfg8qhiHkqPZNdgkV1yP5X5MqZ yWPa5ECMkhtXHzqo9DaBXJYQP8MptlRKDF7CwtH8nu0iGZJpKwXqKbf5go9QM5apId0Y l5gfBbnOtm2mhM+DO1P06VkhYyDInvNMDwR8sHciV41hACc22iVpk7JN0knBYYw+46uo tkMfTVsMmHFUailkZu1MN2iH2nhZADHTjc/R+k9pzkHwv+Dsk1oxnW8efg0dNPqNC+Tx kRpDlMd5OdSBzJu00FQDBNUqVP+dS16utpQqILoEeeUAp9YLCZv/0EqMFAEveMpmS1el WMzA== X-Gm-Message-State: AOJu0Yws4dUT0mu8zoDrbaI4blLVGQ4pzDEMaJMKbgqVTmBEAvWSY2tB ie/v+7bo8KEwIjdnh1/PiDOYtd5mGzVs8Ya/cVgcq1lbSfjeZDnxVEq4V+uUyA== X-Gm-Gg: AeBDiesPCcl31NwG3VNI/Ac+A0aEryXdcaUagCxa+8wGKUf11CXiQpcqvzS1saWNlJ5 ab4Cqlfh1ZgZsa4XmIJKkIpKlAnp04boKkj/knqGljgNZ/QbUkAXTHN/WtAlk50Ms3kvwg7RpBq SwjjgL5ll9ecOWzz7VY0ORZG/2ce0vM2aoiTEzKjk2ZEmwt5mdCiDYDWM3DbLirmCplfyhq3GlM eeTen4VqkSuC01suo9catTwkfGZ0xh2X5XnrLZfSULGT/k4gvnVfC/xW+F9H0LivYrdY9B0YJft rJDz1/0sYcIod/Ok6dZPq8PAN4LqDa57b/yEWRMLYXlpvebgRWLCfnIWWRu6S5zM68BM+76A9Bo 5r3utdRlmzig4ojjEHWBTdKcRTJD/18i35nXSaMmJoyztrYlzabMQ8QhLy6XjPG54hejAFZRvNM YlPz10o7Hum32IxrgkCafanrjYKZ25f13oAes= X-Received: by 2002:a05:600c:1d18:b0:489:1a63:509c with SMTP id 5b1f17b1804b1-48e51dd689fmr147732715e9.0.1778184924846; Thu, 07 May 2026 13:15:24 -0700 (PDT) Received: from ?IPv6:2a01:50a0:aa10:1a36::106? ([2a01:50a0:aa:0:185:40:248:10]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-45416b5c811sm1317153f8f.17.2026.05.07.13.15.24 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 May 2026 13:15:24 -0700 (PDT) Message-ID: Subject: Re: untracked child process (PID XXXXX) exited with exit code 120 From: Torsten Krah To: pgsql-general@lists.postgresql.org Date: Thu, 07 May 2026 22:15:23 +0200 In-Reply-To: References: <2e556bbdbe6ccac93ecb6cfbb5a815059ff5aad2.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.52.3-0ubuntu1.1 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Am Donnerstag, dem 07.05.2026 um 19:51 +0200 schrieb Alexander Kukushkin: > My guess would be that the postmaster in your container is running > with > PID=3D1. > The unexpected process was probably started by docker entrypoint > before it > did exec postgres [...]. > As a result, this subprocess became a direct child of the postmaster > and we > got the problem. >=20 > The most common solution is to avoid running postmaster with PID=3D1. > There are two options available: > 1. dumb-init > 2. start container using "docker run --init [...]" My /docker-entrypoint-initdb.d is empty and I did not customize the default entrypoint or command to run (there was a ready to use data dir / volume, so it just skipped initialization on start), so I am not sure what else should have been started, but I know, just guesswork here. Between starting the pod initially: 16:52:28.317 and the time the untracked process did fail: 18:39:13.947 nearly 2 hours passed, ah too bad I will never know what PID 120 was. Yes, the postgres image postgres:18-trixie does run the postgres process with PID=3D1: postgres 1 0.0 0.2 4443124 139360 ? Ss May06 0:27 postgres Using kubernetes as runtime, there is no "--init" option and e.g. tini is not in the image - if is is a problem running postgres with pid=3D1, could e.g. tini be added to the image (if so, do you know where to address this?) and used as default entrypoint (I know I can build one myself and extend that image to provide tini, but I would prefer just to use the upstream image as-is)? kind regards Torsten