On 10/18/2017 10:38 AM, Nico Schottelius wrote:
Hello Joao,
thanks for coming back!
I copied the log of the crashing monitor to http://www.nico.schottelius.org/cephmonlog-2017-10-08-v2.xz
Can I somehow get access to the logs of the other monitors, without
restarting them?
If you mean increasing the debug levels, then yes; use `inject args`:
ceph tell mon.<id> injectargs '--debug-mon 10 --debug-ms 1
--debug-paxos 10'
All existing logs should be in /var/log/ceph/
-Joao
I would like to not stop them, as currently we are running with 2/3
monitors and adding a new one seems not easily be possible, because
adding a new one means losing the quorum and then being unable to remove
the new one, because the quorum is lost with 2/4 nodes.
(this is what actually happened about a week ago in our cluster)
Best,
Nico
Joao Eduardo Luis <joao@xxxxxxx> writes:
Hi Nico,
I'm sorry I forgot about your issue. Crazy few weeks.
I checked the log you initially sent to the list, but it only contains
the log from one of the monitors, and it's from the one
synchronizing. This monitor is not stuck however - synchronizing is
progressing, albeit slowly.
Can you please share the logs of the other monitors, especially of
those crashing?
-Joao
On 10/18/2017 06:58 AM, Nico Schottelius wrote:
Hello everyone,
is there any solution in sight for this problem? Currently our cluster
is stuck with a 2 monitor configuration, as everytime we restart the one
server2, it crashes after some minutes (and in between the cluster is stuck).
Should we consider downgrading to kraken to fix that problem?
Best,
Nico
--
Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
--
Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
