Yep, that was it. My concern tho is that one node with a bad clock was able to lock the whole 16 node cluster, should that be the case?
On Wed, Oct 8, 2014 at 6:48 PM, Gregory Farnum <greg@xxxxxxxxxxx> wrote:
Check your clock sync on that node. That's the usual cause of this issue.-Greg
On Wednesday, October 8, 2014, Nathan Stratton <nathan@xxxxxxxxxxxx> wrote:I have one out of 16 of my OSDs doing something odd. The logs show some sort of authentication issue. If I restart the OSD things are fine, but in a few hours it happens again and I have to restart it to get things back up.2014-10-08 06:46:46.858260 7f43f62a0700 0 auth: could not find secret_id=2212014-10-08 06:46:46.858276 7f43f62a0700 0 cephx: verify_authorizer could not get service secret for service osd secret_id=2212014-10-08 06:46:46.858302 7f43f62a0700 0 -- 10.71.1.26:6800/22284 >> 10.71.0.218:0/1002562 pipe(0x7c92800 sd=73 :6800 s=0 pgs=0 cs=0 l=1 c=0x87b44c0).accept: got bad authorizer
--
Software Engineer #42 @ http://inktank.com | http://ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
