Thanks for your warmhearted response!

I do not find out the root reason which causes 'client did not provide 
supported auth type'.
I just rebuild keys and it's ok.




------------------ ???????? ------------------
??????: "Goncalo Borges";<[email protected]>;
????????: 2016??6??28??(??????) ????1:18
??????: "????"<[email protected]>; 
"ceph-users"<[email protected]>; 

????: Re: [ceph-users] client did not provide supported auth type



                   
Hi... 
     
     
Just to clarify, you could have just one but if that one is       problematic 
than your cluster stops working. It is always better       to have more than 
one and in odd numbers : 3, 5, ...
     
     Regarding your specific problem, I am guessing it is related to keys     
and permissions because of the  'client         did not provide supported auth 
type' message
     
     Check the status of your client admin key with 'ceph auth list' and     
their permissions. Should be something as
     client.admin
           key: XXXXXXXXXX
           auid: 0
           caps: [mon] allow *
           caps: [osd] allow *
          Cheers
     G
     
     
     On 06/28/2016 01:40 PM, Goncalo Borges       wrote:
     
                   
Hi XiuCai
       
Shouldn't you have, at least, 2 mons?
       
Cheers
       
G.
       
       
       On 06/28/2016 01:12 PM, ???? wrote:
       
                           Hi,
           
           
           ther are 1 mon and 7 osds in my cluster now.
           but it seems something wrong, because `rbd -p test reate             
pet --size 1024` could not return.
           and status is always below:
           
           
                            cluster                   
41f3f57f-0ca8-4dac-ba10-9359043ae21a
                  health HEALTH_WARN
                         256 pgs degraded
                         256 pgs stuck                   degraded
                         256 pgs stuck                   inactive
                         256 pgs stuck                   unclean
                         256 pgs stuck                   undersized
                         256 pgs undersized
                  monmap e1: 1 mons at {a=192.168.1.101:6789/0}
                         election epoch 2,                   quorum 0 a
                  osdmap e32: 7 osds: 7 up,                   7 in
                   pgmap v69: 256 pgs, 1                   pools, 0 bytes data, 
0 objects
                         231 MB used, 1442                   GB / 1442 GB avail
                              256                   undersized+degraded+peered
           
           
           
           i checked monitor's log:
           
           
           1 mon.a@0(leader).log v2235                 check_sub sending 
message to client.?                 192.168.1.101:0/2395453635 with 0 entries 
(version 2235)
           1 mon.a@0(leader).auth v27                 client did not provide 
supported auth type
           1 mon.a@0(leader).auth v27                 client did not provide 
supported auth type
         
         
             
         what is the meaning of v2235 & v27 here ?
         how to solve this problem ?
         
         
         Regards,
         XiuCai.
         
                  
         _______________________________________________ ceph-users mailing 
list [email protected] 
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com               
       --  Goncalo Borges Research Computing ARC Centre of Excellence for 
Particle Physics at the Terascale School of Physics A28 | University of Sydney, 
NSW  2006 T: +61 2 93511937          
     --  Goncalo Borges Research Computing ARC Centre of Excellence for 
Particle Physics at the Terascale School of Physics A28 | University of Sydney, 
NSW  2006 T: +61 2 93511937
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to