Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Strange Problems with Zimbra Web Interface

  1. #11
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,201
    Rep Power
    56

    Default

    Quote Originally Posted by denson View Post
    I installed the latest patch, but the situation has not changed, still the same problem.
    Then you're going to have to give some more information other than 'the same problem'. What, exactly, if the problem you're experiencing? You did follow the install instructions in the patch release notes (that involved running three commands after applying the patch) didn't you? What's the specification of the hardware (including the installed RAM)? Is it a VM and if so, which platform?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  2. #12
    denson is offline New Member
    Join Date
    Jun 2011
    Posts
    4
    Rep Power
    3

    Default

    Yes, this virtual machine, installed vmvare Server 2.0, memory for the virtual machine 6 GB, Zimbra installed on Ubuntu Server 8.4 32 bit, upgraded from version 6, to 7.0 to 7.1

    I quote from the first post

    Problems reported from users and seen with my own eyes were (it is always just the web ui that is affected!):
    - not possible to login (while IMAP, etc. works) or
    - not possible to create a calendar entry or
    - not possible to create a new email message or
    - admin web ui does not load (not even the login screen)

    and logs are exactly the same
    Last edited by denson; 08-04-2011 at 02:29 AM.
    Release 7.1.1_GA_3196.UBUNTU8 UBUNTU8 FOSS edition.

  3. #13
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,201
    Rep Power
    56

    Default

    Quote Originally Posted by denson View Post
    Yes, this virtual machine, installed vmvare Server 2.0, memory for the virtual machine 6 GB, Zimbra installed on Ubuntu Server 8.4 32 bit, upgraded from version 6, to 7.0 to 7.1
    I also asked if you ran the all the commands after installing the patch, did you?

    Quote Originally Posted by denson View Post
    I quote from the first post
    The problem with quoting from the original post is that's a different release of Zimbra to the one you're using, you're going to have to provide some corroboration from the log files that you have the same problem.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  4. #14
    denson is offline New Member
    Join Date
    Jun 2011
    Posts
    4
    Rep Power
    3

    Default

    Yes, I used all commands

    Log

    Code:
    2011-08-04 09:22:52,734 WARN  [btpool0-14] [] log - /zimbraAdmin/
    java.io.IOException: Permission denied
            at sun.nio.ch.FileChannelImpl.map0(Native Method)
            at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:734)
            at org.mortbay.io.nio.DirectNIOBuffer.<init>(DirectNIOBuffer.java:70)
            at org.mortbay.jetty.servlet.DefaultServlet$NIOResourceCache.fill(DefaultServlet.java:1000)
            at org.mortbay.jetty.ResourceCache.load(ResourceCache.java:198)
            at org.mortbay.jetty.ResourceCache.lookup(ResourceCache.java:166)
            at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:411)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:705)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:814)
            at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
            at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
            at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218)
            at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
            at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
            at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:422)
            at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:330)
            at org.mortbay.jetty.servlet.Dispatcher.error(Dispatcher.java:135)
            at org.mortbay.jetty.servlet.ErrorPageErrorHandler.handle(ErrorPageErrorHandler.java:129)
            at org.mortbay.jetty.Response.sendError(Response.java:274)
            at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:475)
            at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218)
            at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
            at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
            at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:422)
            at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
            at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
            at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
            at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
            at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
            at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
            at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
            at org.mortbay.jetty.Server.handle(Server.java:326)
            at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543)
            at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:929)
            at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
            at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
            at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
            at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
            at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
    Release 7.1.1_GA_3196.UBUNTU8 UBUNTU8 FOSS edition.

  5. #15
    CrypTom is offline Project Contributor
    Join Date
    Aug 2006
    Posts
    33
    Rep Power
    8

    Default

    We've upgraded to Zimbra 7.1.2 FOSS Ubuntu8 (32-bit) and we are still experiencing the same problems are mentioned in my first post, several times a day.

    At this very moment, Zimbra Webmail works, but I can't login to the admin interface as the page does not even show up (page stays white, no error message displayed).

    When I hit the browser's reload-button the logfiles (in /opt/zimbra/log) that are updated are the following:
    • mailbox.log
    • 2011_08_14.trace.log
    • access_log.2011-08-14
    • zmmailboxd.out


    /opt/zimbra/log/mailbox.log:
    Code:
    2011-08-14 20:45:08,314 INFO  [btpool0-84://localhost:7071/service/admin/soap/GetDomainInfoRequest] [ip=127.0.0.1;ua=ZCS/7.1.2_GA_3268;] soap - GetDomainInfoRequest
    2011-08-14 20:45:08,319 WARN  [btpool0-83://mail.mydomain.tld:7071/zimbra
    Admin/] [] log - /zimbraAdmin/: java.io.IOException: Permission denied
    2011-08-14 20:45:08,320 WARN  [btpool0-83] [] log - /zimbraAdmin/
    java.io.IOException: Permission denied
            at sun.nio.ch.FileChannelImpl.map0(Native Method)
            at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:734)
            at org.mortbay.io.nio.DirectNIOBuffer.<init>(DirectNIOBuffer.java:70)
            at org.mortbay.jetty.servlet.DefaultServlet$NIOResourceCache.fill(Defaul
    tServlet.java:1000)
            at org.mortbay.jetty.ResourceCache.load(ResourceCache.java:198)
            at org.mortbay.jetty.ResourceCache.lookup(ResourceCache.java:166)
            at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:41
    1)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:705)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:814)
            at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511
    )
            at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
            at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218)
            at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
            at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
            at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:422)
            at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:330)
            at org.mortbay.jetty.servlet.Dispatcher.error(Dispatcher.java:135)
            at org.mortbay.jetty.servlet.ErrorPageErrorHandler.handle(ErrorPageErrorHandler.java:129)
            at org.mortbay.jetty.Response.sendError(Response.java:274)
            at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:475)
            at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218)
            at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
            at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
            at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:422)
            at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
            at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
            at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
            at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
            at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
            at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
            at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
            at org.mortbay.jetty.Server.handle(Server.java:326)
            at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543)
            at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:929)
            at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
            at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
            at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
            at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
            at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
    2011-08-14 20:45:08,501 INFO  [btpool0-85://localhost:7071/service/admin/soap/GetDomainInfoRequest] [ip=127.0.0.1;ua=ZCS/7.1.2_GA_3268;] soap - GetDomainInfoRequest
    2011_08_14.trace.log:
    Code:
    20:45:08.307:btpool0-83://mail.mydomain.tld:7071/zimbraAdmin/ 212.41.104.236 GET ZA_SKIN=carbon; ZA_TEST=true; ZM_TEST=true; JSESSIONID=gqs0r3i9xitn; ZM_AUTH_TOKEN=0_fe77aceaee6f28e8cb24898074bdcff286b16668_69643d33363a39353334373934372d333834622d346638392d393735622d3636633938383062353064633b6578703d31333a313331333531393036333137323b747970653d363a7a696d6272613b; Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 Iceweasel/5.0
    20:45:08.311:btpool0-84://localhost:7071/service/admin/soap/GetDomainInfoRequest 127.0.0.1 POST null; ZCS 7.1.2_GA_3268
    20:45:08.315:btpool0-84://localhost:7071/service/admin/soap/GetDomainInfoRequest 200 text/xml; charset=utf-8 368
    20:45:08.315:btpool0-85://mail.mydomain.tld/service/soap/SaveDraftRequest 81.62.83.131 POST __utma=37539894.1152753001.1313346452.1313346452.1313346452.1
    ; __utmb=37539894.1.10.1313346452; __utmc=37539894; __utmz=37539894.1313346452.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); ZM_TEST=true; ZM_AUTH_TOKEN=0_
    c6496f6e3e80120aa7a343ef7bd1b3490c0e79d5_69643d33363a39366236616234382d366533352d346631382d616365342d6239623932323166346131303b6578703d31333a313331333531393332363438383b747970653d363a7a696d6272613b; Mozilla/5.0 (Windows; U; Windows NT 5.1; 
    de; rv:1.9.2.18) Gecko/20110614 Firefox/3.6.18 (.NET CLR 3.5.30729)
    20:45:08.320:btpool0-83://mail.mydomain.tld:7071/zimbraAdmin/ 500 text/html; charset=ISO-8859-1 0/java.io.IOException: Permission denied
    20:45:08.483:btpool0-83://mail.mydomain.tld:7071/favicon.ico 212.41.104.236 GET ZM_TEST=true; JSESSIONID=gqs0r3i9xitn; ZM_AUTH_TOKEN=0_fe77aceaee6f28e8cb24898074bdcff286b16668_69643d33363a39353334373934372d333834622d346638392d393735622d3636633938383062353064633b6578703d31333a313331333531393036333137323b747970653d363a7a696d6272613b; Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 Iceweasel/5.0
    20:45:08.497:btpool0-85://mail.mydomain.tld/service/soap/SaveDraftRequest 200 text/javascript; charset=utf-8 2522
    20:45:08.498:btpool0-85://localhost:7071/service/admin/soap/GetDomainInfoRequest 127.0.0.1 POST null; ZCS 7.1.2_GA_3268
    20:45:08.501:btpool0-85://localhost:7071/service/admin/soap/GetDomainInfoRequest 200 text/xml; charset=utf-8 368
    20:45:08.505:btpool0-83://mail.mydomain.tld:7071/favicon.ico 404 text/html; charset=utf-8 1331
    access_log.2011-08-14:
    Code:
    127.0.0.1 -  -  [14/Aug/2011:18:45:08 +0000] "POST /service/admin/soap/GetDomainInfoRequest HTTP/1.1" 200 368 "-" "ZCS 7.1.2_GA_3268"
    127.0.0.1 -  -  [14/Aug/2011:18:45:08 +0000] "POST /service/admin/soap/GetDomainInfoRequest HTTP/1.1" 200 368 "-" "ZCS 7.1.2_GA_3268"
    212.41.104.236 -  -  [14/Aug/2011:18:45:08 +0000] "GET /favicon.ico HTTP/1.1" 404 1331 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 Iceweasel/5.0"
    zmmailboxd.out (I don't know exactly how many lines like the following...):
    Code:
    Total time for which application threads were stopped: 0.0001020 seconds
    My Zimbra Version (can't find the User CP field to update at the moment):
    Release 7.1.2_GA_3268.UBUNTU8 UBUNTU8 FOSS edition.

  6. #16
    CrypTom is offline Project Contributor
    Join Date
    Aug 2006
    Posts
    33
    Rep Power
    8

    Default

    Ah, I found out that sometimes (not always) there is a hs_err_pidXYZ.log created, when the problems appear:

    Code:
    #
    # There is insufficient memory for the Java Runtime Environment to continue.
    # Native memory allocation (malloc) failed to allocate 1256608 bytes for Chunk::new
    # Possible reasons:
    #   The system is out of physical RAM or swap space
    #   In 32 bit mode, the process size limit was hit
    # Possible solutions:
    #   Reduce memory load on the system
    #   Increase physical memory or swap space
    #   Check if swap backing store is full
    #   Use 64 bit Java on a 64 bit OS
    #   Decrease Java heap size (-Xmx/-Xms)
    #   Decrease number of Java threads
    #   Decrease Java thread stack sizes (-Xss)
    #   Set larger code cache with -XX:ReservedCodeCacheSize=
    # This output file may be truncated or incomplete.
    #
    #  Out of Memory Error (allocation.cpp:317), pid=9633, tid=128093072
    #
    # JRE version: 6.0_26-b03
    # Java VM: Java HotSpot(TM) Server VM (20.1-b02 mixed mode linux-x86 )
    
    ---------------  T H R E A D  ---------------
    
    Current thread (0x07e3ac00):  JavaThread "C2 CompilerThread1" daemon [_thread_in_native, id=9646, stack(0x079a8000,0x07a29000)]
    
    Stack: [0x079a8000,0x07a29000],  sp=0x07a25f40,  free space=503k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    V  [libjvm.so+0x7248b0]
    I've got nagios checks running, I never see problems with too less RAM (I've got 10GB) or swap space being used (always 0%).

    My system is 32-bit, so what can I do to prevent "the process size limit was hit"? Thanks for any help.

    CrypTom

    My zimbra version:
    Release 7.1.2_GA_3268.UBUNTU8 UBUNTU8 FOSS edition.

  7. #17
    CrypTom is offline Project Contributor
    Join Date
    Aug 2006
    Posts
    33
    Rep Power
    8

    Default

    Hi again

    I found a solution that seems to work (at least up to now):

    I found the following forum post:
    [SOLVED] Memory Upgrade --> MTA Error

    As my zimbra server is a 32-bit system with 10GB of RAM, I tried reducing the heap size to 25% as suggested without success. After realizing that the example in the mentioned post is calculated for 8GB of RAM, I set the values down to 20%.

    mailboxd_java_heap_memory_percent is deprecated as of zimbra 7, but there are 2 new config options according to Performance Tuning Guidelines for Large Deployments - Zimbra :: Wiki

    So I set to following values and got rid of these annoying problems:

    Code:
    zmlocalconfig -e mailboxd_java_heap_size=1500
    zmlocalconfig -e mysql_memory_percent=20
    zmlocalconfig -e mailboxd_java_heap_new_size_percent=20
    Thanks for you support!

Page 2 of 2 FirstFirst 12

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. ZCS7 Beta only Listens on IPv6
    By tobru in forum Installation
    Replies: 2
    Last Post: 03-25-2011, 03:31 AM
  2. Did I miss something? (Zimbra GA 6.0.8 on Ubuntu 10.04)
    By vpetersson in forum Installation
    Replies: 2
    Last Post: 10-26-2010, 06:29 AM
  3. Zimbra shutdowns every n hours.
    By Andrewb in forum Administrators
    Replies: 13
    Last Post: 08-14-2007, 08:55 AM
  4. 3.1 on FC4 problems
    By cohnhead in forum Installation
    Replies: 8
    Last Post: 05-26-2006, 11:16 AM
  5. Zimbra server crashed
    By goetzi in forum Administrators
    Replies: 6
    Last Post: 03-25-2006, 01:00 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •