I have a Zimbra server that has been running for about three months now. Yesterday on trying to collect mail from it there was no response from the web server at the normal address. Checking the server showed that it would not respond to either ssh (no route to host) or a ping (Destination unreachable). At this point perhaps I should mention the server is running as a Xen virtual machine. Trying to connect to the Xen console just gives a blank screen. Trying to reboot or shutdown the machine does not work and I was eventally forced to force the machine to shutdown (pull the virtual plug).
When the server is restarted it starts until the zimbra service has been starting for approximately two to three minutes and then the machine hangs again. Any connection to the console or ssh then locks up. Once again the machine is then completely unresponsive.
I have taken the zimbra service out of the various run levels and the machine starts and stays up overnight but as soon as the zimbra service is started the machine locks up again.
I have tried starting the ldap service on its own (since this is the first service to start) and this gives exactly the same result - locking up the machine.
I tried this this morning and then restarted the machine first thing this evening. /var/log/messages contains multiple occurrences of the following message:
Sep 13 08:34:05 mta001 kernel: 4gb seg fixup, process slapd (pid 2982), cs:ip 73
and this is the last message before the machine hung and the next message show the machine restarting this evening.
I'm not sure if this is relevant or not.
Can anyone suggest in the first instance where to look to discover what is the problem? I am assuming the problem is with zimbra but don't know where to look to find out what the problem is. I have tried checking /opt/zimbra/log/startup.log but this doesn't exist once the machine has restarted.
Can anyone help? Where should I look first?