It appears from the log that the error actually occurs prior to apache, due to some interdependency between plymouth and urandom. I think this is a dupe of plymouth bug 1646731
Setting up bluez (5.37-0ubuntu5.1) ...
insserv: warning: script 'S99runlcactivator' missing LSB tags and overrides
insserv: warning: script 'runlcactivator' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and urandom if started
insserv: loop involving service urandom at depth 4
insserv: loop involving service hwclock at depth 3
insserv: There is a loop between service plymouth and udev if started
insserv: loop involving service udev at depth 1
insserv: There is a loop at service runlcactivator if started
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
It appears from the log that the error actually occurs prior to apache, due to some interdependency between plymouth and urandom. I think this is a dupe of plymouth bug 1646731
Setting up bluez (5.37-0ubuntu5.1) ...
insserv: warning: script 'S99runlcactivator' missing LSB tags and overrides
insserv: warning: script 'runlcactivator' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and urandom if started
insserv: loop involving service urandom at depth 4
insserv: loop involving service hwclock at depth 3
insserv: There is a loop between service plymouth and udev if started
insserv: loop involving service udev at depth 1
insserv: There is a loop at service runlcactivator if started
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!