https://server.domain.com:7071/

[ralf2201]

Hi,

this is my first question here. I think it will not be the last one.

My setup: Debian Lenny + zcs-6.0.8_GA_2661.DEBIAN5.20100820040222.tgz

The installation runs very well witout any comment, but after that i would like to log in as admin to my webpage an there is something wrong. Firefox can not find the page. Is there a way to check what is going on.

Thanks.

Ralf

[phoenix]

When asking for help, you need to post a bit more information than 'it doesn't work'.

You should start by updating your forum profile with the output of the following command (do not post the output in this thread):

zmcontrol -v

What error messages do you get? Are all the Services running? Have you searched the forums for similar problems? Did you try the solutions that you found (most questions/problems have already been asked and answered)? What errors do you see in the log files? etc. etc. etc.

[ralf2201]

one service is not running

zmmailboxdctl is not running

in which log file should i look for the error

[ralf2201]

could this be a problem

mailbox.log


2010-09-01 12:50:58,476 WARN [main] [] log - No value for env-entry-name trustedIPs
2010-09-01 12:50:58,477 INFO [main] [] log - No Transaction manager found - if your webapp requires one, please configure one.
2010-09-01 12:50:59,058 WARN [main] [] log - No value for env-entry-name trustedIPs
2010-09-01 12:50:59,059 INFO [main] [] log - No Transaction manager found - if your webapp requires one, please configure one.
2010-09-01 12:50:59,268 INFO [main] [] log - No Transaction manager found - if your webapp requires one, please configure one.
2010-09-01 12:50:59,392 INFO [main] [] log - Opened /opt/zimbra/jetty-6.1.22.z6/logs/access_log.2010-09-01
2010-09-01 12:50:59,398 INFO [main] [] log - Started SelectChannelConnector@0.0.0.0:80
2010-09-01 12:50:59,401 INFO [main] [] log - Started SslSelectChannelConnector@0.0.0.0:7071
2010-09-01 12:50:59,402 INFO [main] [] log - Started SelectChannelConnector@0.0.0.0:7072

[phoenix]

Originally Posted by ralf2201

zmmailboxdctl is not running

Then you should look in the log files and see what the error is when you start Zimbra.

[ralf2201]

i think i got a error in the mailbox.log

2010-09-01 13:26:21,672 WARN [main] [] log - No value for env-entry-name trustedIPs
2010-09-01 13:26:21,673 INFO [main] [] log - No Transaction manager found - if your webapp requires one, please configure one.
2010-09-01 13:26:22,584 WARN [main] [] log - No value for env-entry-name trustedIPs
2010-09-01 13:26:22,604 INFO [main] [] log - No Transaction manager found - if your webapp requires one, please configure one.
2010-09-01 13:26:23,240 INFO [main] [] log - No Transaction manager found - if your webapp requires one, please configure one.
2010-09-01 13:26:23,503 WARN [main] [] log - failed org.mortbay.jetty.servlet.HashSessionManager@1c833 54: java.lang.OutOfMemoryError: unable to create new native thread
2010-09-01 13:26:23,503 WARN [main] [] log - failed SessionHandler@a1fdd8: java.lang.OutOfMemoryError: unable to create new native thread
2010-09-01 13:26:23,503 WARN [main] [] log - failed org.mortbay.jetty.webapp.WebAppContext@dec87{/zimlet,/opt/zimbra/jetty-6.1.22.z6/webapps/zimlet}: java.lang.OutOfMemoryError: unable to create new native thread
2010-09-01 13:26:23,503 WARN [main] [] log - failed ContextHandlerCollection@120a48c: java.lang.OutOfMemoryError: unable to create new native thread
2010-09-01 13:26:23,505 INFO [main] [] log - Opened /opt/zimbra/jetty-6.1.22.z6/logs/access_log.2010-09-01
2010-09-01 13:26:23,505 WARN [main] [] log - failed HandlerCollection@12ee2a: java.lang.OutOfMemoryError: unable to create new native thread
2010-09-01 13:26:23,505 WARN [main] [] log - failed RewriteHandler@d210ab: java.lang.OutOfMemoryError: unable to create new native thread
2010-09-01 13:26:23,505 WARN [main] [] log - failed DebugHandler@1445748: java.lang.OutOfMemoryError: unable to create new native thread
2010-09-01 13:26:23,506 ERROR [main] [] log - Error starting handlers
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:597)
at java.util.Timer.<init>(Timer.java:154)
at java.util.Timer.<init>(Timer.java:122)
at org.mortbay.jetty.servlet.HashSessionManager.doSta rt(HashSessionManager.java:71)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
at org.mortbay.jetty.servlet.SessionHandler.doStart(S essionHandler.java:116)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
at org.mortbay.jetty.handler.ContextHandler.startCont ext(ContextHandler.java:537)
at org.mortbay.jetty.servlet.Context.startContext(Con text.java:136)
at org.mortbay.jetty.webapp.WebAppContext.startContex t(WebAppContext.java:1250)
at org.mortbay.jetty.handler.ContextHandler.doStart(C ontextHandler.java:517)
at org.mortbay.jetty.webapp.WebAppContext.doStart(Web AppContext.java:467)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerCollection.doStar t(HandlerCollection.java:152)
at org.mortbay.jetty.handler.ContextHandlerCollection .doStart(ContextHandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerCollection.doStar t(HandlerCollection.java:152)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
at org.mortbay.jetty.handler.DebugHandler.doStart(Deb ugHandler.java:127)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at org.mortbay.setuid.SetUIDServer.doStart(SetUIDServ er.java:158)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
at org.mortbay.xml.XmlConfiguration.main(XmlConfigura tion.java:985)
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:194)
at org.mortbay.start.Main.start(Main.java:534)
at org.mortbay.start.Main.start(Main.java:441)
at org.mortbay.start.Main.main(Main.java:119)

[phoenix]

How much RAM is installed on this server? Is it a VM or real hardware?

[ralf2201]

it is a vserver from a host that run on Virtuozzo 4. 512 MB Ram fix. 1024 MB dynamic RAM.

[phoenix]

Originally Posted by ralf2201

it is a vserver from a host that run on Virtuozzo 4.

That's not a supported platform and you may have problems with Zimbra in that environment or you may not.

Originally Posted by ralf2201

512 MB Ram fix. 1024 MB dynamic RAM.

That's below the recommended minimum, I'd recommend at least 1GB of fixed RAM.

Tha lack of RAM would explain the following errors:

2010-09-01 13:26:23,503 WARN [main] [] log - failed org.mortbay.jetty.servlet.HashSessionManager@1c833 54: java.lang.OutOfMemoryError: unable to create new native thread
2010-09-01 13:26:23,503 WARN [main] [] log - failed SessionHandler@a1fdd8: java.lang.OutOfMemoryError: unable to create new native thread
2010-09-01 13:26:23,503 WARN [main] [] log - failed org.mortbay.jetty.webapp.WebAppContext@dec87{/zimlet,/opt/zimbra/jetty-6.1.22.z6/webapps/zimlet}: java.lang.OutOfMemoryError: unable to create new native thread