similar to: ABRT for CentOS Linux is now live

Displaying 20 results from an estimated 10000 matches similar to: "ABRT for CentOS Linux is now live"

2014 Nov 18
1
CentOS-announce Digest, Vol 117, Issue 9
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2016 Aug 18
4
BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
This bug is reported only on the VM's with CentOS 7 running on on VMware ESXi 5.1. The vSphere performance graph shows high CPU consume and disk activity only on VM's with CentOS 7. Sometimes I can not connect remotely with ssh (timeout error). The details of last issues was reported to retrace.fedoraproject.org. ?Do you have a hint? [root at vmguest ~]# abrt-cli list id
2015 Jun 15
0
CESA-2015:1083 Important CentOS 7 abrt Security Update
CentOS Errata and Security Advisory 2015:1083 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1083.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4b27d42a4ed792b8cc8729cc65e6d70a82225000bbad1aa0f002a05582679de2 abrt-2.1.11-22.el7.centos.0.1.x86_64.rpm
2015 Jun 16
0
CentOS-announce Digest, Vol 124, Issue 7
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2020 Aug 17
2
C8 - Register with Red Hat
On Mon, 17 Aug 2020 17:49:29 -0500 Gregory P. Ennis wrote: > What appears is below. Removing dependent packages is required. Removing unused dependencies is optional. dnf remove *subscription* --noautoremove should remove the dependent packages but keep thee unused dependencies if you want them. There's also a setting in /etc/dnf/dnf.conf to set the default behaviour of the autoremove
2020 Aug 17
0
C8 - Register with Red Hat
On Mon, Aug 17, 2020 at 7:37 PM Gregory P. Ennis <PoMec at pomec.net> wrote: > On Mon, 17 Aug 2020 17:49:29 -0500 > Gregory P. Ennis wrote: > > > What appears is below. > > Removing dependent packages is required. Removing unused dependencies is > optional. > > dnf remove *subscription* --noautoremove > > should remove the dependent packages but keep
2020 Aug 25
2
C8 - Register with Red Hat
The subscription-manager dnf plugin is disabled by default as part of our debranding in both CentOS Linux and CentOS Stream. c8: https://git.centos.org/rpms/subscription-manager/blob/580aca8629536c64577e6a443b9349ecb629cc17/f/SPECS/subscription-manager.spec#_850 c8s:
2020 Aug 17
3
C8 - Register with Red Hat
On Mon, 17 Aug 2020 17:03:24 -0500 Gregory P. Ennis wrote: > I downloaded a Centos 8 image file : > > CentOS-8.1.1911-x86_64-dvd1.iso > > then I installed it as a kvm guest on a Centos 7 host machine. > > I installed a lot of the software; gui and server to give it a test drive. > > Nothing unusual about what I did that I can identify. And the message came up when
2013 Feb 01
0
CESA-2013:0215 Important CentOS 6 abrt Update
CentOS Errata and Security Advisory 2013:0215 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0215.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 99851e81e7cac7d406e9931753af92833ecc58fdcf5e328e715334382e169337 abrt-2.0.8-6.el6.centos.2.i686.rpm
2013 Sep 26
0
CEBA-2013:1289 CentOS 6 abrt Update
CentOS Errata and Bugfix Advisory 2013:1289 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-1289.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b201d09a7b2122d998fcf5aeeac00c57adc238968c89fe705e5f6b65efc5c86d abrt-2.0.8-16.el6.centos.1.i686.rpm
2012 Jul 10
0
CESA-2012:0841 Low CentOS 6 abrt Update
CentOS Errata and Security Advisory 2012:0841 Low Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0841.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a761ddbf659067983214235c2729f1247efa178eeb6f9ca87d2dc463afea3c71 abrt-2.0.8-6.el6.centos.i686.rpm
2015 Aug 20
1
Fwd: ABRT Daemon/sosreport disaster
On Sunday, I did a "yum update" which installed kernel 2.6.32-573.3.1.el6.i686 on half a dozen virtual machines running CentOS 6.7. Since then, two of them have gone into "meltdown", and started spewing "ABRT Daemon" emails: one on Tuesday, and one tonight. The machines have a very light workload -- one runs "trac", and a handful of development systems,
2017 Jan 30
0
Strange ABRT error when I try to switch to su
Hello all One of my VMs, running RHEL 7, has been giving me the following ABRT error when I try to login as su Ive seen this error the past three times that Ive logged in. I know that the VM is using Red Hat,but seeing that RHEL/CentOS are pretty much the same thing, I figured I should ask the CentOS mailing list for help. Here is the error: $ su Password: ABRT has detected 1 problem(s). For
2017 Apr 07
0
abrt reported "imap killed by SIGBUS"
Please keep responses on list. Can you please run valgrind on this, as it appears to be some sort of memory corruption issue. Aki > On April 7, 2017 at 5:37 AM Hongying Liu <hongyliu at redhat.com> wrote: > > > Thanks for your response. > > (gdb) p cache > $1 = (struct mail_cache *) 0x7fc4a811a320 > (gdb) p cache->hdr > $2 = (const struct mail_cache_header
2017 Apr 10
0
abrt reported "imap killed by SIGBUS"
Sorry for late response. This issue occurs ran randomly. So I don't know how to run valgrind command. 2017-04-10 17:14 GMT+08:00 Hongying Liu <hongyliu at redhat.com>: > Sorry for late response. > > This issue occurs ran randomly. So I don't know how to run valgrind > command. > > I upload the coredump. > > The version of dovecot is
2012 Jul 25
2
[PATCH 1/2] sysprep: remove the auto generated abrt data
remove the automatically generated abrt data. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- po/POTFILES-ml | 1 + sysprep/Makefile.am | 2 ++ sysprep/sysprep_operation_abrt_data.ml | 47 ++++++++++++++++++++++++++++++++++ 3 files changed, 50 insertions(+) create mode 100644 sysprep/sysprep_operation_abrt_data.ml diff --git
2013 Nov 02
0
How to debug a crash.. Looks like an abrt file.
I have to say the CentOS machines I have used so far seem to work well, so I was surprised the other day when an HP DL580G5 I had running CentOS 6.4 x86_64 the other day for some VM's under KVM/QEMU went belly up. Sadly the sucker was a remote box, so I wasn't just sitting in front of the console, but it looks like it left some files in /var/spool/abrt/oops-2013-11-01-14:00:22-8047-1 on
2018 Dec 20
0
abrt-watch-log -F BUG: WARNING:
Hi, Please what is this error ? /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table
2019 Feb 08
0
C7, enable an abrt for a daemon
I've mentioned here before that gssproxy is crashing all over the place with a SEGV. However, there's no /var/spool/abrt/... when it does. How do I enable the daemon to give me an abrt with information? I'm just not sure of what the right word is for systemd, so online searching isn't always useful. Thanks in advance. mark
2012 Jan 13
1
what to do about [abrt] full crash report kernel taint?
I have a machine with a recent install of centos (2.6.32-220.2.1.el6.x86_64 kernel). It crashed 3 times this week, and sent emails like the one below complaining about kernel taint. I've gone back to a previous kernel to see if that helps, but otherwise I don't know how to investigate this. What should I do? Here's stuff from the log and one of the emails: