Comment 287 for bug 554172
Revision history for this message
| Mike Bianchi (mbianchi-foveal) wrote Re: <OK> [Bug 554172] Re: system services using "console output" not starting at boot | #287 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On Wed, Jan 12, 2011 at 03:14:41PM -0000, John Edwards wrote:
> David Haskins, could you run the 'runlevel' command to check if this is
> related to this particular bug, or if it is another problem?
A better approach might be to put logging into /etc/init.d/apache2
and figure out:
If it is actually called.
And, if it is, why does it fail.
I freely admit my prejudices on the this type of problem.
/bin/init under upstart does not guarantee the order of execution of the
startup scripts. In fact it almost forces them to be random if you have a
multi-core processor. (Again this is my prejudice, based on my prior problems
with upstart).
I strongly suspect that there is some service that /etc/init.d/apache2
depends upon that is sometimes completely started when it runs, and
sometimes is not. Since upstart runs /etc/init/* services
depending on the "start on" prerequisite "event" list being _exactly_ right,
if I didn't know about one or more, or got the "start on" stanza slightly wrong
I saw unreliable service starts.
My two cents: I think it would be good to have access to an old fashion,
one-step-at-a-time boot sequence (as an option).
I would gladly give up boot speed for boot sequence certainty. I do not
see a way to do that with upstart. Boot sequence certainty was easy to
accomplish when everything was started by numbered filenames under
/etc/init.d .
I commented on the lack of upstart event documentation in other bug reports:
https:/
https:/
https:/