On 04/15/2014 04:41 PM, Jonathan Gowar wrote:
On Tue, 2014-04-15 at 15:47 +0100, Joao Eduardo Luis wrote:
Well, logs would be nice.
Set 'debug mon = 10' and 'debug ms = 1' on the monitor, rerun it, share
the log. That might be helpful to diagnose the problem.
-Joao
Thanks, Joao.
Seems to be a problem connecting to the down monitor.
http://pastebin.com/C9DTrJgi
The log itself appears to be only the output from the 'ceph' tool.
If you go through the monitor's troubleshooting page, you'll find out
that there's two ways to inject debug options into a running monitor:
one for when the monitor belongs to the quorum, another for when the
monitor does not belong to the quorum. You have that monitor marked as
'down' and not part of the quorum, and yet you are using the format
intended for when the monitor does belong to the quorum.
Instead of using 'ceph tell mon.ID ...', you should instead be using
'ceph daemon mon.ID ...', which should be run on the server where said
monitor is running.
If that fails, you should set the debug options on the monitor's
ceph.conf and restart the daemon.
You are getting those errors, likely, because your monitor will not
accept mon commands (such as the one to obtain mon command descriptions)
unless it belongs to the quorum.
You should check whether the server is blocking/dropping connections to
that monitor. It may be a firewall thing, it may not. If you're
running a version with such support, you may be able to know something
about the monitor by running 'ceph ping mon.ID'; otherwise, you should
rely on the admin socket (via 'ceph daemon') and/or logs.
-Joao
--
Joao Eduardo Luis
Software Engineer | http://inktank.com | http://ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
