Upstart provides a GetAllJobs method on its D-Bus interface<br><br><div class="gmail_quote">On Thu, Oct 28, 2010 at 12:48 PM, Marcel Kinard <span dir="ltr"><<a href="mailto:marcelk@us.ibm.com">marcelk@us.ibm.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><font size="2" face="sans-serif">Found the dbus problem I had. Using strace
I saw that the dbus client (initctl) was sending an authentication request
to the dbus daemon, which the daemon rejected. The /etc/passwd file was
in a bad state, which is why the daemon was rejecting.</font>
<br>
<br><font size="2" face="sans-serif">Another question: is there any API I
could use to programmatically get the list of upstart-managed jobs and
their state? Right now I'm doing fork/exec on initctl and parsing the output.
Wondering if there was a cleaner way. Thanks!</font>
<br><font size="2" face="sans-serif"><br>
-- <br>
Marcel Kinard<br>
import com.ibm.marcelk.Disclaimer;<br>
</font><font size="1" color="#800080" face="sans-serif">----- Forwarded by
Marcel Kinard/Raleigh/IBM on 10/28/2010 12:43 PM -----</font>
<br>
<table width="100%">
<tbody><tr valign="top">
<td><font size="1" color="#5f5f5f" face="sans-serif">From:</font>
</td><td><font size="1" face="sans-serif">Marcel Kinard/Raleigh/IBM@IBMUS</font>
</td></tr><tr valign="top">
<td><font size="1" color="#5f5f5f" face="sans-serif">To:</font>
</td><td><font size="1" face="sans-serif"><a href="mailto:upstart-devel@lists.ubuntu.com" target="_blank">upstart-devel@lists.ubuntu.com</a></font>
</td></tr><tr valign="top">
<td><font size="1" color="#5f5f5f" face="sans-serif">Date:</font>
</td><td><font size="1" face="sans-serif">10/26/2010 11:37 PM</font>
</td></tr><tr valign="top">
<td><font size="1" color="#5f5f5f" face="sans-serif">Subject:</font>
</td><td><font size="1" face="sans-serif">dbus problem?</font>
</td></tr><tr valign="top">
<td><font size="1" color="#5f5f5f" face="sans-serif">Sent by:</font>
</td><td><font size="1" face="sans-serif"><a href="mailto:upstart-devel-bounces@lists.ubuntu.com" target="_blank">upstart-devel-bounces@lists.ubuntu.com</a></font></td></tr></tbody></table>
<br>
<hr noshade>
<br>
<br>
<br><font size="2" face="sans-serif">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.</font><font size="3">
<br>
</font><font size="2" face="sans-serif"><br>
Without tearing into the dbus source code, are there any hints as to what
I should be looking for?</font><font size="3"> <br>
</font><font size="2" face="sans-serif"><br>
<br>
-- <br>
Marcel Kinard<br>
import com.ibm.marcelk.Disclaimer;</font><tt><font size="2">-- <br>
upstart-devel mailing list<br>
<a href="mailto:upstart-devel@lists.ubuntu.com" target="_blank">upstart-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: </font></tt><a href="https://lists.ubuntu.com/mailman/listinfo/upstart-devel" target="_blank"><tt><font size="2">https://lists.ubuntu.com/mailman/listinfo/upstart-devel</font></tt></a><tt><font size="2"><br>
</font></tt>
<br><br>--<br>
upstart-devel mailing list<br>
<a href="mailto:upstart-devel@lists.ubuntu.com">upstart-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/upstart-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/upstart-devel</a><br>
<br></blockquote></div><br>