PDA

View Full Version : [SOLVED] setroubleshoot: unrecognized service


jfr8595
31st August 2010, 08:05 PM
Upon reboot my F14 vm everything appeared "normal".

SELinux message flashes in upper right corner for a moment, I ignore it. Shortly thereafter I go to Applications > System Tools > SELinux troubleshooter, icon spins for normal amount of time, then nothing.

System > Administration > Services, icon spins for normal amount of time, then nothing.

OK, I start a terminal session, & su - it:

[root@bonk log]# sestatus
SELinux status: enabled
SELinuxfs mount: /selinux
Current mode: permissive
Mode from config file: permissive
Policy version: 24
Policy from config file: targeted

[root@bonk log]# service setroubleshoot status
setroubleshoot: unrecognized service
[root@bonk log]# service auditd status
auditd (pid 1230) is running...

ntsysv shows no setroubleshoot

[root@bonk log]# yum info setroubleshoot
Loaded plugins: auto-update-debuginfo, langpacks, presto, refresh-packagekit
Adding en_US to language list
Found 12 installed debuginfo package(s)
Enabling updates-testing-debuginfo: Fedora 14 - x86_64 - Test Updates Debug
Enabling fedora-debuginfo: Fedora 14 - x86_64 - Debug
Installed Packages
Name : setroubleshoot
Arch : x86_64
Version : 2.2.95
Release : 1.fc14
Size : 295 k
Repo : installed
From repo : updates-testing
Summary : Helps troubleshoot SELinux problems
URL : https://fedorahosted.org/setroubleshoot
License : GPLv2+
Description : setroubleshoot gui. Application that allows you to view
: setroubleshoot-server messages.
: Provides tools to help diagnose SELinux problems. When AVC
: messages are generated an alert can be generated that will give
: information about the problem and help track its resolution.
: Alerts can be configured to user preference. The same tools can be
: run on existing log files.

cat messages |grep setroubleshoot

Aug 31 13:17:41 bonk setroubleshoot: [dbus.ERROR] could not start dbus: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/sealert exited with status 127
Aug 31 13:21:40 bonk setroubleshoot: [dbus.ERROR] could not start dbus: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/sealert exited with status 127
Aug 31 13:30:28 bonk setroubleshoot: [dbus.ERROR] could not start dbus: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/sealert exited with status 127
Aug 31 13:30:51 bonk setroubleshoot: [dbus.ERROR] could not start dbus: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/sealert exited with status 127

Any ideas what I should do here?

Did file update to Red Hat Bugzilla – Bug 628392

THANKS in advance!

AdamW
31st August 2010, 09:56 PM
why do you assume setroubleshoot should run as a service? afaict it doesn't ship as either a sysv or systemd service in the setroubleshoot package, so it seems like it isn't supposed to.

What happens if you go to a console and run 'sealert -b'?

(It seems to me like there's a dbus interaction issue with sealert, because when I try and run it it fails claiming dbus isn't running, which it clearly is).

jfr8595
31st August 2010, 10:04 PM

Got me, I thought it ran as a service on my CentOS 5.5 systems but in answer to your F14 question:

[root@bonk log]# sealert -b
[root@bonk log]#

[root@bonk log]# sealert -bv
2010-09-01 01:32:54,086 [dbus.ERROR] could not start dbus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.

THANKS!

jfr8595
1st September 2010, 09:55 PM
I decided to scratch this install and re-install. Things seem to be fine now.

In my opinion SELinux needs to be set to permissive for at least your first yum update. Subsequent SELinux policy is fixed I think but the one that comes on the non-updated alpha stops some things from being written properly during yum update and that causes a downstream mess...

GoinEasy9
2nd September 2010, 12:37 AM
I had to empty the /home/<Username>/.setroubleshoot file to get rid of an empty AVC alert after a fresh install of the alpha RC3. This is fixed in subsequent selinux-policy versions (or was just an empty alert caused by bugs in the early alpha). So, enabling SELinux after the first update does sound like a good idea, or, using a nightly built instead of the alpha.