[17:51] <Renfield> I'm looking at a problem with starting a service via upstart. I'm using Ubuntu (not sure exactly which version), with, I believe upstart 0.6.3-11.
[17:52] <Renfield> The behavior leads me to believe that procps is not starting at boot. This is on a RackSpace virtual server.
[17:52] <Renfield> I'm having difficulties determining if in fact procps is starting or not, actually.
[17:53] <Renfield> If I've read documentation correctly, if I pass init="/sbin/init --verbose" on kernel boot, that should give me more information about what upstart is doing.
[17:54] <Renfield> However, in this virtual server, I don't have access to change the kernel parameters.
[17:55] <Renfield> I tried adding "exec /sbin/initctl log-priority debug" to the script stanza of /etc/init/mountall.conf, but then the server does not complete a boot up.
[17:56] <Renfield> Also, though that causes some upstart information to come out on console, it doesn't also log it anywhere, and the console access from RackSpace isn't great.