From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Lindsay Mathieson <lindsay.mathieson@gmail.com>
Subject: Re: [PVE-User] Caution: ceph-mon service does not start after today's updates
Date: Thu, 26 Nov 2020 17:14:40 +0100 [thread overview]
Message-ID: <72fbd5d5-1c9b-5d59-5256-4cf1dd1f79cb@proxmox.com> (raw)
In-Reply-To: <269aba60-412c-578b-9757-6a0567d270e5@gmail.com>
On 26.11.20 16:03, Lindsay Mathieson wrote:
> On 27/11/2020 12:46 am, Thomas Lamprecht wrote:
>> 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 issues?
>
> I have a node that is just failing to rejoin the cluster and the ceph mon & mgr fail to start.
>
>
> Seeing this repeated in syslog
>
> Nov 27 00:58:23 vnh pveproxy[2903]: /etc/pve/local/pve-ssl.key:
> failed to load local private key (key_file or key) at
> /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1737.
> Nov 27 00:58:23 vnh pveproxy[2904]: /etc/pve/local/pve-ssl.key:
> failed to load local private key (key_file or key) at
> /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1737.
> Nov 27 00:58:23 vnh pveproxy[2905]: /etc/pve/local/pve-ssl.key:
> failed to load local private key (key_file or key) at
> /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1737.
> Nov 27 00:58:26 vnh ceph-mon[2073]: 2020-11-27 00:58:26.378
> 7fb182935700 -1 mon.vnh@0(probing) e9 handle_auth_bad_method hmm,
> they didn't like 2 result (95) Operation not supported
> Nov 27 00:58:26 vnh ceph-mon[2073]: 2020-11-27 00:58:26.390
> 7fb17d92b700 -1 mon.vnh@0(probing) e9 handle_auth_bad_method hmm,
> they didn't like 2 result (95) Operation not supported
> Nov 27 00:58:26 vnh ceph-mon[2073]: 2020-11-27 00:58:26.526
> 7fb183136700 -1 mon.vnh@0(probing) e9 handle_auth_bad_method hmm,
> they didn't like 2 result (95) Operation not supported
> Nov 27 00:58:27 vnh ceph-mon[2073]: 2020-11-27 00:58:27.702
> 7fb182935700 -1 mon.vnh@0(probing) e9 handle_auth_request no
> AuthAuthorizeHandler found for auth method 1
>
the errors seems like being the result of pve-cluster not coming up,
which seems the actual problem.
>
> The following gets the node back on the cluster:
>
> systemctl start pve-cluster.service
Anything of pve-cluster service in the log?
What does:
# systemd-analyze verify default.target
outputs?
cheers,
Thomas
next prev parent reply other threads:[~2020-11-26 16: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
2020-11-26 14:46 ` Thomas Lamprecht
2020-11-26 15:03 ` Lindsay Mathieson
2020-11-26 16:14 ` Thomas Lamprecht [this message]
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=72fbd5d5-1c9b-5d59-5256-4cf1dd1f79cb@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=lindsay.mathieson@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