Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-17608

include request.log in support bundle if location is customized

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 3.12.1, 2.14.9, 2.14.19
    • Support Tools
    • n/a

    Description

      I've seen several tickets now where the request.log is missing.  In all cases, examining logback-access.xml shows the request.log location has been overridden, as in:

      <?xml version='1.0' encoding='UTF-8'?>
      <configuration>
        <appender name="request.logfile" class="ch.qos.logback.core.rolling.RollingFileAppender">
          <File>/var/log/nexus/request.log</File>
          <Append>true</Append>
          <encoder class="org.sonatype.nexus.pax.logging.AccessPatternLayoutEncoder">
            <pattern>%clientHost %l %user [%date] "%requestURL" %statusCode %bytesSent %elapsedTime "%header{User-Agent}"</pattern>
          </encoder>
          <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
            <fileNamePattern>/var/log/nexus/request-%d{yyyy-MM-dd}.log.gz</fileNamePattern>
            <maxHistory>7</maxHistory>
          </rollingPolicy>
        </appender>
      
        <appender-ref ref="request.logfile"/>
      </configuration>
      

       The request.log is of vital importance when diagnosing customer issues.  The support zip should be able to read it when it's location is changed.

       While this affects both Nexus 2.x and Nexus 3.x, Nexus 3.x is the priority.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              rseddon Rich Seddon
              Rich Seddon Rich Seddon
              Votes:
              4 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:

                tigCommentSecurity.panel-title