mysql won't start on install of zimbra

[bpm]

Hi all,

I did an install of zimbra 6.0.6 on Ubuntu 8.0.4 and everything worked out well except the "unable to verify the mx record". Bypassing this, the install worked perfectly until I did a "zmcontrol status" (see below). I also have bind9 working on the server as normal, resolving the A and MX records to my local LAN IP and tested from a PC.

zimbra@mail:~$ zmcontrol status
Host mail.mydomain.com
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Stopped
mysql.server is not running.
mta Running
snmp Running
spell Running
stats Stopped
zimbra@mail:~$

Can anyone help troubleshoot?

[phoenix]

Originally Posted by bpm

I did an install of zimbra 6.0.6 on Ubuntu 8.0.4 and everything worked out well except the "unable to verify the mx record". Bypassing this, the install worked perfectly until I did a "zmcontrol status" (see below). I also have bind9 working on the server as normal, resolving the A and MX records to my local LAN IP and tested from a PC.

With the MX record error message the install didn't work 'perfectly', you need a valid hosts file (see the Quick Start Installation Guide) and an A & MX records pointing to your server. You need to check that from the ZImbra server itself, make sure that AppArmor & the firewall are disabled and search the forums for how to diagnose this problem (it's been covered many times). If your DNS A & MX records are correct (make sure you post the diagnostic information here for confirmation) then check the log files for errors when you start Zimbra.

[bpm]

Thanks for that. I've already verified that the hosts file is correct and it works from the zimbra server itself. I was not aware about AppArmor so have now disabled it. The firewall is also disabled and I'm rebooting the server at the moment to check again.

I've already gone through the standard tests from previous posts and all came back as normal, hence my post.

Will see how it goes after the reboot.

[phoenix]

Originally Posted by bpm

I've already gone through the standard tests from previous posts and all came back as normal, hence my post.

I understand that but the DNS tests need to run on the Zimbra server and you need to post the output here for verification.

[bpm]

ok will do

[bpm]

Results :


bpm@mail:~$ cat /etc/hosts
127.0.0.1 localhost
#127.0.1.1 mail.mydomain.com mail
192.168.0.249 mail.mydomain.com mail

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
bpm@mail:~$
bpm@mail:~$ cat /etc/resolv.conf
search mydomain.com
nameserver 127.0.0.1
bpm@mail:~$
bpm@mail:~$ dig mydomain.com mx

; <<>> DiG 9.4.2-P2.1 <<>> mydomain.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42176
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;mydomain.com. IN MX

;; ANSWER SECTION:
mydomain.com. 604800 IN MX 10 mail.mydomain.com.

;; AUTHORITY SECTION:
mydomain.com. 604800 IN NS ns.d-y.p.com.

;; ADDITIONAL SECTION:
mail.mydomain.com. 604800 IN A 192.168.0.249

;; Query time: 62 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue May 25 16:07:24 2010
;; MSG SIZE rcvd: 87

bpm@mail:~$
bpm@mail:~$ dig mydomain.com any

; <<>> DiG 9.4.2-P2.1 <<>> mydomain.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64852
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;mydomain.com. IN ANY

;; ANSWER SECTION:
mydomain.com. 604800 IN SOA ns.mydomain.com. root.mydomain.com. 2010190504 28800 3600 604800 38400
mydomain.com. 604800 IN NS ns.d-y.p.com.
mydomain.com. 604800 IN MX 10 mail.mydomain.com.

;; ADDITIONAL SECTION:
mail.mydomain.com. 604800 IN A 192.168.0.249

;; Query time: 80 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue May 25 16:07:51 2010
;; MSG SIZE rcvd: 131

bpm@mail:~$
bpm@mail:~$ host `hostname`
mail.mydomain.com has address 192.168.0.249
bpm@mail:~$

[phoenix]

You hosts file should contain the following line (not the format you have):

127.0.0.1 localhost.localdomain localhost

Change that, restart Zimbra and see if there's any errors in the log files.

[bpm]

I tried that and had no joy. I then rebuilt the system from being a VMWare with Ubuntu to just Ubunto on its own. I then reinstalled bind9 and Zimbra and all worked first time.

I'm guessing it had something to do with the hostname as I used a FQDN this time and only a servername of "mail" the first time around which I then renamed to a FQDN.

Thanks for all your help Phoenix.