I'm using upstart 0.6.5 in an embedded system. After working great for quite a while, today initctl started failing with "initctl: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." I can invoke initctl from a shell prompt and this error message gets returned to me immediately, there doesn't seem to be a pause at all indicative of a timeout. I'm feeling like this is a problem with dbus, since this message exists in libdbus and dbus-daemon. This is consistent behavior, all invocations of initctl are failing this way. Without tearing into the dbus source code, are there any hints as to what I should be looking for? --   Marcel Kinard   import com.ibm.marcelk.Disclaimer;