Zimbra

Raiky · #1 (**permalink**) 03-03-2008, 04:21 AM

Hi,

After a week I haven't been able to start the mailbox service. The message is related to mmailboxdctl not running when zmcontrol status is run.
The error that I saw is a java error:
Caused by: java.net.BindException: Address already in use
But do not know what is that port already in use.

Logs: zmmailboxd.out:

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
5356 WARN [main] log - Config error at
5357 WARN [main] log - Config error at
5361 WARN [main] log - EXCEPTION
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.mortbay.xml.XmlConfiguration.call(XmlConfigura tion.java:534)
at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:244)
at org.mortbay.xml.XmlConfiguration.refObj(XmlConfigu ration.java:638)
at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:252)
at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:206)
at org.mortbay.xml.XmlConfiguration.main(XmlConfigura tion.java:968)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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(ServerSock etChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAd aptor.java:59)
at org.mortbay.jetty.nio.SelectChannelConnector.open( SelectChannelConnector.java:211)
... 17 more
5367 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(ServerSock etChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAd aptor.java:59)
at org.mortbay.jetty.nio.SelectChannelConnector.open( SelectChannelConnector.java:211)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.

/var/log/zimbra.log:

Mar 3 07:44:09 luxserver1 zmmailboxdmgr[18405]: status requested
Mar 3 07:44:09 luxserver1 zmmailboxdmgr[18405]: stale pid 5345 found in /opt/zimbra/log/zmmailboxd.pid: No such process
Mar 3 07:44:09 luxserver1 zmmailboxdmgr[18405]: assuming no other instance is running

Sometimes this (mailboxd) works for just 30 seconds or so, then a message saying the daemon exited twice appears.

I'm going to reinstall the system again and then try, please help me if you know what is wrong.

Thank you.
Raiky

phoenix · #2 (**permalink**) 03-03-2008, 04:59 AM

Quote:

Originally Posted by Raiky

I'm going to reinstall the system again and then try, please help me if you know what is wrong.

You've already answered your own question, the port is in use. Do you have another mailserver running or is the Zimbra proxy running? If either of those is true then get rid of the service and restart Zimbra.

Raiky · #3 (**permalink**) 03-03-2008, 05:33 AM

Hi,

Thanks for your reply.

The question is: what is that port in conflict? I haven't found any other server running so far.

Where could I increase the log level? Perhaps we will have more information.

Thx
R.

phoenix · #4 (**permalink**) 03-03-2008, 05:46 AM

Check if the proxy is running by doing this:

Code:

zmproxyctl status

and if it's running, do this

Code:

zmproxyctl stop

the restart Zimbra. When Zimbra starts, go to the Admin UI and disable the proxy on the Servers//Services tab - uncheck the "Imap and Pop proxy" option (and save the settings). Let's see if that's the problem, first.

Raiky · #5 (**permalink**) 03-03-2008, 06:20 AM

Hi,

Proxy status shows that "is not working". So it should not be a problem.

For the Adminstrator UI . Shall I go to:
https://server1.example.com:7071/zimbraAdmin/ ??

It does not work, I mean there is no 7071 port open.

By the way this is Debian 4.0 etch and the Zimbra is the open source version from last week.

Thx.
Raiky.

aynema · #6 (**permalink**) 03-03-2008, 06:53 AM

I'm having the same problem it seems. It was running fine for a few weeks until I restarted my server today then this showed up.
I'm running on zcs- 5.0.2_GA_1965.RHEL5.200801030221917 on Centos 5.1
I can't see anything in any of the logs other than the same socket in use message but can't see anything that is using any of the sockets I've also tried re-installing and even wiping it clean and installing again (Lucky I haven't put this box into production yet) any help would be usefull