Fresh installation: mysql.server is not working

[Alphaphi]

Hello everyone,

on a fresh debian lenny installation I installed zcs-6.0.10. There is nothing configured yet except what the installation process wants me to configure. The result is:

$ zmcontrol status
Host zimbra.company.lan
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Stopped
mysql.server is not running.
mta Running
snmp Running
spell Running
stats Stopped

In consequence I cannot see the login page in my browser.

From a client in the network:

~> nmap zimbra.company.lan
[...]
22/tcp open ssh
25/tcp open smtp
80/tcp open http
110/tcp open pop3
143/tcp open imap
389/tcp open ldap
465/tcp open smtps
587/tcp open submission
993/tcp open imaps
995/tcp open pop3s
7025/tcp open unknown

We see that there is something listening on port 80, but as said no page is delivered.

Can anyone give me a hint?

Thanks!
Andre

[phoenix]

Originally Posted by Alphaphi

on a fresh debian lenny installation I installed zcs-6.0.10. There is nothing configured yet except what the installation process wants me to configure.

How about looking in the log files for any errors.

I assume this is the Open Source version you're installing on Debian? If I were you I'd pick another distribution as Debian is deprecated (as are the 32bit binary versions) in the next major release of Zimbra 7.

[Alphaphi]

Originally Posted by phoenix

How about looking in the log files for any errors.

Well, this is of course a good idea, but didn't help much in this situation. I have it now up and running, and the solution was to set the mx records to be correct at install time, say: to a value that zimbra considers to be correct, and then reinstall zimbra.
I had a similar problem some time ago with another installation, and I wonder how special zimbra is about the DNS settings. How can wrong DNS settings be a reason not to start the mysql-server...

Originally Posted by phoenix

I assume this is the Open Source version you're installing on Debian? If I were you I'd pick another distribution as Debian is deprecated (as are the 32bit binary versions) in the next major release of Zimbra 7.

You assume right. Well, the problem here is that the Zimbra machine is running inside a 32bit vmware environment, where I cannot install a 64bit guest OS.
And the debian was the OS that installed easiest inside the vmware.

Some time in the future I will move the server to run a 64bit kvm, and then I can give the zimbra a 64bit OS as a kvm guest. Hopefully this is not a problem to update then.
(Have you done this before - is this step possible?)

Thanks for your feedback!
Andre

[phoenix]

Originally Posted by Alphaphi

Well, this is of course a good idea, but didn't help much in this situation. I have it now up and running, and the solution was to set the mx records to be correct at install time, say: to a value that zimbra considers to be correct, and then reinstall zimbra.
I had a similar problem some time ago with another installation, and I wonder how special zimbra is about the DNS settings. How can wrong DNS settings be a reason not to start the mysql-server...

It's imperative that you have a correct /etc/hosts file and valid DNS A & MX records as mentioned in the Quick Start Installation Guide and detailed in the Split DNS article and you can check that by reading the 'Verify....' section of that article.

Originally Posted by Alphaphi

You assume right. Well, the problem here is that the Zimbra machine is running inside a 32bit vmware environment, where I cannot install a 64bit guest OS.
And the debian was the OS that installed easiest inside the vmware.

Some time in the future I will move the server to run a 64bit kvm, and then I can give the zimbra a 64bit OS as a kvm guest. Hopefully this is not a problem to update then.
(Have you done this before - is this step possible?)

Yes, it can be migrated to a new architecture and there are plenty of articles and threads that cover those steps: site:zimbra.com +32bit +64bit +solved - Yahoo! Search Results