Results 1 to 4 of 4

Thread: jetty - huge logs

  1. #1
    demchenko is offline Member
    Join Date
    Apr 2011
    Location
    Russia
    Posts
    10
    Rep Power
    4

    Default jetty - huge logs

    Hello,
    I have a problem with jetty, its logs getting huge - 20-25Gb for each trace and access log file, thats more than 180Gb a week.
    By looking at contents of it, I presume jetty logging just about every operation with dav.
    However, I dont need such verbosity from it, but it seems I cant decrease log level: I tried to change param "logVerbosityLevel" to "WARN" instead of "DEBUG" in /opt/zimbra/jetty/etc/zimbra.web.xml.in and zimbraAdmin.web.xml.in, then restarted zmmailboxd - but no joy, I still getting such huge and verbose logs.
    How do i decrease verbosity level of jetty?
    Last edited by demchenko; 09-20-2011 at 01:34 AM.

  2. #2
    demchenko is offline Member
    Join Date
    Apr 2011
    Location
    Russia
    Posts
    10
    Rep Power
    4

    Default

    Anyone?

    tried to set "log4j.rootLogger=ERROR,CONSOLE" in /opt/zimbra/jetty/resources/log4j.properties - still no effect

  3. #3
    honmanm is offline New Member
    Join Date
    Feb 2012
    Posts
    3
    Rep Power
    3

    Default likely solution

    We have had similar behaviour... in our case the problem is caused by one client's Lightning calendar repeately requesting the same stuff from Zimbra.

    [BAH: this attempted dodge did not have any effect... just documenting it here as one more thing that doesn't work]

    I tried setting logVerbosityLevel in the jetty config in /opt/zimbra/jetty/etc. I set it in two places, zimbra.web.xml.in, and webdefault.xml.

    You might want to use INFORMATION or WARNING logging level instead of the default DEBUG (note that these names differ from the truncated WARN and INFO used in log4j.properties).

    In zimbra.web.xml.in, the relevant location is
    Code:
        <servlet-class>com.zimbra.webClient.servlet.JspServlet</servlet-class>
        <init-param>
          <param-name>logVerbosityLevel</param-name>
          <param-value>WARNING</param-value>
        </init-param>
    In webdefault.xml, I added an <init-param> section at the end of this list:
    Code:
        <servlet-class>org.mortbay.jetty.servlet.DefaultServlet</servlet-class>
        <init-param>
          <param-name>acceptRanges</param-name>
          <param-value>true</param-value>
        </init-param>
    ...    
        <init-param>
          <param-name>logVerbosityLevel</param-name>
          <param-value>WARNING</param-value>
        </init-param>
    Before getting to this idea, I tried configuring the log output to go to /dev/null, in jetty.xml.in, but the mailbox server was unresponsive unless the logging went to a real file... haven't looked very far into the possibilities there.
    Last edited by honmanm; 09-05-2012 at 09:50 AM. Reason: No joy after reboot

  4. #4
    honmanm is offline New Member
    Join Date
    Feb 2012
    Posts
    3
    Rep Power
    3

    Default brutal e3xperiment for access_log

    [BAH: another false start]

    I then tried to supress the access log file by commenting out or removing the related configuration from jetty.xml.in.
    The configuration is described here: Jetty/Tutorial/RequestLog - Eclipsepedia

    The following blocks of configuration were removed from jetty.xml.in, which appeared to access log file:

    Code:
            <Set name="handler">
              <New id="Handlers" class="org.mortbay.jetty.handler.HandlerCollection">
                <Set name="handlers">
                 <Array type="org.mortbay.jetty.Handler">
                   <Item>
                     <New id="Contexts" class="org.mortbay.jetty.handler.ContextHandlerCollection"/>
                   </Item>
                   <Item>
                     <New id="DefaultHandler" class="org.mortbay.jetty.handler.DefaultHandler"/>
                   </Item>
                   <Item>
                     <New id="RequestLog" class="org.mortbay.jetty.handler.RequestLogHandler"/>
                   </Item>
                 </Array>
                </Set>
    and

    Code:
        <Ref id="RequestLog">
          <Set name="requestLog">
            <New id="RequestLogImpl" class="org.mortbay.jetty.NCSARequestLog">
              <Arg><SystemProperty name="jetty.home" default="."/>/../log/access_log.yyyy_mm_dd</Arg>
              <Set name="logDateFormat">dd/MMM/yyyy:HH:mm:ss Z</Set>
              <Set name="retainDays">30</Set>
              <Set name="append">true</Set>
              <Set name="extended">true</Set>
              <Set name="filenameDateFormat">yyyy-MM-dd</Set>
              <Set name="preferProxiedForAddress">true</Set>
            </New>
          </Set>
        </Ref>
    After that (and obviously a Zimbra restart in between), there is *still* disk space being gobbled up on the drive on which /opt/zimbra is located
    NB these spinning Lightning clients generally go back to spinning after a while, and never mind the log file usage, their associated java instances hog the processor on the Zimbra server... the only real solution is to disable Lightning on the client (at least in our setup).

    And then after a reboot the web interface to mailboxd did not work until these settings had been restored in jetty.xml.in (& Zimbra restarted). That left me back at the starting point, with rapidly growing access.log and trace.log... sigh... groan... bangs head on keyboard.
    Last edited by honmanm; 09-05-2012 at 09:54 AM. Reason: No joy after reboot

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Zimbra Open source - Redo Logs erased
    By AndreGomes in forum Administrators
    Replies: 3
    Last Post: 05-09-2011, 06:56 AM
  2. Jetty access_log off by 10 hours
    By pixelplumber in forum Administrators
    Replies: 2
    Last Post: 12-02-2010, 07:44 PM
  3. Make jetty bind to a specific ip
    By carnold in forum Administrators
    Replies: 9
    Last Post: 04-23-2008, 05:15 PM
  4. Buried in logger logs
    By mcevoys in forum Administrators
    Replies: 6
    Last Post: 08-14-2006, 11:00 PM
  5. Admin Logs not working on 3.1.4
    By blapearce in forum Administrators
    Replies: 1
    Last Post: 08-10-2006, 08:26 PM

Tags for this Thread

Posting Permissions

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