28 Feb
2024
28 Feb
'24
12:05 p.m.
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
28 Feb
28 Feb
1:06 p.m.
Hi,
I’d double check that the 3300 port is accessible (e.g. using telnet, which can be
installed as an optional Windows feature). Make sure that it’s using the default port and
not a custom one, also be aware the v1 protocol uses 6789 by default.
Increasing the messenger log level to 10 might also be useful: debug ms = 10.
Regards,
Lucian
On 28 Feb 2024, at 11:05, duluxoz
<duluxoz(a)gmail.com> wrote:
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(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io
9 Mar
9 Mar
6:32 a.m.
Thanks Lucian, your advice helped uncover the root cause of my issue :-)
(Sorry about the delay in the reply)
On 28/02/2024 21:06, Lucian Petrut wrote:
> Hi,
>
> I’d double check that the 3300 port is accessible (e.g. using telnet, which can be
installed as an optional Windows feature). Make sure that it’s using the default port and
not a custom one, also be aware the v1 protocol uses 6789 by default.
>
> Increasing the messenger log level to 10 might also be useful: debug ms = 10.
>
> Regards,
> Lucian
>
>> On 28 Feb 2024, at 11:05, duluxoz <duluxoz(a)gmail.com> wrote:
>>
>> 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(a)ceph.io
>> To unsubscribe send an email to ceph-users-leave(a)ceph.io
28 Feb
28 Feb
5:03 p.m.
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(a)gmail.com>
Sent: Wednesday, February 28, 2024 4:05 AM
To: ceph-users(a)ceph.io
Subject: [ceph-users] 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(a)ceph.io To unsubscribe send an email to
ceph-users-leave(a)ceph.io
9 Mar
9 Mar
6:31 a.m.
Thanks Robert (sorry about the delay in replying) :-)
On 29/02/2024 01:03, Robert W. Eckert wrote:
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(a)gmail.com>
Sent: Wednesday, February 28, 2024 4:05 AM
To:ceph-users@ceph.io
Subject: [ceph-users] 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(a)ceph.io To unsubscribe send an email
toceph-users-leave(a)ceph.io
--
Peregrine IT Signature
*Matthew J BLACK*
M.Inf.Tech.(Data Comms)
MBA
B.Sc.
MACS (Snr), CP, IP3P
When you want it done /right/ ‒ the first time!
Phone: +61 4 0411 0089
Email: matthew(a)peregrineit.net <mailto:matthew@peregrineit.net>
Web: www.peregrineit.net <http://www.peregrineit.net>
View Matthew J BLACK's profile on LinkedIn
<http://au.linkedin.com/in/mjblack>
This Email is intended only for the addressee. Its use is limited to
that intended by the author at the time and it is not to be distributed
without the author’s consent. You must not use or disclose the contents
of this Email, or add the sender’s Email address to any database, list
or mailing list unless you are expressly authorised to do so. Unless
otherwise stated, Peregrine I.T. Pty Ltd accepts no liability for the
contents of this Email except where subsequently confirmed in
writing. The opinions expressed in this Email are those of the author
and do not necessarily represent the views of Peregrine I.T. Pty
Ltd. This Email is confidential and may be subject to a claim of legal
privilege.
If you have received this Email in error, please notify the author and
delete this message immediately.
71
days inactive
81
days old
4 comments
3 participants
participants (3)
-
duluxoz -
Lucian Petrut -
Robert W. Eckert