delayed network interfaces and ctdb service startup

[Amitay Isaacs]

On Thu, Sep 8, 2016 at 1:49 PM, Steve French <smfrench at gmail.com> wrote:

> I am not convinced it is network related after all, may have misread
> one of the logs e.g.
>
>
> 2016/08/31 21:01:32.549360 [ 3623]: CTDB starting on node
> 2016/08/31 21:01:32.549697 [ 3623]: Recovery lock file set to "".
> Disabling recovery lock checking
> 2016/08/31 21:01:32.556948 [ 3666]: Starting CTDBD (Version
> 4.4.6-UNKNOWN) as PID: 3666
> 2016/08/31 21:01:32.557023 [ 3666]: Created PID file /run/ctdb/ctdbd.pid
> 2016/08/31 21:01:32.557040 [ 3666]: Set real-time scheduler priority
> 2016/08/31 21:01:32.557138 [ 3666]: Set runstate to INIT (1)
> 2016/08/31 21:01:32.557605 [ 3666]: Set event helper to
> "/usr/libexec/ctdb/ctdb_event_helper"
> 2016/08/31 21:01:35.951911 [ 3666]: libust[4475/4475]: Error: Timed
> out waiting for lttng-sessiond (in lttng_ust_init() at
> lttng-ust-comm.c:1532)
> 2016/09/01 02:09:10.002215 [ 3666]: No event for 18453 seconds!
> 2016/09/01 02:09:10.002240 [ 3666]: libust[4698/4698]: Error: Timed
> out waiting for lttng-sessiond (in lttng_ust_init() at
> lttng-ust-comm.c:1532)
> 2016/09/01 02:09:10.002277 [ 3666]: Event script '05.system init '
> timed out after 18454.0s, pid: 4698
> 2016/09/01 02:09:10.002463 [ 3666]: ../ctdb/server/eventscript.c:912
> eventscript for 'init' timedout. Immediately banning ourself for 300
> seconds
> 2016/09/01 02:09:10.002478 [ 3666]: ctdb exiting with error: Failed to
> run init event
>
>
Looks like system time jumped  Or was there really no event for 5+ hours?
May be we need additional dependency on time-sync.target as well as
network-online.target.

Steve, is there a reason why you are building with lttng?  Syslog not
enough?

Amitay.