RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
# rpm -qa setroubleshoot\* | sort
setroubleshoot-2.2.91-1.el6.i686
setroubleshoot-plugins-2.1.58-1.el6.noarch
setroubleshoot-server-2.2.91-1.el6.i686
# /sbin/chkconfig --list setroubleshoot
error reading information on service setroubleshoot: No such file or directory
# /sbin/chkconfig --list setroubleshootd
error reading information on service setroubleshootd: No such file or directory
# /sbin/chkconfig --list | grep -i setrouble
# 

Actual results
========
After installing the setroubleshoot-server package, use the /sbin/chkconfig --list setroubleshoot command to confirm that setroubleshootd starts when the system is running in runlevel[9] 3, 4, and 5:

$ /sbin/chkconfig --list setroubleshoot
setroubleshoot  0:off   1:off   2:off   3:on    4:on    5:on    6:off

If the output differs, as the Linux root user, run the /sbin/chkconfig --levels 345 setroubleshoot on command. This makes setroubleshootd automatically start when the system is in runlevel 3, 4, and 5. 

Expected results
==========
remove these lines

fixed in 2.0-9 on doc-stage

Verified: Red_Hat_Enterprise_Linux-Security-Enhanced_Linux-web-6-en-US-2.0.el5

setroubleshootd is no longer mentioned.