Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators
Reload this Page CentOS 5.2 with stuck emails and random reboots

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
Page 1 of 2 1 2
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-30-2009, 10:52 AM
Intermediate Member
  
Posts: 16
Default CentOS 5.2 with stuck emails and random reboots
I'm running Zimbra 5.0.13 on CentOS 5.2 and have problems with periodic server reboots after which emails stick in the mail queue. Sometimes I can clear them by requeueing but most often I have to reboot the server. the periodic reboots began after installing Zimbra.

I've invested a lot of my own time and have had a couple of Linux admins look at it but can't seem to find the problem. Is there an experienced Zimbra admin who would be willing to take a look at my server?

Thanks
Reply With Quote
  #2 (permalink)  
Old 03-30-2009, 12:46 PM
Moderator
  
Posts: 7,928
Default
Okay, server specs ? Memory/CPU etc ... Is it a VM ? what does dmesg show ?
__________________
Reply With Quote
  #3 (permalink)  
Old 03-30-2009, 01:48 PM
Intermediate Member
  
Posts: 16
Default
Compaq Proliant 5500 Quad PIII 500 Xeon 2.5 gig memory, no VM. The server is only running Zimbra and Apache.

sizeof(dentry)=136 bytes
sizeof(ext3inode)=492 bytes
sizeof(buffer_head)=52 bytes
sizeof(skbuff)=172 bytes
migration_cost=2218
checking if image is initramfs... it is
Freeing initrd memory: 3041k freed
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread F7CC4AA0 could not acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread F7CC4AA0 could not acquire Mutex [2] [20060707]
PCI: PCI BIOS revision 2.10 entry at 0xf0080, last bus=9
PCI: Using configuration type 1
Setting up standard PCI resources
mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: probably your BIOS does not setup all CPUs.
mtrr: corrected configuration.
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
usbcore: USB support disabled
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:00:0e.0
* Found PM-Timer Bug on the chipset. Due to workarounds for a bug,
* this clock source is slow. Consider trying other clock sources
PCI quirk: region 1200-123f claimed by PIIX4 ACPI
PCI quirk: region 1240-124f claimed by PIIX4 SMB
PCI: Searching for i450NX host bridges on 0000:00:10.0
PCI: Device 0000:00:0f.0 not found by BIOS
PCI: Device 0000:00:10.0 not found by BIOS
PCI: Device 0000:00:12.0 not found by BIOS
PCI: Device 0000:00:13.0 not found by BIOS
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
PCI: Bridge: 0000:04:02.0
IO window: 4000-4fff
MEM window: f7f00000-f7ffffff
PREFETCH window: a8100000-a81fffff
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
apm: BIOS not found.
audit: initializing netlink socket (disabled)
audit(1238331659.928:1): initialized
highmem bounce pool size: 64 pages
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key C6715965C252FDCB
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: C0 revision 450NX. Disabling PCI restreaming.
PCI: C0 revision 450NX. Disabling PCI restreaming.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:0f.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x3000-0x3007, BIOS settings: hdaio, hdbio
Probing IDE interface ide0...
hdb: COMPAQ CDR-8435, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
PIIX4: IDE controller at PCI slot 0000:00:10.0
PIIX4: device not capable of full native PCI mode
PIIX4: device disabled (BIOS)
PIIX4: IDE controller at PCI slot 0000:00:10.0
PIIX4: device not capable of full native PCI mode
PIIX4: device disabled (BIOS)
Probing IDE interface ide1...
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
ide-floppy driver 0.99.newide
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
Time: tsc clocksource has been installed.
Freeing unused kernel memory: 228k freed
Write protecting the kernel read-only data: 393k
input: AT Translated Set 2 keyboard as /class/input/input0
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v3.0
Compaq SMART2 Driver (v 2.6.0)
cpqarray: Device 0xae10 has been found at bus 5 dev 0 func 0
PCI: Setting latency timer of device 0000:05:00.0 to 64
cpqarray: Finding drives on ida0 (Smart Array 3200)
cpqarray ida/c0d0: blksz=512 nr_blks=17764320
cpqarray ida/c0d1: blksz=512 nr_blks=142253280
ida/c0d0: p1 p2 p3
ida/c0d1: p1
SCSI subsystem initialized
sym0: <875> rev 0x14 at pci 0000:00:0d.0 irq 10
sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.2.3
target0:0:4: FAST-10 WIDE SCSI 20.0 MB/s ST (100 ns, offset 15)
Vendor: QUANTUM Model: DLT7000 Rev: 296D
Type: Sequential-Access ANSI SCSI revision: 02
target0:0:4: Beginning Domain Validation
target0:0:4: asynchronous
target0:0:4: wide asynchronous
target0:0:4: FAST-10 WIDE SCSI 20.0 MB/s ST (100 ns, offset 15)
target0:0:4: Domain Validation skipping write tests
target0:0:4: Ending Domain Validation
sym1: <875> rev 0x14 at pci 0000:00:0d.1 irq 11
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: SCSI BUS has been reset.
scsi1 : sym-2.2.3
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel@redhat.com
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: dm-0: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 1475331
ext3_orphan_cleanup: deleting unreferenced inode 1475378
ext3_orphan_cleanup: deleting unreferenced inode 1475376
ext3_orphan_cleanup: deleting unreferenced inode 1475372
ext3_orphan_cleanup: deleting unreferenced inode 1475350
ext3_orphan_cleanup: deleting unreferenced inode 1475347
ext3_orphan_cleanup: deleting unreferenced inode 1475335
ext3_orphan_cleanup: deleting unreferenced inode 1475330
ext3_orphan_cleanup: deleting unreferenced inode 1475329
ext3_orphan_cleanup: deleting unreferenced inode 1475327
ext3_orphan_cleanup: deleting unreferenced inode 1475326
ext3_orphan_cleanup: deleting unreferenced inode 1475314
ext3_orphan_cleanup: deleting unreferenced inode 1475312
ext3_orphan_cleanup: deleting unreferenced inode 1475311
ext3_orphan_cleanup: deleting unreferenced inode 1475310
ext3_orphan_cleanup: deleting unreferenced inode 1475309
ext3_orphan_cleanup: deleting unreferenced inode 1475308
EXT3-fs: dm-0: 17 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: Disabled at runtime.
SELinux: Unregistering netfilter hooks
audit(1238331695.089:2): selinux=0 auid=4294967295 ses=4294967295
USB Universal Host Controller Interface driver v3.0
input: PC Speaker as /class/input/input1
ThunderLAN driver v1.15
TLAN: eth0 irq= 9, io=2000, Compaq Netelligent 10/100 TX PCI UTP, Rev. 16
TLAN: 1 device installed, PCI: 1 EISA: 0
Floppy drive(s): fd0 is 1.44M
hdb: ATAPI 32X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.20
FDC 0 is a National Semiconductor PC87306
libata version 3.00 loaded.
piix4_smbus 0000:00:0f.3: Found 0000:00:0f.3 device
piix4_smbus 0000:00:0f.3: Host SMBus controller not enabled!
ata_piix 0000:00:10.0: version 2.12
ata_piix 0000:00:10.0: 450NX errata present, disabling IDE DMA.
ata_piix 0000:00:10.0: A BIOS update may resolve this.
ata_piix 0000:00:10.0: no available native port
scsi 0:0:4:0: Attached scsi generic sg0 type 1
st: Version 20050830, fixed bufsize 32768, s/g segs 256
st 0:0:4:0: Attached scsi tape st0
st0: try direct i/o: yes (alignment 512 B)
st0: Block limits 2 - 16777214 bytes.
parport0: PC-style at 0x3bc [PCSPP,TRISTATE]
lp0: using parport0 (polling).
lp0: console ready
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
device-mapper: multipath: version 1.0.5 loaded
EXT3 FS on dm-0, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on ida/c0d0p1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on ida/c0d1p1, internal journal
ext3_orphan_cleanup: deleting unreferenced inode 4947986
ext3_orphan_cleanup: deleting unreferenced inode 4947989
ext3_orphan_cleanup: deleting unreferenced inode 4947997
ext3_orphan_cleanup: deleting unreferenced inode 4947990
ext3_orphan_cleanup: deleting unreferenced inode 4947987
EXT3-fs: ida/c0d1p1: 5 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Adding 2031608k swap on /dev/VolGroup00/LogVol01. Priority:-1 extents:1 across:2031608k
IA-32 Microcode Update Driver: v1.14a <tigran@veritas.com>
TLAN: eth0: Starting autonegotiation.
TLAN: eth0: Autonegotiation complete.
TLAN: eth0: Link active with AutoNegotiation enabled, at 100Mbps Full-Duplex
TLAN: Partner capability: 10BaseT-HD 10BaseT-FD 100baseTx-HD 100baseTx-FD<NULL>
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
eth0: no IPv6 routers present
[root@mail ~]#
Reply With Quote
  #4 (permalink)  
