Hi Peter-
The hostmanager error can be ignored.
If the error is on port 110, then you have to stop what ever is already bound to port 110. Did you happen to turn on IMAP/POP proxy? If you turn it on in a single server enviroment, it can cause tomcat to go down. Try:
su - zimbra
zmperditionctl stop
tomcat start
and see if it comes back up. If not, then you need to track down what is binding. Try:
lsof | grep TCP
and look for port 110, and the file associated with it.
You can also find out which Zimbra version you're running by running:
su - zimbra
zmcontrol -v
Best,
john |