Zimbra 8.8.8 Crashes after Kernel Update

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
krabat
Posts: 2
Joined: Mon Feb 06, 2017 3:14 pm

Zimbra 8.8.8 Crashes after Kernel Update

Post by krabat »

I'm not sure I'm in the right place. Sorry, if I'm not.

I run a Zimbraserver Ver. 8.8.8_GA3008.FOSS with current patch level.
My OS is Ubuntu 14.04.5 LTS
Kernel: 3.13.0-153-generic
The host runs in a KVM virtualization at my hoster and never had runtime problems in the past years.

When I install the current kernel 3.13.0-155-generic zimbra does not run anymore.
The Java provided with Zimbra crashes.
openjdk version "1.8.0_172-zimbra"

The error message in syslog:

Code: Select all

Aug 15 21:30:30 maili kernel: [   14.795713] PGD 1952e5067 PUD 1948cc067 PMD 1948ff067 PTE 80003ffffe17c225
Aug 15 21:30:30 maili kernel: [   14.796022] Bad pagetable: 000d [#1] SMP 
Aug 15 21:30:30 maili kernel: [   14.796022] Modules linked in: kvm_amd kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev serio_raw i2c_piix4 mac_hid lp parport hid_generic usbhid hid psmouse pata_acpi floppy
Aug 15 21:30:30 maili kernel: [   14.796022] CPU: 0 PID: 1306 Comm: java Not tainted 3.13.0-155-generic #205-Ubuntu
Aug 15 21:30:30 maili kernel: [   14.796022] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
Aug 15 21:30:30 maili kernel: [   14.796022] task: ffff880191e53000 ti: ffff880194abe000 task.ti: ffff880194abe000
Aug 15 21:30:30 maili kernel: [   14.796022] RIP: 0033:[<00007f1809111bb0>]  [<00007f1809111bb0>] 0x7f1809111bb0
Aug 15 21:30:30 maili kernel: [   14.796022] RSP: 002b:00007f182188cc38  EFLAGS: 00010206
Aug 15 21:30:30 maili kernel: [   14.796022] RAX: 0000000000000000 RBX: 00007f181db0c778 RCX: 00007f181db9fc08
Aug 15 21:30:30 maili kernel: [   14.796022] RDX: 00007f1809007d80 RSI: 00000000000006e0 RDI: 00007f182188cde0
Aug 15 21:30:30 maili kernel: [   14.796022] RBP: 00007f182188cc90 R08: 00007f1809013340 R09: 00007f182188cf28
Aug 15 21:30:30 maili kernel: [   14.796022] R10: 00007f1820c3fda0 R11: 00007f1809111b60 R12: 0000000000000000
Aug 15 21:30:30 maili kernel: [   14.796022] R13: 00007f182188cc50 R14: 00007f182188ccd8 R15: 00007f181800b000
Aug 15 21:30:30 maili kernel: [   14.796022] FS:  00007f182188f700(0000) GS:ffff880198e00000(0000) knlGS:0000000000000000
Aug 15 21:30:30 maili kernel: [   14.796022] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 15 21:30:30 maili kernel: [   14.796022] CR2: 00007f182178e100 CR3: 0000000193b64000 CR4: 00000000000407f0
Aug 15 21:30:30 maili kernel: [   14.796022] 
Aug 15 21:30:30 maili kernel: [   14.796022] RIP  [<00007f1809111bb0>] 0x7f1809111bb0
Aug 15 21:30:30 maili kernel: [   14.796022]  RSP <00007f182188cc38>
Aug 15 21:30:30 maili kernel: [   14.796022] ---[ end trace 88062b12b8e0efd6 ]---
Aug 15 21:30:30 maili kernel: [   14.843194] BUG: Bad page map in process java  pte:80003ffffe17c225 pmd:1948ff067
Aug 15 21:30:30 maili kernel: [   14.844903] addr:00007f182178e000 vm_flags:08000071 anon_vma:          (null) mapping:          (null) index:7f182178e
Aug 15 21:30:30 maili kernel: [   14.848395] CPU: 0 PID: 1306 Comm: java Tainted: G      D       3.13.0-155-generic #205-Ubuntu
Aug 15 21:30:30 maili kernel: [   14.850201] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
Aug 15 21:30:30 maili kernel: [   14.851996]  0000000000000000 ffff880194abfac8 ffffffff8173983f 00007f182178e000
Aug 15 21:30:30 maili kernel: [   14.852387]  ffff880036545980 ffff880194abfb18 ffffffff8117e374 80003ffffe17c225
Aug 15 21:30:30 maili kernel: [   14.852387]  00000001948ff067 00000007f182178e ffff8801948ffc70 ffff880194abfc88
Has the problem been observed elsewhere?
If so, how can it be fixed?
Is an upgrade to Zimbra 8.8.9 worthwhile?
svalavuo
Posts: 11
Joined: Sat Sep 13, 2014 12:35 am
Location: Rauma, Finland
ZCS/ZD Version: ZCS 8.8.9
Contact:

Re: Zimbra 8.8.8 Crashes after Kernel Update

Post by svalavuo »

Same happens with 8.8.9.
Removing 3.13.0-155-generic helped.
So, run -153 and everything is ok. :)
Post Reply