Re: another assertion failure in monitor

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

 



On 03/10/2014 10:30 PM, Pawel Veselov wrote:

Now, I'm getting this. May be any idea what can be done to straighten
this up?

This is weird. Can you please share the steps taken until this was triggered, as well as the rest of the log?

  -Joao


    -12> 2014-03-10 22:26:23.748783 7fc0397e5700  0 log [INF] : mdsmap
e1: 0/0/1 up
    -11> 2014-03-10 22:26:23.748793 7fc0397e5700 10 send_log to self
    -10> 2014-03-10 22:26:23.748795 7fc0397e5700 10  log_queue is 4
last_log 4 sent 2 num 4 unsent 2 sending 2
     -9> 2014-03-10 22:26:23.748800 7fc0397e5700 10  will send
2014-03-10 22:26:23.715607 mon.0 10.16.20.11:6789/0
<http://10.16.20.11:6789/0> 2 : [INF] mon.c@0 won leader election with
quorum 0,1
     -8> 2014-03-10 22:26:23.748809 7fc0397e5700 10  will send
2014-03-10 22:26:23.748677 mon.0 10.16.20.11:6789/0
<http://10.16.20.11:6789/0> 3 : [INF] pgmap v1: 0 pgs: ; 0 bytes data, 0
kB used, 0 kB / 0 kB avail
     -7> 2014-03-10 22:26:23.748817 7fc0397e5700  1 --
10.16.20.11:6789/0 <http://10.16.20.11:6789/0> --> mon.0
10.16.20.11:6789/0 <http://10.16.20.11:6789/0> -- log(2 entries) v1 --
?+0 0x25f21c0
     -6> 2014-03-10 22:26:23.749128 7fc0397e5700  5
mon.c@0(leader).paxos(paxos active c 1..2) queue_proposal bl 1200 bytes;
ctx = 0x2568240
     -5> 2014-03-10 22:26:23.754248 7fc0397e5700  1 --
10.16.20.11:6789/0 <http://10.16.20.11:6789/0> --> mon.1
10.16.43.12:6789/0 <http://10.16.43.12:6789/0> -- paxos(begin lc 2 fc 0
pn 100 opn 0) v3 -- ?+0 0x26b2300
     -4> 2014-03-10 22:26:23.754743 7fc0397e5700  5
mon.c@0(leader).paxos(paxos updating c 1..2) queue_proposal bl 449
bytes; ctx = 0x2568230
     -3> 2014-03-10 22:26:23.754761 7fc0397e5700  5
mon.c@0(leader).paxos(paxos updating c 1..2) propose_new_value not
active; proposal queued
     -2> 2014-03-10 22:26:23.754838 7fc0397e5700  5
mon.c@0(leader).paxos(paxos updating c 1..2) queue_proposal bl 471
bytes; ctx = 0x2568290
     -1> 2014-03-10 22:26:23.754853 7fc0397e5700  5
mon.c@0(leader).paxos(paxos updating c 1..2) propose_new_value not
active; proposal queued
      0> 2014-03-10 22:26:23.757166 7fc0397e5700 -1 mon/AuthMonitor.cc:
In function 'virtual void AuthMonitor::create_initial()' thread
7fc0397e5700 time 2014-03-10 22:26:23.755442
mon/AuthMonitor.cc: 101: FAILED assert(ret == 0)

  ceph version 0.72.2 (a913ded2ff138aefb8cb84d347d72164099cfd60)
  1: (AuthMonitor::create_initial()+0x4d8) [0x637bb8]
  2: (PaxosService::_active()+0x51b) [0x594fcb]
  3: (Context::complete(int)+0x9) [0x565499]
  4: (finish_contexts(CephContext*, std::list<Context*,
std::allocator<Context*> >&, int)+0x95) [0x5698b5]
  5: (Paxos::handle_accept(MMonPaxos*)+0x885) [0x589595]
  6: (Paxos::dispatch(PaxosServiceMessage*)+0x28b) [0x58d66b]
  7: (Monitor::dispatch(MonSession*, Message*, bool)+0x4f0) [0x563620]
  8: (Monitor::_ms_dispatch(Message*)+0x1fb) [0x5639fb]
  9: (Monitor::ms_dispatch(Message*)+0x32) [0x57f212]
  10: (DispatchQueue::entry()+0x582) [0x7de6c2]
  11: (DispatchQueue::DispatchThread::entry()+0xd) [0x7d994d]
  12: (()+0x7ddb) [0x7fc03e736ddb]
  13: (clone()+0x6d) [0x7fc03d46ca1d]
  NOTE: a copy of the executable, or `objdump -rdS <executable>` is
needed to interpret this.



_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



--
Joao Eduardo Luis
Software Engineer | http://inktank.com | http://ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




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


  Powered by Linux