Announcement

Collapse
No announcement yet.

ABRT problems

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ABRT problems

    Hello,

    I have some installations of Cloudlinux 7 physical servers and I keep getting ABRT warnings at login about the kernel:

    ABRT has detected 6 problem(s). For more info run: abrt-cli list

    [root@hostname ~]# abrt-cli list

    reason: WARNING: at lib/list_debug.c:59 __list_del_entry+0xa1/0xd0()
    time: Tue 22 Nov 2016 06:28:29 PM WEST
    cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-427.10.1.lve1.4.22.el7.x86_64 root=UUID=522a7708-31a2-40e1-8070-383512e0ef4d ro crashkernel=auto rd.md.uuid=9343f694:10bd45db:f4a9d712:3d115d67 rd.md.uuid=1c5bfff3:f81d94d0:662e0040:99131ba7 rd.md.uuid=4945aee6:ce525ed6:34236c18:13924326 rd.md.uuid=e31bda51:b30ffc21:4b617043:2cc25415 rhgb quiet
    package: kernel
    uid: 0 (root)
    count: 53
    Directory: /var/spool/abrt/oops-2016-11-22-18:28:29-217592-0
    Reported: cannot be reported

    reason: WARNING: at lib/list_debug.c:36 __list_add+0x8a/0xc0()
    time: Tue 22 Nov 2016 06:09:35 PM WEST
    cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-427.10.1.lve1.4.22.el7.x86_64 root=UUID=522a7708-31a2-40e1-8070-383512e0ef4d ro crashkernel=auto rd.md.uuid=9343f694:10bd45db:f4a9d712:3d115d67 rd.md.uuid=1c5bfff3:f81d94d0:662e0040:99131ba7 rd.md.uuid=4945aee6:ce525ed6:34236c18:13924326 rd.md.uuid=e31bda51:b30ffc21:4b617043:2cc25415 rhgb quiet
    uid: 0
    count: 265
    Directory: /var/spool/abrt/oops-2016-11-22-18:09:33-210397-2
    Reported: cannot be reported

    These are just the first two entries. Does anybody know what the problem is and how can I solve it?

    Let me know if anybody needs any other info.

    Thank you.

  • #2
    Hello,

    First of all please try using latest kernel. I see from our internal bugzilla something related has been fixed already. Here is latest stable: https://www.cloudlinux.com/cloudlinu...o-production-1

    If issue happens after update/reboot please create support ticket at https://helpdesk.cloudlinux.com .

    Comment


    • #3
      Hello,

      I did update the kernel, but I got some errors in /var/log/messages:

      Dec 1 18:20:58 myserver NetworkManager[1577]: (NetworkManager:1577): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
      Dec 1 18:20:58 myserver NetworkManager[1577]: [1480594858.4497] bus-manager: could not create org.freedesktop.DBus proxy (Error calling StartServiceByName for org.freedesktop.DBus: The connection is closed); only the private D-Bus socket will be available
      Dec 1 18:21:01 myserver NetworkManager[1577]: (NetworkManager:1577): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
      Dec 1 18:21:01 myserver NetworkManager[1577]: [1480594861.4501] bus-manager: could not create org.freedesktop.DBus proxy (Error calling StartServiceByName for org.freedesktop.DBus: The connection is closed); only the private D-Bus socket will be available

      Also, while trying to restart exim, I got the following errors:

      [root@myserver log]# service exim restart
      Redirecting to /bin/systemctl restart exim.service
      Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)

      Can something be done to solve these issues?

      Comment


      • #4
        We never saw something like that. How often this errors are happening? I have found https://access.redhat.com/solutions/2695651and they says if errors are happening during server shutdown - you may ignore them.

        About exim, really not sure. Better to create support ticket with us.

        Comment


        • #5
          Hello,

          I cannot see the content of your thread as I do not have the proper subscription.

          The command which gives the "Error getting authority" error is not bound to a single process. It happens if I restart exim, ipaliases, cpanel and a whole bunch of other services.

          [root@myserver ~]# service ipaliases restart
          Redirecting to /bin/systemctl restart ipaliases.service
          Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)
          [root@myserver ~]# systemctl restart ipaliases
          Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)
          [root@myserver ~]# service cpanel restart
          Redirecting to /bin/systemctl restart cpanel.service
          Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)

          These errors are from /var/log/messages and they keep pilling up and filling up the log.

          Dec 1 18:50:01 myserver NetworkManager[1520]: (NetworkManager:1520): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
          Dec 1 18:50:01 myserver NetworkManager[1520]: [1480611001.6048] bus-manager: could not create org.freedesktop.DBus proxy (Error calling StartServiceByName for org.freedesktop.DBus: The connection is closed); only the private D-Bus socket will be available
          Dec 1 18:50:01 myserver crond[1552]: Use of uninitialized value in concatenation (.) or string at /usr/bin/sendmail line 15.
          Dec 1 18:50:04 myserver NetworkManager[1520]: (NetworkManager:1520): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
          Dec 1 18:50:04 myserver NetworkManager[1520]: [1480611004.6041] bus-manager: could not create org.freedesktop.DBus proxy (Error calling StartServiceByName for org.freedesktop.DBus: The connection is closed); only the private D-Bus socket will be available
          Dec 1 18:50:07 myserver NetworkManager[1520]: (NetworkManager:1520): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
          Dec 1 18:50:07 myserver NetworkManager[1520]: [1480611007.6044] bus-manager: could not create org.freedesktop.DBus proxy (Error calling StartServiceByName for org.freedesktop.DBus: The connection is closed); only the private D-Bus socket will be available

          Any suggestion?

          Comment


          • #6
            I worry no suggestions here. I do not like it, but Is this happening after server reboot? Something happened to systemd.

            I believe it is a time to create support ticket with us.

            Comment


            • #7
              Hello,

              Ive opened a ticket with your support team. Will come back with feedback.

              Thank you.

              Comment

              Working...
              X