zimbra services not starting

[bluethundr_]

My Zimbra server has been running reliably for over a week at this point.

Then I did a zmcontrol status and noticed that the stats service wasn't running.

I tried doing a zmcontrol startup several times but the service would not start. Running the startup control is deceptive here because I did not encounter any error messages.

zimbra@cloud3:~$ zmcontrol startup
Host cloud3.jiffycloud.com
	Starting logger...Done.
	Starting mailbox...Done.
	Starting memcached...Done.
	Starting antispam...Done.
	Starting antivirus...Done.
	Starting snmp...Done.
	Starting spell...Done.
	Starting mta...Done.
	Starting stats...Done.

So then I bounced the server. After that NONE of the zimbra services would start using the zmcontrol command. I then, in a last ditch effort, performed an in-place-upgrade of the zimbra version that was already there just to get it running.

That at least brought the zimbra server up again. However now several MORE zimbra services are now no longer running.

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

Even after more attempts at zmcontrol start (which seems to work as you run the command) none of the services actually do start.

I must be doing something wrong here. Is there an article I can reference or just some sound advice out there that could help resolve this confusion?

[uxbod]

Check /var/log/zimbra.log for any error messages and also post

cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain mx
dig yourdomain any
host `hostname` <- note backticks and not single quotes

[bluethundr_]

[root@cloud3:~ ] #:cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
10.249.74.116 cloud3.newdom.com cloud3
123.45.678.91 newdom.com 

# 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

[root@cloud3:~ ] #:cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search compute-1.internal

[root@cloud3:~ ] #:dig newdom.com mx

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

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

;; ANSWER SECTION:
newdom.com.		604800	IN	MX	0 cloud3.newdom.com.

;; AUTHORITY SECTION:
newdom.com.		604800	IN	NS	cloud3.newdom.com.

;; ADDITIONAL SECTION:
cloud3.newdom.com.	604800	IN	A	10.249.74.116

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon May 17 13:53:38 2010
;; MSG SIZE  rcvd: 85

[root@cloud3:~ ] #:dig newdom.com any

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

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

;; ANSWER SECTION:
newdom.com.		604800	IN	SOA	cloud3.newdom.com. admin.newdom.com. 5131001 604800 86400 2419200 604800
newdom.com.		604800	IN	NS	cloud3.newdom.com.
newdom.com.		604800	IN	MX	0 cloud3.newdom.com.
newdom.com.		604800	IN	A	10.249.74.116

;; ADDITIONAL SECTION:
cloud3.newdom.com.	604800	IN	A	10.249.74.116

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon May 17 13:54:33 2010
;; MSG SIZE  rcvd: 143

[root@cloud3:~ ] #:host `hostname`
cloud3.newdom.com has address 10.249.74.116