Bug 451427
| Summary: | Startup of setroubleshootd fails and connection to it denied | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stefan Schulze Frielinghaus <fedoraproject> |
| Component: | setroubleshoot | Assignee: | John Dennis <jdennis> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | powerpc | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 2.0.8-2.fc9 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-06-17 19:20:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I'm pretty sure this is a dup of bug 446661 which only occurs on PPC. For a quick test of that theory edit /usr/lib/python2.5/site-packages/setroubleshoot/access_control.py and change SO_PEERCRED from 17 to 21 Or you could try installing 2.0.7.1 which has the bug fix, but this hasn't been pushed out yet, but you can download it from: http://koji.fedoraproject.org/koji/buildinfo?buildID=49322 setroubleshoot-2.0.7-1.fc9 has been submitted as an update for Fedora 9 Version 2.0.7-1.fc9 didn't fix the problem. But I noticed another error message.
When I manually restart the daemon the following is returned to terminal:
$ /etc/init.d/setroubleshoot restart
Stopping setroubleshootd: [ OK ]
Starting setroubleshootd: [ OK ]
$ Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/setroubleshoot/server.py", line 221, in
on_connection_state_change
self.uid, self.gid = self.access.get_credentials(self.socket_address.socket)
File "/usr/lib/python2.5/site-packages/setroubleshoot/access_control.py", line
142, in get_credentials
if family != socket.AF_UNIX:
NameError: global name 'socket' is not defined
The message in logfile is still the same.
setroubleshoot-2.0.8-1.fc9 was pushed to updates-testing this morning to correct this (a capitalization typo, it should have been 'Socket' not 'socket'). In the spec file of setroubleshoot-2.0.8-1.fc9 is another typo. Line 22: Requires: libxml2-pythonRequires(post): /usr/bin/update-desktop-database Should be: Requires: libxml2-python Requires(post): /usr/bin/update-desktop-database setroubleshoot-2.0.8-2.fc9 has been submitted as an update for Fedora 9 Thank you! Must be my day for silly editing mistakes :-) setroubleshoot-2.0.8-2.fc9 fixes the deleted line break. Pushed to updates-testing. Perfect, that version did it ;-) I really missed setroubleshoot over the last weeks. It's a real nice app! setroubleshoot-2.0.8-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: When setroubleshootd is started the following error message is generated in the logfile: 2008-06-14 13:43:09,315 [rpc.ERROR] exception TypeError: not all arguments converted during string formatting Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/setroubleshoot/rpc.py", line 940, in handle_client_io self.receiver.feed(data) File "/usr/lib/python2.5/site-packages/setroubleshoot/rpc.py", line 762, in feed self.process() File "/usr/lib/python2.5/site-packages/setroubleshoot/rpc.py", line 754, in process self.dispatchFunc(self.header, self.body) File "/usr/lib/python2.5/site-packages/setroubleshoot/rpc.py", line 978, in default_request_handler return_args = method_ptr(*args) File "/usr/lib/python2.5/site-packages/setroubleshoot/server.py", line 251, in logon raise ProgramError(ERR_USER_LOOKUP, detail="uid=s does not match logon username (%s)" % (self.uid, username)) TypeError: not all arguments converted during string formatting 2008-06-14 13:43:09,321 [rpc.WARNING] remove_client: client (channel: name=None addr={unix}/var/run/setroubleshoot/setroubleshoot_server socket=None type=sealert) not in client pool Also if I try to connect to the daemon via "/usr/bin/sealert -b" (ak. SELinux Troubleshooter) the same error message is generated in the logfile and the GUI just says "connection lost to /var/run/setroubleshoot/setroubleshoot_server" Version-Release number of selected component (if applicable): 2.0.6-1.fc9 Steps to Reproduce: Just restart or connect to setroubleshootd