> Op 14 mei 2016 om 12:40 schreef Wido den Hollander :
>
>
>
> > Op 14 mei 2016 om 11:53 schreef Ruben Kerkhof :
> >
> >
> > On Thu, May 12, 2016 at 2:16 PM, Wido den Hollander wrote:
> > > Hi,
> >
> > Hi Wido,
> >
> > >
> > > I am setting up a Jewel cluster in VMs with Ubuntu 16.04.
> > >
On Sat, May 14, 2016 at 12:40 PM, Wido den Hollander wrote:
>
>> Op 14 mei 2016 om 11:53 schreef Ruben Kerkhof :
>>
>>
>> On Thu, May 12, 2016 at 2:16 PM, Wido den Hollander wrote:
>> > Hi,
>>
>> Hi Wido,
>>
>> >
>> > I am setting up a Jewel cluster in VMs with Ubuntu 16.04.
>> >
>> > ceph versio
> Op 14 mei 2016 om 11:53 schreef Ruben Kerkhof :
>
>
> On Thu, May 12, 2016 at 2:16 PM, Wido den Hollander wrote:
> > Hi,
>
> Hi Wido,
>
> >
> > I am setting up a Jewel cluster in VMs with Ubuntu 16.04.
> >
> > ceph version 10.2.0 (3a9fba20ec743699b69bd0181dd6c54dc01c64b9)
> >
> > After a re
On Thu, May 12, 2016 at 2:16 PM, Wido den Hollander wrote:
> Hi,
Hi Wido,
>
> I am setting up a Jewel cluster in VMs with Ubuntu 16.04.
>
> ceph version 10.2.0 (3a9fba20ec743699b69bd0181dd6c54dc01c64b9)
>
> After a reboot the Ceph Monitors don't start and I have to do so manually.
I had a simil
> Op 13 mei 2016 om 14:56 schreef Jan Schermer :
>
>
> Can you check that the dependencies have started? Anything about those in the
> logs?
>
> network-online.target local-fs.target ceph-create-keys@%i.service
>
May 13 16:59:15 alpha systemd[1]: Reached target Local File Systems (Pre).
May
Can you check that the dependencies have started? Anything about those in the
logs?
network-online.target local-fs.target ceph-create-keys@%i.service
Jan
> On 13 May 2016, at 14:30, Sage Weil wrote:
>
> This is starting to sound like a xenial systemd issue to me. Maybe poke
> the canonical
This is starting to sound like a xenial systemd issue to me. Maybe poke
the canonical folks?
You might edit the unit file and make it touch something in /tmp instead
of starting Ceph just to rule out ceph...
sage
On Fri, 13 May 2016, Wido den Hollander wrote:
> No luck either. After a reboo
No luck either. After a reboot only the Ceph OSD starts, but the monitor not.
I have checked:
- service is enabled
- tried to re-enable the service
- check the MON logs to see if it was started, it wasn't
- systemd log to see if it wants to start the MON, it doesn't
My systemd-foo isn't that good
Btw try replacing
WantedBy=ceph-mon.target
With: WantedBy=default.target
then systemctl daemon-reload.
See if that does the trick
I only messed with systemctl to have my own services start, I still hope it
goes away eventually... :P
Jan
> On 12 May 2016, at 15:01, Wido den Hollander wrote:
So systemctl is-enabled ceph-mon.target says "enabled" as well?
I think it should start then, or at least try
Jan
> On 12 May 2016, at 15:14, Wido den Hollander wrote:
>
>
>> Op 12 mei 2016 om 15:12 schreef Jan Schermer :
>>
>>
>> What about systemctl is-enabled ceph-mon.target?
>>
>
> Ju
> Op 12 mei 2016 om 15:12 schreef Jan Schermer :
>
>
> What about systemctl is-enabled ceph-mon.target?
>
Just tried that, no luck either. There is simply no trace of the monitors
trying to start on boot.
> Jan
>
>
>
> > On 12 May 2016, at 15:01, Wido den Hollander wrote:
> >
> >
> > T
What about systemctl is-enabled ceph-mon.target?
Jan
> On 12 May 2016, at 15:01, Wido den Hollander wrote:
>
>
> To also answer Sage's question: No, this is a fresh Jewel install in a few
> test VMs. This system was not upgraded.
>
> It was installed 2 hours ago.
>
>> Op 12 mei 2016 om 14
To also answer Sage's question: No, this is a fresh Jewel install in a few test
VMs. This system was not upgraded.
It was installed 2 hours ago.
> Op 12 mei 2016 om 14:51 schreef Jan Schermer :
>
>
> Can you post the contents of ceph-mon@.service file?
>
Yes, here you go:
root@charlie:~# c
Can you post the contents of ceph-mon@.service file?
what does
systemctl is-enabled ceph-mon@charlie
say?
However, this looks like it was just started at a bad moment and died - nothing
in logs?
Jan
> On 12 May 2016, at 14:44, Sage Weil wrote:
>
> On Thu, 12 May 2016, Wido den Hollander wro
On Thu, 12 May 2016, Wido den Hollander wrote:
> Hi,
>
> I am setting up a Jewel cluster in VMs with Ubuntu 16.04.
>
> ceph version 10.2.0 (3a9fba20ec743699b69bd0181dd6c54dc01c64b9)
>
> After a reboot the Ceph Monitors don't start and I have to do so manually.
>
> Three machines, alpha, bravo an
Hi,
I am setting up a Jewel cluster in VMs with Ubuntu 16.04.
ceph version 10.2.0 (3a9fba20ec743699b69bd0181dd6c54dc01c64b9)
After a reboot the Ceph Monitors don't start and I have to do so manually.
Three machines, alpha, bravo and charlie all have the same problem.
root@charlie:~# systemctl
16 matches
Mail list logo
