From: Frank Thommen <f.thommen@dkfz-heidelberg.de>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] After update Ceph monitor shows wrong version in UI and is down and out of quorum
Date: Fri, 8 Jan 2021 12:44:58 +0100 [thread overview]
Message-ID: <8599b7ad-0ea0-b836-4492-d80b9d43cfcb@dkfz-heidelberg.de> (raw)
In-Reply-To: <1073f776-3910-dbde-8304-e86b5f6ed4fb@web.de>
yes /etc/ceph/ceph.conf is identical on all three hosts and there is a
mon_host line with the correct IPs. Interestingly there is a special
section for odcf-pve02:
-----------
[mon.odcf-pve02]
public_addr = 192.168.255.2
-----------
This is the same IP as in the mon_host line. However there is no
equivalent section for the other two nodes.
Frank
On 08.01.21 12:27, Peter Simon wrote:
> Hi Frank,
>
> your /etc/ceph/ceph.conf is the same on all hosts ?
>
> is there mon host = ip1, ip2, ip3
>
> and seperate sections with [mon.x]
> host = hostname
> mon addr = ip:6789
>
> Cheers
> Peter
>
> Am 08.01.21 um 12:05 schrieb Frank Thommen:
>>
>>
>> On 08.01.21 11:45, Uwe Sauter wrote:
>>>
>>>
>>> Am 08.01.21 um 11:36 schrieb Frank Thommen:
>>>>
>>>> On 05.01.21 21:17, Frank Thommen wrote:
>>>>> On 05.01.21 21:02, Uwe Sauter wrote:
>>>>>> There's a paragraph about probing mons on
>>>>>>
>>>>>> https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-mon/
>>>>>>
>>>>>>
>>>>>
>>>>> I will check that (tomorrow :-)
>>>>
>>>>
>>>> using the monitor's admin socket on either of the three nodes I can
>>>> query the monitors of 01 and 03 (the good ones) but not of 02 (the
>>>> problematic one):
>>>>
>>>> root@odcf-pve01:~# ceph tell mon.odcf-pve02 mon_status
>>>> Error ENOENT: problem getting command descriptions from mon.odcf-pve02
>>>> root@odcf-pve01:~#
>>>>
>>>> The monitor daemon is running on all three and the ports are open.
>>>>
>>>> Any other ideas?
>>>
>>> You could check the permissions on the socket:
>>>
>>> ss -xln | grep ceph-mon
>>> SOCK=$(ss -xln | awk '/ceph-mon/ {print $5}')
>>> ls -la ${SOCK}
>>>
>>> On my host, this shows
>>>
>>> srwxr-xr-x 1 ceph ceph 0 Dec 20 23:47
>>> /var/run/ceph/ceph-mon.px-alpha-cluster.asok
>>
>> same here
>>
>> _______________________________________________
>> 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
>
next prev parent reply other threads:[~2021-01-08 11:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 11:44 Frank Thommen
2021-01-05 19:01 ` Frank Thommen
2021-01-05 19:08 ` Frank Thommen
2021-01-05 19:10 ` Uwe Sauter
2021-01-05 19:24 ` Frank Thommen
2021-01-05 19:29 ` Uwe Sauter
2021-01-05 19:44 ` Frank Thommen
[not found] ` <f3ca5f88-5cbd-9807-02d7-d8f24fcbefdb@gmail.com>
2021-01-05 20:17 ` Frank Thommen
2021-01-08 10:36 ` Frank Thommen
2021-01-08 10:45 ` Uwe Sauter
2021-01-08 11:05 ` Frank Thommen
2021-01-08 11:27 ` Peter Simon
2021-01-08 11:44 ` Frank Thommen [this message]
2021-01-08 11:57 ` Peter Simon
2021-01-08 12:01 ` Frank Thommen
2021-01-16 12:26 ` Frank Thommen
[not found] ` <058f3eca-2e6f-eead-365a-4d451fa160d3@gmail.com>
2021-01-05 20:18 ` Frank Thommen
2021-01-05 19:35 ` Frank Thommen
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=8599b7ad-0ea0-b836-4492-d80b9d43cfcb@dkfz-heidelberg.de \
--to=f.thommen@dkfz-heidelberg.de \
--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