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 1wL2sx-001Ubc-3D for pgsql-general@arkaria.postgresql.org; Thu, 07 May 2026 17:51:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wL2sv-005Sjb-2k for pgsql-general@arkaria.postgresql.org; Thu, 07 May 2026 17:51:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wL2sv-005Sj0-12 for pgsql-general@lists.postgresql.org; Thu, 07 May 2026 17:51:41 +0000 Received: from mail-oo1-xc2f.google.com ([2607:f8b0:4864:20::c2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wL2ss-00000000gBZ-2a46 for pgsql-general@lists.postgresql.org; Thu, 07 May 2026 17:51:40 +0000 Received: by mail-oo1-xc2f.google.com with SMTP id 006d021491bc7-6967080e6c0so675591eaf.2 for ; Thu, 07 May 2026 10:51:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1778176298; cv=none; d=google.com; s=arc-20240605; b=dai5IhC8+kmXUQ14ffz8o373m4dmzgLSPs1exN/tQUNiExVgLYuAoHK48SHsLW0fK3 YmLVRGb/aeDIBNwhDSzPya2MuJy1TZwr3ao353wMnovjJdAsRpbe1yiQ1WMwZpXvtvfQ 9omj1mnVKxAcJNGGdv1/PTXJiY8vAbR9+QM6EhSW/nrPTTgyDRE9DzguXHl0JZdoursi s1fTWNLW7FkLhX7VQ0xsKkN4i7xlty45+z4ERtGOay6x9n4PyGE9CSyy37NESAOarffa mhYUBQNe2FRum+Kl4yp6Ikl2z8OAvq+aqdYgwRRHxjXDYdpY+v0vifYm8TkM1IRNvj+A 6FZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=KRGbgseJpMsz0cgEPuWpZ7pUl08WzMyJEwvIegdZsXc=; fh=7BlUO7s8y7Wztffu0tuqdcDXr5gOBXvIIgGZyj5Uw6M=; b=JpQKCDxaAxi/v91b/p74rAADyODrCp4kLXN0C1hQNLZRkC2nLOlBf9jBuEH8yRb2PU hvncKti9mKcV4nqcrWfXTjdE0U0C5D4K+M7bYuSFFiE2sHPuE6K1eqBe3vw0MIUSxHzc QrpUIjpfr/1vnTb5sRudOo4dlh6exJLW0N0TwEQJDgvO0J6KIswbKBMR9oCq+p2p2h19 5sNXdDHH+95P+Srd9eqF7Fx0KOBvPkjl/6Xf3n8mygTLOaKKSTXq+9rH9kf5gjslIhi7 tcBP2TK/DjC6ibt56GJJmDv5oFgby6jb3SABKo2L5cLyNfejpHDdyb8hG9UfLCI0Y0Yb BMxw==; darn=lists.postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1778176298; x=1778781098; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KRGbgseJpMsz0cgEPuWpZ7pUl08WzMyJEwvIegdZsXc=; b=Etf1Z+fJ79q9vUtT5dilkGvi2IuJyG2yclYTIWyNeeyY08SX0wQNsmtJ9uP/wgojUi W1BU2wJR7lbDR+8u7ibGAB5hpY0ckNKjhgTHI/rqU1Na5i56w4jgOEDTr0eVZnADjXt3 969IrYx/nYaowSSRJTFfeKuE2V8hjg/ZGos5Fe+0PfQA58HimVRdj7KNTkAvtjNlcpeZ DlUj3vWn+dxm92A+YvDP6sgDe93YcbmdeZk3rEIZWaQSYEWak2C2/OTEDgwdNQkGhT2V vpMjpLWZbcrjESATOaeMJVynSANgIdXUu02FbdkIRLQXGTtO1ger1dx4nSy/jTLHNw6t mrlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1778176298; x=1778781098; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=KRGbgseJpMsz0cgEPuWpZ7pUl08WzMyJEwvIegdZsXc=; b=COW8muzasbhWZ8Vi8YQajwfJc93M/6OQ2Z3xoUfJKdtuVE84EpuugOPMBJFTtcbHdL Z0WB9lwPXTosymN3W6/jisH5vm6iJyp/VxjRxDI51WOdeJO3tuvThtKgZEwbx7NZ/s0n EFhFqSeqpZtgg6ZgYESJfmC36qEhlyQbyTJw4hIN5sq3/peKAgD7J51zFLP/kJfpC3Ty NfihcRV2wPGutMxXR4JdeFWdWQeY9IGU3z9ZM7MmWje+cweMn39I0oHVzDE7Ur5F+Ar5 cOn1A+pyepbuHrfQ6v/jpiztzKNOSOh+EaV15Hu80/jV8qvk7S7briXI7iGv1YBmvSyG YKdw== X-Gm-Message-State: AOJu0YyqtauKm9pR3KxSR5CKz9mqsR/J/v5vrHtwdHqYKGu3vnDEWWTt M0OiQ/J13ajrl1c1MgXoqMS6+EyapIvnE1C05OFChr/CjkAg6QTAy3QslnQWdJAvNj2cLvkxSGZ Ne8Y2KuzhGtZ9sR6s7hNLU0WXsqPeGDg= X-Gm-Gg: AeBDiesXdMcGkEY9JrkIjA3FTYPRscqDne2fxUOdV0HKm/j4qXCwZhEoA1ca32uGbGW GxwUnTuHfqb3N3Q+zSUQA9WgYekba3No2n4QZox/mkNsqkJR7zK2FZIpYwi7gEWY7IOZGHGDesM p/g2ylE7NlkzDFWtnLQtZ8aF81PtkBao2ddVYQ2qiZpjb2mbFfJJf9R6nI5+vDCobAYcA0fwEz7 ESoeizZPboxz04ZV8lHm6xnF7PyOFqnx+XOSxM0+bKlB0joe02RSmQuS7wln3/Io76SxUXh9r1g gqTBofsqAqNFGqGW6KR3CKdQHHL8JTjiBCWaY24l X-Received: by 2002:a05:6820:178a:b0:67e:366b:53b7 with SMTP id 006d021491bc7-69998d5c303mr4843934eaf.53.1778176298421; Thu, 07 May 2026 10:51:38 -0700 (PDT) MIME-Version: 1.0 References: <2e556bbdbe6ccac93ecb6cfbb5a815059ff5aad2.camel@gmail.com> In-Reply-To: <2e556bbdbe6ccac93ecb6cfbb5a815059ff5aad2.camel@gmail.com> From: Alexander Kukushkin Date: Thu, 7 May 2026 19:51:27 +0200 X-Gm-Features: AVHnY4JYDkvpLcUh0aCml0F1DWBqIAxGXjgFaR3ASxXDeaK_VH9wHV48IbCKev4 Message-ID: Subject: Re: untracked child process (PID XXXXX) exited with exit code 120 To: Torsten Krah Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000009d913d06513dee07" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009d913d06513dee07 Content-Type: text/plain; charset="UTF-8" My guess would be that the postmaster in your container is running with PID=1. 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. The most common solution is to avoid running postmaster with PID=1. There are two options available: 1. dumb-init 2. start container using "docker run --init [...]" On Thu, 7 May 2026 at 19:37, Torsten Krah wrote: > Hi, > > I am running PostgreSQL 18.3 (Debian 18.3-1.pgdg13+1) (docker image) > and found this in my database logs the other day: > > 2026-05-07 18:39:13.947 CEST [1] LOG: untracked child process (PID 33254) > exited with exit code 120 > 2026-05-07 18:39:13.947 CEST [1] LOG: terminating any other active server > processes > 2026-05-07 18:39:14.077 CEST [1] LOG: all server processes terminated; > reinitializing > > > Anyone an idea about that untracked child process and what exit code > 120 of that process would mean / want to tell me? > > Thanks. > > Torsten > > PS: I used https://www.postgresql.org/search/ , but was unsuccessful so > far to get any hints on this, but maybe I just did not find the correct > question yet ;). > > > > -- Regards, -- Alexander Kukushkin --0000000000009d913d06513dee07 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
My guess would be that the postmaster in your contain= er is running with PID=3D1.
The unexpected process was probably s= tarted by docker entrypoint before it did exec postgres [...].
As= a result, this subprocess became a direct child of the postmaster and we g= ot the problem.

The most common solution is to avo= id running postmaster with PID=3D1.
There are two options availab= le:
1. dumb-init
2. start container using "docker = run=C2=A0--init [...]"

On Thu, 7 May 2026 a= t 19:37, Torsten Krah <krah.tm@gmai= l.com> wrote:
Hi,

I am running PostgreSQL 18.3 (Debian 18.3-1.pgdg13+1) (docker image)
and found this in my database logs the other day:

2026-05-07 18:39:13.947 CEST [1] LOG:=C2=A0 untracked child process (PID 33= 254) exited with exit code 120
2026-05-07 18:39:13.947 CEST [1] LOG:=C2=A0 terminating any other active se= rver processes
2026-05-07 18:39:14.077 CEST [1] LOG:=C2=A0 all server processes terminated= ; reinitializing


Anyone an idea about that untracked child process and what exit code
120 of that process would mean / want to tell me?

Thanks.

Torsten

PS: I used https://www.postgresql.org/search/ , but was unsucc= essful so
far to get any hints on this, but maybe I just did not find the correct
question yet ;).





--
Regards,
--
Alexander Kukushkin
=
--0000000000009d913d06513dee07--