Re: [ceph-users] ceph/systemd startup bug (was Re: Some OSDs are down after Server reboot)

On Fri, Sep 29, 2017 at 8:58 PM, Matthew Vernon wrote: > Hi, > > On 29/09/17 01:00, Brad Hubbard wrote: >> This looks similar to >> https://bugzilla.redhat.com/show_bug.cgi?id=1458007 or one of the >> bugs/trackers attached to that. > > Yes, although increasing the timeout

Re: [ceph-users] ceph/systemd startup bug (was Re: Some OSDs are down after Server reboot)

Hi, On 29/09/17 01:00, Brad Hubbard wrote: > This looks similar to > https://bugzilla.redhat.com/show_bug.cgi?id=1458007 or one of the > bugs/trackers attached to that. Yes, although increasing the timeout still leaves the issue that if the timeout fires you don't get anything resembling a

Re: [ceph-users] ceph/systemd startup bug (was Re: Some OSDs are down after Server reboot)

This looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=1458007 or one of the bugs/trackers attached to that. On Thu, Sep 28, 2017 at 11:14 PM, Sean Purdy wrote: > On Thu, 28 Sep 2017, Matthew Vernon said: >> Hi, >> >> TL;DR - the timeout setting in

Re: [ceph-users] ceph/systemd startup bug (was Re: Some OSDs are down after Server reboot)

On Thu, 28 Sep 2017, Matthew Vernon said: > Hi, > > TL;DR - the timeout setting in ceph-disk@.service is (far) too small - it > needs increasing and/or removing entirely. Should I copy this to ceph-devel? Just a note. Looks like debian stretch luminous packages have a 10_000 second timeout:

[ceph-users] ceph/systemd startup bug (was Re: Some OSDs are down after Server reboot)

Hi, TL;DR - the timeout setting in ceph-disk@.service is (far) too small - it needs increasing and/or removing entirely. Should I copy this to ceph-devel? On 15/09/17 16:48, Matthew Vernon wrote: On 14/09/17 16:26, Götz Reinicke wrote: After that, 10 OSDs did not came up as the others. The