|
Hello,
Thanks for quick response, as it seems to be related to when I tried to enable the dashboard (if I’m correct) is their a way I can try and disable the dashboard via admin socket e.t.c or another work around till version is released with the patch?
Thanks,
Ashley
Sent from my iPhone
On Tue, Jul 18, 2017 at 12:43 PM, Ashley Merrick <ashley@xxxxxxxxxxxxxx> wrote:
Hello,
I just updated to latest CEPH Lum RC, all was working fine with my 3
Mon’s/Mgr’s online, went to enable the Dashboard with the command : ceph mgr
module enable dashboard
Now only one of the 3 MON’s will run, every time a try and start a failed
mon it will either fail or stay online and the running mon fail.
This is presumably a crash in the "log last" command that the
dashboard sends to the monitor on startup to load its log history.
It could be the same one that's fixed by
https://github.com/ceph/ceph/pull/16376/files
John
The following is showed in the error log:
2017-07-18 12:07:19.611915 has v0 lc 44232717
0> 2017-07-18 12:07:14.687001 7f7c9f2fc700 -1 *** Caught signal
(Segmentation fault) **
in thread 7f7c9f2fc700 thread_name:ms_dispatch
ceph version 12.1.1 (f3e663a190bf2ed12c7e3cda288b9a159572c800) luminous (rc)
1: (()+0x87494c) [0x55ae716da94c]
2: (()+0xf890) [0x7f7cab700890]
3:
(LogMonitor::preprocess_command(boost::intrusive_ptr<MonOpRequest>)+0x9af)
[0x55ae7124e3ef]
4: (LogMonitor::preprocess_query(boost::intrusive_ptr<MonOpRequest>)+0x2de)
[0x55ae7124ed9e]
5: (PaxosService::dispatch(boost::intrusive_ptr<MonOpRequest>)+0x7e8)
[0x55ae71335f58]
6: (Monitor::handle_command(boost::intrusive_ptr<MonOpRequest>)+0x294f)
[0x55ae7120bb7f]
7: (Monitor::dispatch_op(boost::intrusive_ptr<MonOpRequest>)+0x8b9)
[0x55ae71212099]
8: (Monitor::_ms_dispatch(Message*)+0xd99) [0x55ae71213999]
9: (Monitor::ms_dispatch(Message*)+0x23) [0x55ae7123ad43]
10: (DispatchQueue::entry()+0x7ca) [0x55ae71683fda]
11: (DispatchQueue::DispatchThread::entry()+0xd) [0x55ae714e554d]
12: (()+0x8064) [0x7f7cab6f9064]
13: (clone()+0x6d) [0x7f7ca8c0162d]
NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to
interpret this.
Thanks,
Ashley Merrick
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
|
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
