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 1qdseW-0053Uf-Pt for pgsql-general@arkaria.postgresql.org; Wed, 06 Sep 2023 13:33:04 +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 1qdseV-00ANXh-N9 for pgsql-general@arkaria.postgresql.org; Wed, 06 Sep 2023 13:33:03 +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 1qdseV-00ANXV-Az for pgsql-general@lists.postgresql.org; Wed, 06 Sep 2023 13:33:03 +0000 Received: from mail-pl1-x62a.google.com ([2607:f8b0:4864:20::62a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qdseN-003QJK-D7 for pgsql-general@lists.postgresql.org; Wed, 06 Sep 2023 13:33:02 +0000 Received: by mail-pl1-x62a.google.com with SMTP id d9443c01a7336-1c337aeefbdso25375605ad.0 for ; Wed, 06 Sep 2023 06:32:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694007172; x=1694611972; darn=lists.postgresql.org; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=9DsVciXMDaZcpATbRYecel9D2CCd5cHXVVCfD2n6T6M=; b=Dq4+YGe07/htW1Az4K9L/u2Q2dRWK0CthkGu9pXn3rNzMJZDQIbnvL7NnKZlujZKSz yRwJqgIVZEeDlXuCRwwIlQeSZcQBhBfPZ5hpZZ7dRcAO6ZR29xEqZcuTLCq1ffkiHJeI 5JTQlDhi7ExlNpbwUojKsZ7WUh5kQJhxSh5Ch+uXPezV73txMDUDoeJ8KZIuwR1kaMuu niCEgx8UgEsU4jt63k6S/U2PWl1t+QkAPiRsOau4CBsuKn6SoX12psAe3jo05lws0eW9 x0ZpKB9wS7rqvKBo5V9Q+lZ3M5ie+ExD8depoIGNFbATpo9vhMnuM7r82c4+/0sYhyKk agjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1694007172; x=1694611972; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=9DsVciXMDaZcpATbRYecel9D2CCd5cHXVVCfD2n6T6M=; b=VScMSfZ6TkVPq59I9QjNerJtqyU8IvLlVZ9yzXRKgzsgnBGzKBrxbXQ5AMPWy+z+x3 XCVtYltxv6R0zpxMDMhfsepoa/x85ZeufuJm4Jz5KKnyMVW0wdTSBVJIjFFpeEVYmVQx lx2/qnApZkLWA20PqE8vd7jw8yZswTamcQ+PHVabh/EAiIuhmMnoxEx1XOjbusmt0SYE vFLh6+Kur9oW78EW47tIXrJ9SFNrdW9xT7pwlk4JHUCmYWdRDDOUayzFe2jBuTaTi2do 3COXlLz2Qjmpl35YK8H13kWMhImJix68tlZ40zJTxIrxcBwkoq9XAS4xZ6xHUpuVGVqG nV1A== X-Gm-Message-State: AOJu0YyWUNcmki1PQU7AGUYwqvOS8UE4LM2NtHsZpFDz8hsqSsHBiBXp QbHBSEYEeA6M9zsO7smQSlgyIjQYJ14= X-Google-Smtp-Source: AGHT+IG9ihYeMjCv8h9z6zVi+hd6HKG+EryBP+B3UCjoN3nXkQw/yWRAoTagQZnwctXH1tjmrwMsDQ== X-Received: by 2002:a17:902:d504:b0:1c0:ec66:f2b5 with SMTP id b4-20020a170902d50400b001c0ec66f2b5mr19974457plg.57.1694007171848; Wed, 06 Sep 2023 06:32:51 -0700 (PDT) Received: from ?IPV6:2601:681:5a00:f790:5167:bfa2:1136:cfd8? ([2601:681:5a00:f790:5167:bfa2:1136:cfd8]) by smtp.gmail.com with ESMTPSA id a20-20020a170903101400b001b06c106844sm11116465plb.151.2023.09.06.06.32.50 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Sep 2023 06:32:51 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------k2swMySQuuqoL7oN2Xd07p48" Message-ID: Date: Wed, 6 Sep 2023 07:32:49 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: Pgbackrest Restore Error - Segmentation fault (core dumped) Content-Language: en-CA To: pgsql-general@lists.postgresql.org References: From: Rob Sargent In-Reply-To: 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. --------------k2swMySQuuqoL7oN2Xd07p48 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 9/6/23 05:08, pgdba pgdba wrote: > Hello, when I restore with Pgbackrest, I get the following error, I > couldn't find a solution when I researched, can you support? > > postgres@dev-test:~$ pgbackrest > --config=/etc/pgbackrest/pgbackrest.conf --stanza=db3 > --log-level-console=info --type=immediate restore > WARN: configuration file contains invalid option 'archive-mode' > 2023-09-06 06:54:45.826 P00 INFO: restore command begin 2.27: > --config=/etc/pgbackrest/pgbackrest.conf --log-level-console=info > --pg1-path=/var/lib/ postgresql/11 --repo1-host=0.0.0.1 > --repo1-host-user=postgres --stanza=db3 --type=immediate > Segmentation fault (core dumped) > > Thanks, Have you tried removing the invalid option ('archive-mode') from the config file? --------------k2swMySQuuqoL7oN2Xd07p48 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
On 9/6/23 05:08, pgdba pgdba wrote:
Hello, when I restore with Pgbackrest, I get the following error, I couldn't find a solution when I researched, can you support?

postgres@dev-test:~$ pgbackrest --config=/etc/pgbackrest/pgbackrest.conf --stanza=db3 --log-level-console=info --type=immediate restore
WARN: configuration file contains invalid option 'archive-mode'
2023-09-06 06:54:45.826 P00 INFO: restore command begin 2.27: --config=/etc/pgbackrest/pgbackrest.conf --log-level-console=info --pg1-path=/var/lib/ postgresql/11 --repo1-host=0.0.0.1 --repo1-host-user=postgres --stanza=db3 --type=immediate
Segmentation fault (core dumped)

Thanks,
Have you tried removing the invalid option ('archive-mode') from the config file?

--------------k2swMySQuuqoL7oN2Xd07p48--