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 1suvFU-00BCfR-DV for pgsql-general@arkaria.postgresql.org; Sun, 29 Sep 2024 14:50:13 +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 1suvEU-005Jjl-0G for pgsql-general@arkaria.postgresql.org; Sun, 29 Sep 2024 14:49:10 +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 1suvET-005Jjd-LO for pgsql-general@lists.postgresql.org; Sun, 29 Sep 2024 14:49:09 +0000 Received: from mail-ej1-x636.google.com ([2a00:1450:4864:20::636]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1suvEP-001h4Z-Kv for pgsql-general@lists.postgresql.org; Sun, 29 Sep 2024 14:49:08 +0000 Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-a8d56155f51so448157866b.2 for ; Sun, 29 Sep 2024 07:49:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727621345; x=1728226145; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=vzf4kShLbsr3Q0z2z/l5MmJsysqxMaF59bTJUf/jIgM=; b=bRNmAoJ26PWx++/CZrEviJTHoR4/9h5VxoqHR/KimkSQs45X9F0Ck1Aix7GNtpN0IQ Ngs23B7w+Wy6+xp6yhJla1lv6V0xsaMGfjao28TT5HbGHQnMPIr9BhCZzdfrJWcc6JGs iJQYANeJV/8b24KNvOPLiPpvgal+sk26AACUFV7RgYC16mgMswGnNVURteD8Jj6DbDG4 eAC/Ao2dd8Sm/40dX9EjX+cesTST94Qh1NhUXSyXua39lQ2FnUsVWIDWeN+9GAOTWwwy TAvLhMNagWbG1BF37cYffGbrWvt5Pa9qwIhRCHu3OmOxL8WEhgS7RgQUBQcv373FZPd0 91sg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727621345; x=1728226145; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=vzf4kShLbsr3Q0z2z/l5MmJsysqxMaF59bTJUf/jIgM=; b=vJurmOobvWVc1J9BO8vta6ukErQmje8xrxRF+DMH3Huxg7mMniv/MAA2RYEp9CKYWL Uzw5R9xo6CCvsFVNdb/Fgijn2xhzy+rtAGOPFrlD3ifIVn8+BS097H1rDD9jgv0SYuht UqLJ/fQOKAj3s7N/Pz+1jgxJKQsNHLMGE300spwlELlKFv3nAQnnhhn2cA4tDWje+kly 7D6yw+nnixxOhJe3soUkGM78T134m4fLiHr5C9LoylT+m9S0ixGlepj55K1s2pbjY8ff yqYb0H8Bk9aeia9PoGAV0ftELR95BGDXfeFguVnxFej+xSS31Do6h636AY+nE9pbmz1P k5cw== X-Gm-Message-State: AOJu0Yx2rEi8EPk1epeFEg/4XgUfWx2RtQrZGe5Tc0r1zeSgjqIzstY4 d1EmqwjDYr/YCc2Qr+L00WwAW+JsbzAhowadbOhWFLHFhhNY65cFGq6CeJdjyGXYFU9yLl1oefE 9BYR1mPDQd1uvy8q3n5xKggiFD1NW+6kn X-Google-Smtp-Source: AGHT+IHY+Tttb72EgC7Calco+HLbvkX4nULx5ezcUXTL4DWibOe9VNYWqUjdhyaJFpAZXbEa63XGSyf4QhR4GBQOMcc= X-Received: by 2002:a17:907:9341:b0:a8d:4e26:c9b9 with SMTP id a640c23a62f3a-a93c49218abmr1005518666b.17.1727621345404; Sun, 29 Sep 2024 07:49:05 -0700 (PDT) MIME-Version: 1.0 From: Koen De Groote Date: Sun, 29 Sep 2024 16:48:54 +0200 Message-ID: Subject: Basebackup fails without useful error message To: PostgreSQL General Content-Type: multipart/alternative; boundary="0000000000009971de06234330e4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009971de06234330e4 Content-Type: text/plain; charset="UTF-8" Having run a basebackup, I'm getting this output at the very end: pg_basebackup: child process exited with error 1 pg_basebackup: removing contents of data directory "/mnt/base_backup/dir/" Is there a way to get more information as to what exactly happened? I'd like to look into fixing this or doing whatever is required so that it doesn't happen again, but this just isn't enough info. Where do I start looking? Regards, Koen De Groote --0000000000009971de06234330e4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Having run a basebackup, I'm getting this output at th= e very end:

pg_basebackup: child process exited with err= or 1
pg_basebackup: removing contents of data directory "/mnt/base_= backup/dir/"

Is there a way to get more i= nformation as to what exactly happened?

I'd li= ke to look into fixing this or doing whatever is required so that it doesn&= #39;t happen again, but this just isn't enough info. Where do I start l= ooking?

Regards,
Koen De Groote
--0000000000009971de06234330e4--