Fatal Java Error stops zmmailboxdctl

[tbovingdon]

Good Day,

Our

Release 6.0.5_GA_2213.UBUNTU8 UBUNTU8 FOSS edition.

just suddenly stopped working..

status shows zmmailboxdctl and zmclamdctl not running.
zmmailboxd.out shows repeated:

A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xb74382bb, pid=7889, tid=3072363408
#
# JRE version: 6.0_16-b01
# Java VM: Java HotSpot(TM) Server VM (14.2-b01 mixed mode linux-x86 )
# Problematic frame:
# V  [libjvm.so+0x20a2bb]
#
# An error report file with more information is saved as:
# /opt/zimbra/log/hs_err_pid7889.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp

• fsck checks out ok
• trying to "repair" the installation the install tries to install the first .deb and fails (thank god for vm snapshots!)

not sure what else to do from here... any suggestions?

it is running on a exsi 3.5 box 4gb RAM 1 processor

cat /proc/meminfo
MemTotal:      3896244 kB
MemFree:       3274576 kB
Buffers:         14232 kB
Cached:         179672 kB
SwapCached:          0 kB
Active:         466276 kB
Inactive:       131568 kB
HighTotal:     3014592 kB
HighFree:      2423068 kB
LowTotal:       881652 kB
LowFree:        851508 kB
SwapTotal:     4305380 kB
SwapFree:      4305380 kB
Dirty:             124 kB
Writeback:           0 kB
AnonPages:      404016 kB
Mapped:          14584 kB
Slab:            11484 kB
SReclaimable:     4552 kB
SUnreclaim:       6932 kB
PageTables:       3096 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   6253500 kB
Committed_AS:  2579232 kB
VmallocTotal:   118776 kB
VmallocUsed:      4528 kB
VmallocChunk:   113764 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
HugePages_Surp:      0
Hugepagesize:     2048 kB

zmcontrol start gives this error:

 Starting clamd.../opt/zimbra/bin/zmclamdctl: line 83: 20647 Segmentation fault      ${zimbra_home}/clamav/bin/freshclam --config-file=${zimbra_home}/conf/freshclam.conf --quiet --daemon --checks=12 >> ${zimbra_log_directory}/freshclam.log 2>&1
failed.

[phoenix]

Originally Posted by tbovingdon

• fsck checks out ok
• trying to "repair" the installation the install tries to install the first .deb and fails (thank god for vm snapshots!)

What happens when you try to re-install, do you get the same segmentation fault? Is it always reproducible? Did you get any other errors in the log files when you try to start Zimbra after the seg fault?

What happened on your machine before the problem started, have you done any updates to ESXi or Ubuntu? Are the VMware tools installed and have they been updated?

When you say 4GB of RAM is that for the whole machine or the Zimbra server? If it's the whole machine, how much RAM does the Zimbra server have?

[tbovingdon]

Ok Installation error was corrupt tar (odd seeing as it was valid when i installed it!)

reinstalling it first time had ldap errors
reinstalling it second time zimbra-spell was still active and after installation completed mysql and spam/antivirus was not working


vmware tools are NOT installed.
nothing has changed on the esxi host to my knowledge
nothing has changed on the ubuntu guest to my knowledge

[phoenix]

..... and the question about the RAM? What errors did you see in the log files when you had the mysql etc. not running?

[tbovingdon]

The 4GB of ram is for the zimbra server there is 20GB of ram on the whole VMware server.

The segmentation fault can be reproduced when trying to start the antivirus.

Which error log should we be looking at? The zmmailboxd.out shows java hotspot errors (as noted in first post)

P.s what exactly is a segment fault.

[phoenix]

Originally Posted by tbovingdon

The 4GB of ram is for the zimbra server there is 20GB of ram on the whole VMware server.

Have any of your other VMs had any problems? Could this be a RAM problem? I don't suppose you could take this machine offline and run a RAM test?

Originally Posted by tbovingdon

The segmentation fault can be reproduced when trying to start the antivirus.

Always?

Originally Posted by tbovingdon

Which error log should we be looking at? The zmmailboxd.out shows java hotspot errors (as noted in first post)

Have a look in the /var/log/maillog and /var/log/zimbra.log for any errors. I'm not a java coder so I can't offer any immediate advice on that error you've seen.

Originally Posted by tbovingdon

P.s what exactly is a segment fault.

Briefly, it occurs when a program attempts to access a memory location that it is not allowed to access or access a memory location in a way that's not allowed (i.e. write to a section of memory that read-only).

[tbovingdon]

None of the VM's seem to be having issues..

this is the only vm on this set of raid discs.. could that be an issue??
looking into checking the ram now..