Re: CephFS On Windows 10

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have it working on my machines-  the global configuration for me looks like
[global]
        fsid = fe3a7cb0-69ca-11eb-8d45-c86000d08867
        mon_host = [v2:192.168.2.142:3300/0,v1:192.168.2.142:6789/0] [v2:192.168.2.141:3300/0,v1:192.168.2.141:6789/0] [v2:192.168.2.199:3300/0,v1:192.168.2.199:6789/0]
        auth_cluster_required = cephx
        auth_service_required = cephx
        auth_client_required = cephx

The important thing for me was to add the FSID, and the auth sections

Also note the port is the 6789 not 3300.



-----Original Message-----
From: duluxoz <duluxoz@xxxxxxxxx> 
Sent: Wednesday, February 28, 2024 4:05 AM
To: ceph-users@xxxxxxx
Subject:  CephFS On Windows 10

Hi All,

  I'm looking for some pointers/help as to why I can't get my Win10 PC to connect to our Ceph Cluster's CephFS Service. Details are as follows:

Ceph Cluster:

- IP Addresses: 192.168.1.10, 192.168.1.11, 192.168.1.12

- Each node above is a monitor & an MDS

- Firewall Ports: open (ie 3300, etc)

- CephFS System Name: my_cephfs

- Log files: nothing jumps out at me

Windows PC:

- Keyring file created and findable: ceph.client.me.keyring

- dokany installed

- ceph-for-windows installed

- Can ping all three ceph nodes

- Connection command: ceph-dokan -l v -o -id me --debug --client_fs my_cephfs -c C:\ProgramData\Ceph\ceph.conf

Ceph.conf contents:

~~~

[global]
   mon_host = 192.168.1.10, 192.168.1.11, 192.168.1.12
   log to stderr = true
   log to syslog = true
   run dir = C:/ProgramData/ceph
   crash dir = C:/logs/ceph
   debug client = 2
[client]
   keyring = C:/ProgramData/ceph/ceph.client.me.keyring
   log file = C:/logs/ceph/$name.$pid.log
   admin socket = C:/ProgramData/ceph/$name.$pid.asok
~~~

Windows Logfile contents (ieC:/logs/ceph/client.me.NNNN.log):

~~~

2024-02-28T18:26:45.201+1100 1  0 monclient(hunting): authenticate timed out after 300
2024-02-28T18:31:45.203+1100 1  0 monclient(hunting): authenticate timed out after 300
2024-02-28T18:36:45.205+1100 1  0 monclient(hunting): authenticate timed out after 300

~~~

Additional info from Windows CLI:

~~~

failed to fetch mon config (--no-mon-config to skip)

~~~

So I've gone through the doco and done some Google-foo and I can't work out *why* I'm getting a failure; why I'm getting the authentication failure. I know it'll be something simple, something staring me in the face, but I'm at the point where I can't see the forest for the trees - please help.

Any help greatly appreciated

Thanks in advance

Cheers

Dulux-Oz
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux