Bug 522922 - Some setroubleshoot error messages
Summary: Some setroubleshoot error messages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F12Target
TreeView+ depends on / blocked
 
Reported: 2009-09-12 07:54 UTC by Nicolas Mailhot
Modified: 2010-01-19 20:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-19 20:07:29 UTC
Type: ---


Attachments (Terms of Use)

Description Nicolas Mailhot 2009-09-12 07:54:35 UTC
As logged in syslog:

Sep 12 09:44:24  setroubleshoot: [dbus.proxies.ERROR] Introspect error on :1.106:/org/fedoraproject/Setroubleshootd: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 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.

Sep 12 09:46:46  setroubleshoot: [rpc.ERROR] [delete_signature] 1001 signature not found
Sep 12 09:46:46  setroubleshoot: [rpc.ERROR] [delete_signature] 1001 signature not found
Sep 12 09:46:46  setroubleshoot: [rpc.ERROR] [delete_signature] 1001 signature not found

Comment 1 Nicolas Mailhot 2009-09-12 07:55:00 UTC
setroubleshoot-2.2.28-1.fc12.x86_64

Comment 2 Daniel Walsh 2009-09-14 15:41:40 UTC
Did you do anything to trigger this?  IE Did you try the fixit button?

Comment 3 Nicolas Mailhot 2009-09-14 17:42:29 UTC
no idea, don't even know what the fixit button is

Comment 4 Daniel Walsh 2009-09-14 19:49:11 UTC
Does setroubleshoot seem to be working for you?

Comment 5 Nicolas Mailhot 2009-09-14 20:07:41 UTC
It works right now, but I admit I had to restart it manually a few times this week

Comment 6 Daniel Walsh 2009-09-14 20:21:45 UTC
There should be no restarting, are you talking about seapplet?

The only constantly running components in Rawhide should be sedispatch which listens to audit for avc messages and seapplet which listens for setroubleshoot messages.

If an AVC arrives, audit sends a message to seapplet which sends a dbus message to setroubleshoot, dbus will start setroubleshoot if it is not running,  setroubleshoot sends a dbus message to seapplet which puts up the star.  If the user clicks on the star it will launch sealert which talks to setroubleshoot, (Starting it if it is not running).  

setroubleshoot dies 10 seconds after the sealert browser exits and any avc message arrives.

Comment 7 Nicolas Mailhot 2009-09-14 20:42:42 UTC
sealert yes

Comment 8 Nicolas Mailhot 2009-09-14 20:44:45 UTC
BTW I hit this a few hours ago

Sep 14 19:58:21  setroubleshoot: [dbus.proxies.ERROR] Introspect error on :1.106:/org/fedoraproject/Setroubleshootd: dbus.exceptions.DBusException: org.freedeskt
op.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the repl
y, the reply timeout expired, or the network connection was broken.

Sep 14 19:58:46  setroubleshoot: [dbus.ERROR] could not start dbus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the rem
ote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Comment 9 Daniel Walsh 2010-01-19 20:07:29 UTC
It seems to be working fine now.


Note You need to log in before you can comment on or make changes to this bug.