com.atlassian.bitbucket.internal.ssh.server.SelfClosingChannelSession log messages

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 4.3.3, 4.4.2, 4.5.1
    • Affects Version/s: 4.3.0
    • Component/s: Git Hosting
    • None

      Symptoms

      com.atlassian.bitbucket.internal.ssh.server.SelfClosingChannelSession generates a lot of log messages:

      E.g.

      2016-03-04 06:18:44,739 INFO  [NioProcessor-8]  c.a.b.i.s.s.SelfClosingChannelSession Executing command: git-upload-pack '/foo/bar.git'
      2016-03-04 06:18:45,506 INFO  [NioProcessor-9]  c.a.b.i.s.s.SelfClosingChannelSession Executing command: git-upload-pack '/bar/baz.git'
      

      Workaround

      Permanently adjusting the log level

      The log level can be adjusted by adding logging.logger.com.atlassian.bitbucket.internal.ssh.server.SelfClosingChannelSession=WARN to $BITBUCKET_HOME/shared/bitbucket.properties

      see https://confluence.atlassian.com/bitbucketserver/bitbucket-server-config-properties-776640155.html#BitbucketServerconfigproperties-Logging.

      Runtime adjustment

      To avoid restarting the instance to apply the log level as described above, the log level can be adjusted at runtime via REST. The following example uses curl (please adjust the host and context path information, the user needs to have global administration permissions):

      curl -H'Content-Type:application/json' \
          -u USERNAME -d '' \
          -v -X PUT https://stash.example.com/rest/api/latest/logs/logger/com.atlassian.bitbucket.internal.ssh.server.SelfClosingChannelSession/WARN
      

            Assignee:
            Stefan Saasen (Inactive)
            Reporter:
            Stefan Saasen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: