pveceph got timeout creating pool

[GambitK]

I'm trying to configure a cephfs pool using pveceph and I'm getting "got timeout" on the command prompt or in the web UI. The thing is that the pool is shown after in the web UI.

I'm getting the same when I create the Cephf FS after the first pool "ceph_data" is created.

ceph status

  cluster:
    id:     48ec00f9-f72a-45bc-afb3-63cb8f4ca2f4
    health: HEALTH_WARN
            clock skew detected on mon.proxmoxvm02, mon.proxmoxvm03
 
  services:
    mon: 3 daemons, quorum proxmoxvm01,proxmoxvm02,proxmoxvm03 (age 53m)
    mgr: proxmoxvm02(active, since 53m), standbys: proxmoxvm03, proxmoxvm01
    osd: 3 osds: 3 up (since 53m), 3 in (since 4h)
 
  data:
    pools:   2 pools, 0 pgs
    objects: 0 objects, 0 B
    usage:   3.0 GiB used, 90 GiB / 93 GiB avail
    pgs:

I can telnet on port 6789 between all nodes and can create pools directly with ceph commands.
Maybe is something proxmox related?

Here is my proxmox cluster status:

pvecm status
Quorum information
------------------
Date:             Wed Nov 20 08:28:09 2019
Quorum provider:  corosync_votequorum
Nodes:            3
Node ID:          0x00000001
Ring ID:          1.4c
Quorate:          Yes

Votequorum information
----------------------
Expected votes:   3
Highest expected: 3
Total votes:      3
Quorum:           2 
Flags:            Quorate

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 10.0.0.11 (local)
0x00000002          1 10.0.0.12
0x00000003          1 10.0.0.13

 

[Alwin]

I'm trying to configure a cephfs pool using pveceph and I'm getting "got timeout" on the command prompt or in the web UI.

What is the message when you are using pveceph? What does the journal/syslog say?

clock skew detected on mon.proxmoxvm02, mon.proxmoxvm03

First, please check that all nodes in the cluster do have the same time. Best configure a local NTP server as source (see timesyncd).

I can telnet on port 6789 between all nodes and can create pools directly with ceph commands.

pveceph uses Ceph tools underneath. Possibly that the ceph tooling is connecting to a different server.

Here is my proxmox cluster status:

This is the status of corosync and not relevant for Ceph.