From: Uwe Sauter <uwe.sauter.de@gmail.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Caution: ceph-mon service does not start after today's updates
Date: Thu, 26 Nov 2020 15:15:00 +0100 [thread overview]
Message-ID: <9c0ceb9e-ff96-b12f-a4ed-1e1ac250fbb6@gmail.com> (raw)
In-Reply-To: <15f5893d-83cf-ee8c-11ff-0a67e376dc41@gmail.com>
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 which caused a hanging Ceph once the second monitoring service
>> went offline.
>
> I ran into that, also the node failed to rejoin the cluster quorum. syslog had errors relating to the pem-ssl key.
>
> Manually start the pve cluster service and a 2nd reboot solved both issues.
>
Yes, rebooting might help, but not reliably. I had nodes that needed several reboots until pvestatd did not fail.
I also had failed ceph-mgr@<host> services (with Nautilus).
My current suspicion is that my network takes too long to become available.
Regards,
Uwe
next prev parent reply other threads:[~2020-11-26 14:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 12:18 Uwe Sauter
2020-11-26 14:10 ` Lindsay Mathieson
2020-11-26 14:15 ` Uwe Sauter [this message]
2020-11-26 14:46 ` Thomas Lamprecht
2020-11-26 15:03 ` Lindsay Mathieson
2020-11-26 16:14 ` Thomas Lamprecht
2020-11-26 16:35 ` Thomas Lamprecht
2020-11-26 18:56 ` Thomas Lamprecht
2020-11-26 19:35 ` [PVE-User] [update available] " Thomas Lamprecht
2020-11-26 19:54 ` Uwe Sauter
2020-11-27 0:53 ` Lindsay Mathieson
2020-11-27 8:19 ` Uwe Sauter
2020-11-27 13:18 ` Lindsay Mathieson
2020-11-27 13:29 ` Jean-Luc Oms
2020-11-27 13:31 ` Lindsay Mathieson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c0ceb9e-ff96-b12f-a4ed-1e1ac250fbb6@gmail.com \
--to=uwe.sauter.de@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox