similar to: CEBA-2013:1289 CentOS 6 abrt Update

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

Hi, hopping everyone is fine. I am using a Centos 7 server based on Nginx. I am using the server for providing downloadable data. Around 8 TB per day is downloaded. The server was working fine and perfectly. I hired a freelancer to limit the download speed as i am unexperienced with linux (Worst Mistake Ever) he messed up the server and after 4 hours said he cant impletement a simple

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

using a fully up to date 6.0 (and the CR repo) on my eeepc 901, every time the system boots and log in,, almost immediately (sometimes a few seconds later) get a popup from abrt complaining of a crash in the kernel package. yet the system continues to run fine, as far as I can tell. Package: kernel Latest Crash: Sun 04 Dec 2011 04:08:15 PM Command: not_applicable Reason:

There is a program that starts up abrt-dump-oops. What controls that starting up? It does not seem to be a "service" Thanks, Jerry

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

Hello, centos 7(1) I have a question about abrt-auto-reporting? should this work normal ? I have on my System Problems to report the Errors. Thanks for a answer, -- mit freundlichen Gr?ssen / best regards, G?nther J. Niederwimmer

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

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

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

ABRT is a collection of scripts that makes it easier to report bugs and crashes in various components of the distribution to a central server. Metadata from this allows developers and upstream projects to evaluate their priority chain, and also get crucial information on why their software might not be performing as expected on CentOS Linux. This information is sent to the server in a json format

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,

Hi All, I've been tuning a server recently and just today this has started to appear in my top/htop output. [root at db1 ~]# ps -aux | grep kernel root 1011 0.0 0.0 212048 4532 ? Ss 13:34 0:00 /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

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

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

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

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

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

When using nbdsh for scripting, it is convenient to let nbdsh fail with status 1 when encountering an API failure. However, doing so by letting the nbd.Error exception leak all the way causes ABRT (on Fedora 32 at least) to assume the program crashed from a programming error, and needlessly complicates clients to have to add try: blocks. Better is if nbdsh itself prints the same stack trace that

Everyone, I have a mail server running CentOS release 6.3 (Final) with 2.6.32-279.22.1.el6.i686 kernel that is reporting errors to me pertaining dovecot. I have appended the error message to this note. There is only one user that appears to generate this message, and it is generated to me by way of e-mail without a perceptible problem to the user which is not me. This particular user had an