Old 03-30-2009, 11:05 PM
Zimbra Consultant & Moderator
  
Posts: 20,312
Default
That server is under the recommended specification for running Zimbra, it should be a 1.5GHZ. Randon reboots usually indicate a hardware problem, have you tried running a memory check for at least 24-48hrs?
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 03-31-2009, 12:52 AM
Moderator
  
Posts: 7,928
Default
Do you have access to the console to see if there are any other error messages when it reboots ?
__________________
Reply With Quote
  #6 (permalink)  
Old 03-31-2009, 08:08 AM
Intermediate Member
  
Posts: 16
Default
I've run the memory test on a couple of different occasions and it has passed both times with no problems.

Regarding the logs, there are no indications of a problem before the reboot, it simply shows the reboot.
Reply With Quote
  #7 (permalink)  
Old 03-31-2009, 08:22 AM
Zimbra Consultant & Moderator
  
Posts: 20,312
Default
Quote:
Originally Posted by white8 View Post
I've run the memory test on a couple of different occasions and it has passed both times with no problems.
How long did you run it for? Memory problems don't always show unless you run them for 48hrs. What about HD problems, have you checked them?
__________________
Regards


Bill
Reply With Quote
  #8 (permalink)  
Old 03-31-2009, 08:42 AM
Intermediate Member
  
Posts: 16
Default
The memory test ran for 3-4 days and all of the hard drives are showing good.
Reply With Quote
  #9 (permalink)  
Old 03-31-2009, 08:43 AM
Moderator
  
Posts: 7,928
Default
How old is the PSU in the server ?
__________________
Reply With Quote
  #10 (permalink)  
Old 03-31-2009, 08:52 AM
Intermediate Member
  
Posts: 16
Default
It has two and they came with the server so I don't know the age. Each one is fed by its own UPS
Reply With Quote
Reply
Page 1 of 2 1 2

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode


Product Information

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com


Home - Blog - Contact Us - Archive - Top


 

SEO by vBSEO ©2011, Crawlability, Inc.