From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id BC4EC6070F for ; Wed, 9 Sep 2020 20:19:12 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A664013C58 for ; Wed, 9 Sep 2020 20:18:42 +0200 (CEST) Received: from mx0.matrixscience.co.uk (mx0.matrixscience.co.uk [83.217.111.202]) by firstgate.proxmox.com (Proxmox) with ESMTP id F373513C49 for ; Wed, 9 Sep 2020 20:18:40 +0200 (CEST) Received: from [192.168.10.196] (bison.matrixscience.co.uk [192.168.10.196]) by mx0.matrixscience.co.uk (Postfix) with ESMTP id 762E52C05E0 for ; Wed, 9 Sep 2020 19:11:48 +0100 (BST) To: pve-user@lists.proxmox.com References: <65499872-efcc-6f73-4b73-4039728c2a4e@matrixscience.com> <93d6fc90-f902-e33a-d2ee-b09daebc1d1b@proxmox.com> From: Adam Weremczuk Organization: Matrix Science Ltd Message-ID: <6f14f3f9-87d2-f685-030a-a1b1a61de003@matrixscience.com> Date: Wed, 9 Sep 2020 19:11:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <93d6fc90-f902-e33a-d2ee-b09daebc1d1b@proxmox.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-SPAM-LEVEL: Spam detection results: 0 AWL 0.413 Adjusted score from AWL reputation of From: address KAM_ASCII_DIVIDERS 0.8 Spam that uses ascii formatting tricks KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -1.626 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: Re: [PVE-User] CT replication error X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2020 18:19:12 -0000 Hi Fabian, Yes, all replication use the same shared zfs storage. Are you referring to /var/log/pve/replicate/102-0 file? It seems to only hold information about the last run. Anyway, my problem turned out to be the node2 still holding zfs-pool/subvol-102-disk-0 of the previous container. I had deleted the old container from the web GUI before creating a new one in its place (id 102). For some reason node2 still had the old disk. Once I rm'ed it from the shell of node2 replication started working for CT-102. Regards, Adam On 09/09/2020 08:51, Fabian Ebner wrote: > Hi, > could you check the replication log itself? There might be more > information there. Do the working replications use the same storages > as the failing one? > > Am 03.09.20 um 14:56 schrieb Adam Weremczuk: >> Hi all, >> >> I have a dual host set up, PVE 6.2-6. >> >> All containers replicate fine except for 102 giving the following: >> >> Sep  3 13:49:00 node1 systemd[1]: Starting Proxmox VE replication >> runner... >> Sep  3 13:49:02 node1 zed: eid=7290 class=history_event >> pool_guid=0x33A69221E174DDE9 >> Sep  3 13:49:03 node1 pvesr[6852]: send/receive failed, cleaning up >> snapshot(s).. >> Sep  3 13:49:03 node1 pvesr[6852]: 102-0: got unexpected replication >> job error - command 'set -o pipefail && pvesm export >> zfs-pool:subvol-102-disk-0 zfs - -with-snapshots 1 -snapshot >> __replicate_102-0_1599137341__ | /usr/bin/ssh -e none -o >> 'BatchMode=yes' -o 'HostKeyAlias=node2' root@192.168.100.2 -- pvesm >> import zfs-pool:subvol-102-disk-0 zfs - -with-snapshots 1 >> -allow-rename 0' failed: exit code 255 >> Sep  3 13:49:03 node1 zed: eid=7291 class=history_event >> pool_guid=0x33A69221E174DDE9 >> >> Any idea what the problem is and how to fix it? >> >> Regards, >> Adam >> >> >> _______________________________________________ >> pve-user mailing list >> pve-user@lists.proxmox.com >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user