Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 need dbus which is provided by messagebus daemon. User might disable messagebus which cause abrtd cannot start:
===
abrtd: Failed to start: timeout waiting for child
===
abrtd -vvvv show the correct reason:
===
abrtd: dbus error: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
abrtd: Error requesting DBus name com.redhat.abrt, possible reasons: abrt run by non-root; dbus config is incorrect; or dbus daemon needs to be restarted to reload dbus config
abrtd: Failed to start: timeout waiting for child
===
You might also think about change the warning message of /etc/init.d/abrtd, it don't provide any useful information with "timeout waiting for child".
Version-Release number of selected component (if applicable):
RHEL 6.1
How reproducible:
100%
Steps to Reproduce:
1. Stop messagebus daemon
2. Start abrtd daemon
Actual results:
abrtd start failed with meaningless error message.
Expected results:
Abrtd require messagebus in LBS header and provide useful error message to user.
Additional info:
(In reply to comment #0)
> Description of problem:
>
> abrtd need dbus which is provided by messagebus daemon. User might disable
> messagebus which cause abrtd cannot start:
> ===
> abrtd: Failed to start: timeout waiting for child
this is printed out, but take a look at /var/log/message. The rest of error message is there. If you invoke abrtd without -d and -v it will put all logs into /var/log/message
> You might also think about change the warning message of /etc/init.d/abrtd, it
> don't provide any useful information with "timeout waiting for child".
that message comes from abrtd binary not from init script
I'm going to close the bug as NOTABUG. The reasonable message is printed out to /var/log/messages when -d and -v options are not specified.
Feel free to reopen for rhel6.3 if you think that message needs to be printed out for stderr without options -d and -v.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1598.html