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:
abrtd consumes high cpu when restarting abrt daemon from satellite remote command utility.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux - 6.2
Red Hat Satellite release 5.6.0

How reproducible:
always

Steps to Reproduce:
1. Login to Red Hat Satellite portal
2. Select a host or hosts from the "Systems" tab.
3. With the host(s) selected click the "Manage" button at the top right side of the page.
4. Click "remote commands" from the "Provisioning" section.
5. Enter your script i.e.:
      #!/bin/bash
      /sbin/service abrtd restart
6. Click "Schedule Remote Command" button at the bottom right.
7. Click "Schedule commands" button at the bottom right.
8. Wait for the commands to execute on each host on schedule.
9. Now login to any client for satellite and check top. 
abrtd consumes almost more CPU.

Actual results:
abrtd consumes 90-95% of CPU

Expected results:
abrtd does not consumes 90-95% of CPU

Additional info: