Discuss February 2013

discuss@lists.centos.org

203 participants
198 discussions

Centos 6.3 and dovecot with an abrt problem
by Gregory P. Ennis 23 Feb '13

23 Feb '13

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 inbox greater than 2 gigs in size, so I asked him to move or delete unwanted files, which reduced the size of the inbox to 400 megs. Unfortunately, the abrt messages have continued. I did a google search on : "usr/libexec/dovecot/imap was killed by signal 6", but did not find much that I could use to help me debug this. Can any of you point me in the right direction. ' Thanks much!!! Greg From: user(a)domain.com To: root(a)domain.com Subject: [abrt] full crash report Date: Fri, 22 Feb 2013 17:57:29 -0600 abrt_version: 2.0.8 cmdline: dovecot/imap environ: '\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab' executable: /usr/libexec/dovecot/imap kernel: 2.6.32-279.22.1.el6.i686 pid: 12871 pwd: /home/user reason: Process /usr/libexec/dovecot/imap was killed by signal 6 (SIGABRT) time: Fri 22 Feb 2013 05:56:56 PM CST uid: 507 username: user sosreport.tar.xz: Binary file, 2236756 bytes limits: :Limit Soft Limit Hard Limit Units :Max cpu time unlimited unlimited seconds :Max file size unlimited unlimited bytes :Max data size unlimited unlimited bytes :Max stack size 10485760 unlimited bytes :Max core file size 0 unlimited bytes :Max resident set unlimited unlimited bytes :Max processes 1024 19090 processes :Max open files 1024 4096 files :Max locked memory 65536 65536 bytes :Max address space unlimited unlimited bytes :Max file locks unlimited unlimited locks :Max pending signals 19090 19090 signals :Max msgqueue size 819200 819200 bytes :Max nice priority 0 0 :Max realtime priority 0 0 :Max realtime timeout unlimited unlimited us maps: :001ec000-001f8000 r-xp 00000000 08:07 2108047 /lib/libnss_files-2.12.so :001f8000-001f9000 r--p 0000b000 08:07 2108047 /lib/libnss_files-2.12.so :001f9000-001fa000 rw-p 0000c000 08:07 2108047 /lib/libnss_files-2.12.so :00595000-00596000 r-xp 00000000 00:00 0 [vdso] :0069b000-006b9000 r-xp 00000000 08:07 2109054 /lib/ld-2.12.so :006b9000-006ba000 r--p 0001d000 08:07 2109054 /lib/ld-2.12.so :006ba000-006bb000 rw-p 0001e000 08:07 2109054 /lib/ld-2.12.so :006bd000-0084d000 r-xp 00000000 08:07 2109055 /lib/libc-2.12.so :0084d000-0084f000 r--p 0018f000 08:07 2109055 /lib/libc-2.12.so :0084f000-00850000 rw-p 00191000 08:07 2109055 /lib/libc-2.12.so :00850000-00853000 rw-p 00000000 00:00 0 :00881000-00884000 r-xp 00000000 08:07 2109061 /lib/libdl-2.12.so :00884000-00885000 r--p 00002000 08:07 2109061 /lib/libdl-2.12.so :00885000-00886000 rw-p 00003000 08:07 2109061 /lib/libdl-2.12.so :00888000-0089f000 r-xp 00000000 08:07 2109060 /lib/libpthread-2.12.so :0089f000-008a0000 r--p 00016000 08:07 2109060 /lib/libpthread-2.12.so :008a0000-008a1000 rw-p 00017000 08:07 2109060 /lib/libpthread-2.12.so :008a1000-008a3000 rw-p 00000000 00:00 0 :008bb000-008c2000 r-xp 00000000 08:07 2109063 /lib/librt-2.12.so :008c2000-008c3000 r--p 00006000 08:07 2109063 /lib/librt-2.12.so :008c3000-008c4000 rw-p 00007000 08:07 2109063 /lib/librt-2.12.so :008c6000-00946000 r-xp 00000000 08:07 1071940 /usr/lib/dovecot/libdovecot.so.0.0.0 :00946000-00948000 rw-p 0007f000 08:07 1071940 /usr/lib/dovecot/libdovecot.so.0.0.0 :00948000-00949000 rw-p 00000000 00:00 0 :0094b000-00a21000 r-xp 00000000 08:07 1079292 /usr/lib/dovecot/libdovecot-storage.so.0.0.0 :00a21000-00a25000 rw-p 000d6000 08:07 1079292 /usr/lib/dovecot/libdovecot-storage.so.0.0.0 :00d59000-00d76000 r-xp 00000000 08:07 2109059 /lib/libgcc_s-4.4.6-20120305.so.1 :00d76000-00d77000 rw-p 0001d000 08:07 2109059 /lib/libgcc_s-4.4.6-20120305.so.1 :08048000-08066000 r-xp 00000000 08:07 1187972 /usr/libexec/dovecot/imap :08066000-08069000 rw-p 0001e000 08:07 1187972 /usr/libexec/dovecot/imap :09722000-0976c000 rw-p 00000000 00:00 0 [heap] :b7619000-b769a000 rw-p 00000000 00:00 0 :b7703000-b7705000 rw-p 00000000 00:00 0 :b771c000-b771f000 r--s 00000000 08:06 5373984 /home/user/mail/.imap/INBOX/dovecot.index.log :b771f000-b7720000 rw-p 00000000 00:00 0 :bf9d8000-bf9ed000 rw-p 00000000 00:00 0 [stack] open_fds: :0:/dev/null :pos: 0 :flags: 0100001 :1:/dev/null :pos: 0 :flags: 0100001 :2:pipe:[12459322] :pos: 0 :flags: 01 :3:pipe:[12459236] :pos: 0 :flags: 01 :4:pipe:[16684763] :pos: 0 :flags: 04000 :5:pipe:[12459338] :pos: 0 :flags: 04001 :6:pipe:[12459231] :pos: 0 :flags: 01 :7:socket:[12459252] :pos: 0 :flags: 04002 :8:pipe:[16684763] :pos: 0 :flags: 04001 :9:anon_inode:[eventpoll] :pos: 0 :flags: 02 :10:/home/user/mail/.imap/Draft/dovecot.index.log :pos: 0 :flags: 0100002 :11:socket:[16684731] :pos: 0 :flags: 04002 :12:/home/user/mail/.imap/Draft/dovecot.index :pos: 0 :flags: 0100002 :13:/home/user/mail/.imap/INBOX/dovecot.index.log :pos: 0 :flags: 0100002 :14:/home/user/mail/.imap/INBOX/dovecot.index :pos: 0 :flags: 0100002 :15:/home/user/mail/.imap/Sent/dovecot.index.log :pos: 0 :flags: 0100002 :16:/home/user/mail/.imap/Sent/dovecot.index :pos: 0 :flags: 0100002

1 0

Re: [CentOS] Warning: Your BIOS is broken
by Robert Moskowitz 22 Feb '13

22 Feb '13

On 02/22/2013 02:32 PM, Reindl Harald wrote: > > Am 22.02.2013 20:28, schrieb Robert Moskowitz: >>> on a similar/identical bug with Fedora FC17, someone suggested booting >>> with iommu=off to work around this. >> Where do I add this? > like every other kernel param in /boot/grub/grub.conf at > the end of the kernel line Kernel param. I really should have caught that. So I was all ready to edit grub.conf and then slapped my hand. You TEST it out first, adding the command at boot time. ARGH! Once before (5+ years back) I had to add a kernel param and did it wrong and it was a big recovery challenge. No test and verify before making permanent. Whew. So I googled the param to get its format right, and it is iommu=off. Without that dash in front. But as I read up on this option, it does not sound like something I want to globally turn off just to stop a supposedly annoying message (if they have indeed worked around it, and my new DNS server is running with this OK). So I will test from booting and typing the option in without actually altering grub.conf. But if there is a way to just stop getting this message, that would be good too. thank you all for your help. > > https://www.google.com/search?q=linux+add+kernel+params > http://www.kernel.org/doc/Documentation/kernel-parameters.txt >

1 0

Warning: Your BIOS is broken
by Robert Moskowitz 22 Feb '13

22 Feb '13

I am getting the following on my 'new box' for my DNS server: Date: Wed, 20 Feb 2013 13:58:04 -0500 From: To: Subject: [abrt] full crash report User-Agent: Heirloom mailx 12.4 7/29/08 abrt_version: 2.0.8 cmdline: ro root=/dev/mapper/vg_onlo3-root_01 rd_NO_LUKS rd_LVM_LV=vg_onlo3/root_01 LANG=en_US.UTF-8 +rd_NO_MD SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=128M rhgb quiet rd_NO_DM rhgb +quiet kernel: 2.6.32-279.22.1.el6.i686 not-reportable: Your BIOS is broken reason: WARNING: at drivers/pci/dmar.c:594 warn_invalid_dmar+0x7f/0xa0() (Not tainted) time: Wed 20 Feb 2013 01:57:36 PM EST sosreport.tar.xz: Binary file, 460076 bytes backtrace: :WARNING: at drivers/pci/dmar.c:594 warn_invalid_dmar+0x7f/0xa0() (Not tainted) :Hardware name: HP Compaq dc7800 Small Form Factor :[Firmware Warn]: Your BIOS is broken; DMAR reported at address fed90000 returns all ones! :BIOS vendor: Hewlett-Packard; Ver: 786F1 v01.04; Product Version: :Modules linked in: :Pid: 0, comm: swapper Not tainted 2.6.32-279.22.1.el6.i686 #1 :Call Trace: :[<c0455141>] ? warn_slowpath_common+0x81/0xc0 :[<c06217ff>] ? warn_invalid_dmar+0x7f/0xa0 :[<c06217ff>] ? warn_invalid_dmar+0x7f/0xa0 :[<c04551d3>] ? warn_slowpath_fmt_taint+0x33/0x40 :[<c06217ff>] ? warn_invalid_dmar+0x7f/0xa0 :[<c0abdeb8>] ? check_zero_address+0xfb/0x132 :[<c06608b7>] ? acpi_tb_verify_table+0x1d/0x46 :[<c0abdefd>] ? detect_intel_iommu+0xe/0x57 :[<c0aae15b>] ? mem_init+0x10/0x2ab :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c082ee00>] ? die_nmi+0x80/0xf0 :[<c082ee00>] ? die_nmi+0x80/0xf0 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0a9781d>] ? start_kernel+0x1d1/0x3b5 :[<c0a9748a>] ? unknown_bootoption+0x0/0x190 Should I worry?

4 8

Re: [CentOS] Dell Precision M6700 with centos 5?
by Eero Volotinen 22 Feb '13

22 Feb '13

>> any experiences with centos 5/rhel 5 install? machine is rhel 6.1 >> certified laptop? > > Why not install CentOS 6.3 instead? CentOS and RHEL are binary compatible. Yes, but Centos 5 is needed on this project. -- Eero

4 7

IPV6 auto configuration cannot be disabled from if script.
by Eliezer Croitoru 22 Feb '13

22 Feb '13

I want to configure IPV6 on the system and not use some auto ipv6 config. I have tried to use IPV6_AUTOCONF=no in interface script dose not affect anything. ifcfg-eth0: GATEWAY=192.168.1.254 IPV6INIT=no IPV6_AUTOCONF=no BROADCAST=192.168.1.255 BOOTPROTO=none NAME="" NM_CONTROLLED=yes MACADDR="" TYPE=Ethernet DEVICE=eth0 NETMASK=255.255.255.0 MTU="1500" IPADDR=192.168.11.1 NETWORK=192.168.11.0 ONBOOT=yes The above file should have resulted an interface with only inet address but the result is: eth0 Link encap:Ethernet HWaddr XX inet addr:192.168.11.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::7271:bcff:febd:c46b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24452216 errors:0 dropped:0 overruns:0 frame:0 TX packets:38068314 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6777513704 (6.3 GiB) TX bytes:21817051849 (20.3 GiB) Interrupt:29 Base address:0xc000 Thanks, Eliezer Croitoru

6 7

RHEL 6.4 == FC?
by Robert Moskowitz 22 Feb '13

22 Feb '13

I have read that v 6.3 is about Fedora 12. Now that v 6.4 has shipped (no I won't be dumb enough to ask when C6.4 we ship), what version of Fedora does it match up with?

6 9

Strange errors with NFS under CentOS 6.3
by C. L. Martinez 22 Feb '13

22 Feb '13

Hi all, This morning, my centos NFS server returns these error messages: RPC: fragment too large: 0x00800103 RPC: multiple fragments per record not supported RPC: fragment too large: 0x00800103 RPC: multiple fragments per record not supported RPC: fragment too large: 0x00800103 RPC: multiple fragments per record not supported RPC: fragment too large: 0x00800103 RPC: multiple fragments per record not supported I have googled arround this type of error and the only solution that I have found is to change tso to off in network interface, but error continues. Any idea?? Many thanks.

1 0

Dell Precision M6700 with centos 5?
by Eero Volotinen 22 Feb '13

22 Feb '13

any experiences with centos 5/rhel 5 install? machine is rhel 6.1 certified laptop? -- Eero

2 1

Packaging bug: xulrunner-17.0.3-1.el5_9.i386.rpm
by Robert Heller 21 Feb '13

21 Feb '13

Minor packaging bug: with the new xulrunner (at least for 32-bit): When running the /usr/bin/xulrunner script, it looks for the binary in /usr/lib/xulrunner-17.0.3, but all of the files are actually installed in /usr/lib/xulrunner. Creating a symlink: cd /usr/lib ln -s xulrunner xulrunner-17.0.3 cures the problem. -- Robert Heller -- 978-544-6933 / heller(a)deepsoft.com Deepwoods Software -- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments

1 0

libtiff with bigtiff support
by Weiner, Michael 21 Feb '13

21 Feb '13

Can anyone tell me if the current libtiff-3.9.4-9.el6_3.x86_64 RPM has bigtiff support built into it? I need this for tiling rather large images for the Virtual Microscope project I am working on, and I am having issues building the 4x versions that only seem to be available for F18. Thank you for any information you can provide Michael Weiner =================================== Please consider the environment before printing this e-mail Cleveland Clinic is ranked one of the top hospitals in America by U.S.News & World Report (2012). Visit us online at http://www.clevelandclinic.org for a complete listing of our services, staff and locations. Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you.

2 1

← Newer
1
...
4
5
6
7
8
9
10
...
20
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss February 2013