Mailboxd fails to start

[sfoe]

I just installed Zimbra on my dedicated server to have a good e-mail system for my domains. The install script said everything worked just fine.

If I do zmcontrol status, it tells me that mailboxd is not running. I will then run zmmailboxdctl start and everything appears to work, but the status turns up the same.

It looks as if mailboxd is starting, but then crashes. When I checked the mailboxd.out log, it shows that everytime it checks for status, the PID in the file is stale. I tried to telnet into port 7071, but it refuses the connection.

I'm new to installing/configuring Zimbra; but have been an end-user for some time, which is why I am wanting to use it for my own install.

I would post some logs with this; but there are so many and they are so large, just tell if you need one in particular.

Other than that, I'm at a loss with this.

[irfan]

Welcome to Zimbra Forums!

Stop the zmcontrol.
zmcontrol stop

Then check if any processes are running as zimbra.
ps aux |grep zimbra

If not, then check if there is any stale PID inside in following files. Remove them if exists.
zmmailboxd_java.pid
zmmailboxd_manager.pid

start zmcontrol.
If this does not helps, post the errors from /opt/zimbra/log/zmmailboxd.out file while it crashes.

[sfoe]

I did everything you like was posted, but with the same result. There was an error this time, so here it is. This is the first time I have saw this error, but it might have been in there before. I don't know if this helps or if anyone has an idea, but I really would appreciate the help.

CompilerOracle: exclude com/zimbra/cs/session/SessionMap putAndPrune
CompilerOracle: exclude com/zimbra/cs/mailbox/MailItem delete
0    INFO  [main] log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
Zimbra server reserving server socket port=110 bindaddr=null ssl=false
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Zimbra server reserving server socket port=143 bindaddr=null ssl=false
Zimbra server reserving server socket port=993 bindaddr=null ssl=true
Zimbra server reserving server socket port=7025 bindaddr=null ssl=false
610  WARN  [main] log - Config error at 
610  WARN  [main] log - Config error at 
611  WARN  [main] log - EXCEPTION 
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.mortbay.xml.XmlConfiguration.call(XmlConfiguration.java:534)
	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:244)
	at org.mortbay.xml.XmlConfiguration.refObj(XmlConfiguration.java:638)
	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:252)
	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:206)
	at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:968)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.mortbay.start.Main.invokeMain(Main.java:183)
	at org.mortbay.start.Main.start(Main.java:497)
	at org.mortbay.start.Main.main(Main.java:115)
Caused by: java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
	at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:211)
	... 17 more
612  WARN  [main] log - Nested in java.lang.reflect.InvocationTargetException:
java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
	at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:211)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.mortbay.xml.XmlConfiguration.call(XmlConfiguration.java:534)
	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:244)
	at org.mortbay.xml.XmlConfiguration.refObj(XmlConfiguration.java:638)
	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:252)
	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:206)
	at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:968)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.mortbay.start.Main.invokeMain(Main.java:183)
	at org.mortbay.start.Main.start(Main.java:497)
	at org.mortbay.start.Main.main(Main.java:115)
614  INFO  [Shutdown] log - Shutdown hook executing
614  INFO  [Shutdown] log - Shutdown hook complete

[raj]

Caused by: java.net.BindException: Address already in use

are you sure you are not running something else on the server other than zimbra.?

Raj

[uxbod]

su - zimbra
zmcontrol stop
netstat -an

and post the result please so we can see if anything is being bound to the ports used by Zimbra.