From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <t.lamprecht@proxmox.com>
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))
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id ABE3460862
 for <pve-user@lists.proxmox.com>; Thu, 26 Nov 2020 15:46:03 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id 9B7FC125D0
 for <pve-user@lists.proxmox.com>; Thu, 26 Nov 2020 15:46:03 +0100 (CET)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
 [212.186.127.180])
 (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 firstgate.proxmox.com (Proxmox) with ESMTPS id C5282125C6
 for <pve-user@lists.proxmox.com>; Thu, 26 Nov 2020 15:46:01 +0100 (CET)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
 by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 8DC5C45C8F;
 Thu, 26 Nov 2020 15:46:01 +0100 (CET)
To: uwe.sauter.de@gmail.com, Proxmox VE user list <pve-user@lists.proxmox.com>
References: <4545c7f5-9b50-2f0a-952a-cc532ad01b13@gmail.com>
 <15f5893d-83cf-ee8c-11ff-0a67e376dc41@gmail.com>
 <9c0ceb9e-ff96-b12f-a4ed-1e1ac250fbb6@gmail.com>
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
Message-ID: <11d60eb0-9b17-53ba-cc21-79728e1296b0@proxmox.com>
Date: Thu, 26 Nov 2020 15:46:00 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:83.0) Gecko/20100101
 Thunderbird/83.0
MIME-Version: 1.0
In-Reply-To: <9c0ceb9e-ff96-b12f-a4ed-1e1ac250fbb6@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-SPAM-LEVEL: Spam detection results:  0
 AWL -0.083 Adjusted score from AWL reputation of From: address
 GB_TO_NAME_FREEMAIL      0.01 Freemail spear phish with free mail
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 NICE_REPLY_A           -0.001 Looks like a legit reply (A)
 RCVD_IN_DNSWL_MED        -2.3 Sender listed at https://www.dnswl.org/,
 medium trust
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [PVE-User] Caution: ceph-mon service does not start after
 today's updates
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Thu, 26 Nov 2020 14:46:03 -0000

On 26.11.20 15:15, Uwe Sauter wrote:
> Am 26.11.20 um 15:10 schrieb Lindsay Mathieson:
>> On 26/11/2020 10:18 pm, Uwe Sauter wrote:
>>> this is a warning for all that are eager to apply today's updates.
>>> In my case the ceph-mon@<host> service did not start after a reboot w=
hich caused a hanging Ceph once the second monitoring service
>>> went offline.
>>
>> I ran into that, also the node failed to rejoin the cluster quorum. sy=
slog had errors relating to the pem-ssl key.
>>
>> Manually start the pve cluster service and a 2nd reboot solved both is=
sues.
>>
>=20
> Yes, rebooting might help, but not reliably. I had nodes that needed se=
veral reboots until pvestatd did not fail.
>=20
> I also had failed ceph-mgr@<host> services (with Nautilus).
>=20
> My current suspicion is that my network takes too long to become availa=
ble.
>=20

Note, it's always good idea to check if all services are running OK again=
 before
continuing with upgrading the next host, not just on this update :-)

Also, ceph monitors can be nicely restarted over the web interface, there=
's a
visible status about which services run outdated versions/need a restart.=



Anyway, do you have any logs which could give more details for possible i=
ssues?

regards,
Thomas