On Fri, Feb 16, 2018 at 10:21 AM, Gregory Farnum <gfarnum@xxxxxxxxxx> 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 as well though so there may be multiple issues or points of confusion. > > 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 <mark@xxxxxxxx> wrote: >> >> 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?) fail to start the new version. >> >> >> >> Yes, I did. I also noticed the other two monitors mention that one of the >> monitors was out. >> >> >> >> -- >> >> Kerio Operator in de Cloud? https://www.kerioindecloud.nl/ >> >> Mark Schouten | Tuxis Internet Engineering >> >> KvK: 61527076 | http://www.tuxis.nl/ >> >> T: 0318 200208 | info@xxxxxxxx >> >> _______________________________________________ >> 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 > -- Cheers, Brad _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |