On vrijdag 16 februari 2018 13:33:32 CET David Turner wrote:
> Can you send us a `ceph status` and `ceph health detail`? Something is
> still weird. Also can you query the running daemon for it's version instead
> of asking the cluster? You should also be able to find it in the logs when
> it start
Can you send us a `ceph status` and `ceph health detail`? Something is
still weird. Also can you query the running daemon for it's version instead
of asking the cluster? You should also be able to find it in the logs when
it starts.
On Fri, Feb 16, 2018, 4:24 AM Mark Schouten wrote:
> On vrijdag
On vrijdag 16 februari 2018 00:21:34 CET Gregory Farnum wrote:
> If mon.0 is not connected to the cluster, the monitor version report won’t
> update — how could it?
>
> So you need to figure out why that’s not working. A monitor that’s running
> but isn’t part of the active set is not good.
Obvio
On Fri, Feb 16, 2018 at 10:21 AM, Gregory Farnum wrote:
> If mon.0 is not connected to the cluster, the monitor version report won’t
> update — how could it?
Heh, heh. That would certainly explain that part of the mystery. Seems there are
differing version of OSD processes on the same machine a
If mon.0 is not connected to the cluster, the monitor version report won’t
update — how could it?
So you need to figure out why that’s not working. A monitor that’s running
but isn’t part of the active set is not good.
On Thu, Feb 15, 2018 at 2:47 AM Mark Schouten wrote:
> On donderdag 15 febru
The process version in memory (running) will match the version of the
binary on disk unless it has not been restarted so there is something
being misunderstood here.
Carefully check the path of the running process binary and the package
that owns that binary, the version of that package and the li
On donderdag 15 februari 2018 10:14:40 CET Burkhard Linke wrote:
> Did you verify that the ceph mon process was actually restarted? If the
> initscripts/systemd stuff has changed during the releases, the restart
> might not be able to recognize the already running process, and (maybe
> silently?) f
Hi,
On 02/15/2018 09:19 AM, Mark Schouten wrote:
On woensdag 14 februari 2018 16:20:57 CET David Turner wrote:
From the mon.0 server run `ceph --version`. If you've restarted the mon
daemon and it is still showing 0.94.5, it is most likely because that is
the version of the packages on that
On woensdag 14 februari 2018 16:20:57 CET David Turner wrote:
> From the mon.0 server run `ceph --version`. If you've restarted the mon
> daemon and it is still showing 0.94.5, it is most likely because that is
> the version of the packages on that server.
root@proxmox2:~# ceph --version
ceph ver
>From the mon.0 server run `ceph --version`. If you've restarted the mon
daemon and it is still showing 0.94.5, it is most likely because that is
the version of the packages on that server.
On Wed, Feb 14, 2018 at 10:56 AM Mark Schouten wrote:
> Hi,
>
>
>
> I have a (Proxmox) cluster with Hamme
Hi,
I have a (Proxmox) cluster with Hammer and I started thinking about different
versions of
daemons that are running. So last night I started restarting daemons on a lot
of clusters to
get all versions per cluster in sync.
There is one cluster that is giving me issues:
root@proxmox2:~# ceph
11 matches
Mail list logo
