From: Piviul <piviul@riminilug.it>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] ceph
Date: Tue, 10 Jan 2023 14:29:47 +0100 [thread overview]
Message-ID: <d89b9b46-4575-12e3-fefe-4732ef79e639@riminilug.it> (raw)
In-Reply-To: <mailman.215.1673337884.458.pve-user@lists.proxmox.com>
On 1/10/23 09:04, Eneko Lacunza via pve-user wrote:
>
> I think you may have a wrong Ceph network definition in
> /etc/pve/ceph.conf, check for "public_network".
# cat /etc/pve/ceph.conf
[global]
auth_client_required = cephx
auth_cluster_required = cephx
auth_service_required = cephx
cluster_network = 192.168.254.3/24
fsid = 332d7723-d16f-443f-947d-a5ab160e4fac
mon_allow_pool_delete = true
mon_host = 192.168.70.34 192.168.70.30 192.168.70.32
osd_pool_default_min_size = 2
osd_pool_default_size = 3
public_network = 192.168.70.34/20
[client]
keyring = /etc/pve/priv/$cluster.$name.keyring
[mds]
keyring = /var/lib/ceph/mds/ceph-$id/keyring
[mds.pve01]
host = pve01
mds standby for name = pve
[mds.pve02]
host = pve02
mds_standby_for_name = pve
[mds.pve03]
host = pve03
mds_standby_for_name = pve
[mon.pve01]
public_addr = 192.168.70.30
[mon.pve02]
public_addr = 192.168.70.32
[mon.pve03]
public_addr = 192.168.70.34
> Also check what IP are listening on OSD daemons.
# netstat -tunlp | grep ceph-
tcp 0 0 192.168.254.1:6806 0.0.0.0:* LISTEN
1760/ceph-osd
tcp 0 0 192.168.70.30:6806 0.0.0.0:* LISTEN
1760/ceph-osd
tcp 0 0 192.168.254.1:6807 0.0.0.0:* LISTEN
1760/ceph-osd
tcp 0 0 192.168.70.30:6807 0.0.0.0:* LISTEN
1761/ceph-osd
tcp 0 0 192.168.254.1:6808 0.0.0.0:* LISTEN
1762/ceph-osd
tcp 0 0 192.168.70.30:6808 0.0.0.0:* LISTEN
1760/ceph-osd
tcp 0 0 192.168.254.1:6809 0.0.0.0:* LISTEN
1762/ceph-osd
tcp 0 0 192.168.70.30:6809 0.0.0.0:* LISTEN
1760/ceph-osd
tcp 0 0 192.168.254.1:6810 0.0.0.0:* LISTEN
1762/ceph-osd
tcp 0 0 192.168.70.30:6810 0.0.0.0:* LISTEN
1762/ceph-osd
tcp 0 0 192.168.254.1:6811 0.0.0.0:* LISTEN
1762/ceph-osd
tcp 0 0 192.168.70.30:6811 0.0.0.0:* LISTEN
1762/ceph-osd
tcp 0 0 192.168.254.1:6812 0.0.0.0:* LISTEN
68106/ceph-osd
tcp 0 0 192.168.70.30:6812 0.0.0.0:* LISTEN
1762/ceph-osd
tcp 0 0 192.168.254.1:6813 0.0.0.0:* LISTEN
68106/ceph-osd
tcp 0 0 192.168.70.30:6813 0.0.0.0:* LISTEN
1762/ceph-osd
tcp 0 0 192.168.254.1:6814 0.0.0.0:* LISTEN
68106/ceph-osd
tcp 0 0 192.168.70.30:6814 0.0.0.0:* LISTEN
68106/ceph-osd
tcp 0 0 192.168.254.1:6815 0.0.0.0:* LISTEN
68106/ceph-osd
tcp 0 0 192.168.70.30:6815 0.0.0.0:* LISTEN
68106/ceph-osd
tcp 0 0 192.168.70.30:6816 0.0.0.0:* LISTEN
68106/ceph-osd
tcp 0 0 192.168.70.30:6817 0.0.0.0:* LISTEN
68106/ceph-osd
tcp 0 0 192.168.70.30:3300 0.0.0.0:* LISTEN
1753/ceph-mon
tcp 0 0 192.168.70.30:6789 0.0.0.0:* LISTEN
1753/ceph-mon
tcp 0 0 192.168.254.1:6800 0.0.0.0:* LISTEN
1761/ceph-osd
tcp 0 0 192.168.70.30:6800 0.0.0.0:* LISTEN
1740/ceph-mds
tcp 0 0 192.168.254.1:6801 0.0.0.0:* LISTEN
1761/ceph-osd
tcp 0 0 192.168.70.30:6801 0.0.0.0:* LISTEN
1740/ceph-mds
tcp 0 0 192.168.254.1:6802 0.0.0.0:* LISTEN
1760/ceph-osd
tcp 0 0 192.168.70.30:6802 0.0.0.0:* LISTEN
1761/ceph-osd
tcp 0 0 192.168.254.1:6803 0.0.0.0:* LISTEN
1760/ceph-osd
tcp 0 0 192.168.70.30:6803 0.0.0.0:* LISTEN
1761/ceph-osd
tcp 0 0 192.168.254.1:6804 0.0.0.0:* LISTEN
1761/ceph-osd
tcp 0 0 192.168.70.30:6804 0.0.0.0:* LISTEN
1760/ceph-osd
tcp 0 0 192.168.254.1:6805 0.0.0.0:* LISTEN
1761/ceph-osd
tcp 0 0 192.168.70.30:6805 0.0.0.0:* LISTEN
1761/ceph-osd
I wrong something on CEPH configuration?
Piviul
next prev parent reply other threads:[~2023-01-10 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 9:14 Piviul
[not found] ` <mailman.191.1673258105.458.pve-user@lists.proxmox.com>
2023-01-09 11:47 ` Piviul
[not found] ` <mailman.203.1673265308.458.pve-user@lists.proxmox.com>
2023-01-10 7:23 ` Piviul
[not found] ` <mailman.215.1673337884.458.pve-user@lists.proxmox.com>
2023-01-10 13:29 ` Piviul [this message]
[not found] ` <mailman.232.1673430028.458.pve-user@lists.proxmox.com>
2023-01-11 11:19 ` Piviul
[not found] ` <mailman.235.1673444838.458.pve-user@lists.proxmox.com>
2023-01-11 15:51 ` Piviul
-- strict thread matches above, loose matches on Subject: below --
2021-09-08 12:46 Leandro Roggerone
2021-09-08 12:55 ` Gilberto Ferreira
2021-09-08 20:07 ` Alex K
2021-09-08 22:11 ` ic
2021-09-13 11:32 ` Leandro Roggerone
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=d89b9b46-4575-12e3-fefe-4732ef79e639@riminilug.it \
--to=piviul@riminilug.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.