All Linux HowTo's

Solution to the “abrt-cli status timed out” problem

This article will help you if you’re receiving any of the following error messages. The short answer is that you need to reboot the server.

Please add a comment if this helps you. I’d love some feedback to know if this is for Azure only.

Can't connect to system DBus: Error calling StartServiceByName for org.freedesktop.problems: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.problems': timed out

…and

'abrt-cli status' timed out

I was not able to find a solution by running restart commands. I believe the problem is related to kernel versions in memory and its dependencies. For the record, the servers i am seeing with this error are in Microsoft Azure.

Similar Posts:

One comment

  1. In Reference to “‘abrt-cli status’ timed out”

    Step 1. Check the ownership of “/home//.cache/abrt/lastnotification” file and correct it as per RHEL article “https://access.redhat.com/solutions/3077311”
    i.e. If working with ‘user1’, then the ownership needs to be as below, group does not matter.
    -rw——- 1 user1 group1 11 Jun 9 16:44 lastnotification

    Verify

    Step 2. If the issue still persists, (as i had)
    Check for the status of the ‘abrtd’ service, in RHEL7 the output will indicate a locked file. i.e.

    Apr 01 00:00:00 abrtd[18351]: Lock file ‘.lock’ is locked by process 7436

    – Find the locking process and kill it.
    – Check the ‘abrtd’ service status again
    – If required, start the service
    – Verify for error message.

    Hope this helps/.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.