Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-19812

Disabling SSH access in Bitbucket results in repeated IPD-thrown WARN messages in application log

XMLWordPrintable

      Issue Summary

      Disabling SSH access in a Bitbucket DC instance that has IPD enabled results in a long WARN log entry with an entire stack trace being added to the main atlassian-bitbucket.log application log exactly once a minute.

      Steps to Reproduce

      1. Navigate to System → Server Settings
      2. Uncheck the SSH access option to disable SSH access for the Bitbucket instance
      3. Save

      Expected Results

      SSH access is disabled with no additional log entries being generated within the application logs.

      Actual Results

      The atlassian-bitbucket.log file has a WARN log entry added to it every minute as a result of it attempting to gather SSH metrics despite SSH access being disabled:

      2025-01-08 19:33:12,304 WARN [Caesium-1-4] c.a.b.i.ipd.ssh.SshMetricsService Unable to read attribute
javax.management.InstanceNotFoundException: com.atlassian.bitbucket:name=SshSessions
at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Unknown Source)
at com.atlassian.bitbucket.internal.ipd.ssh.SshMetricsService.getSshSessionMetrics(SshMetricsService.java:38)
at com.atlassian.bitbucket.internal.ipd.ssh.SshMetricsIpdJob.runJob(SshMetricsIpdJob.java:49)
at com.atlassian.diagnostics.internal.ipd.DefaultIpdJobRunner.runJobs(DefaultIpdJobRunner.java:49)
at com.atlassian.bitbucket.internal.ipd.IpdEmitterScheduler.ipdEmitterIteration(IpdEmitterScheduler.java:68)
at com.atlassian.bitbucket.internal.ipd.SchedulerServiceJobRunner.runJob(SchedulerServiceJobRunner.java:22)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$JobRunnerWithStats.runJob(CaesiumSchedulerService.java:743)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:545)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJobWithRetryOnFailure(CaesiumSchedulerService.java:500)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:440)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35)
at java.base/java.lang.Thread.run(Unknown Source)
... 2 frames trimmed

      Workaround

      Disable In-Product Diagnostics by navigating to Troubleshooting and Support Tools → Monitoring and then toggling off the "Enable In-Product Diagnostics" toggle. Note that this will disable IPD, disabling it and its reports/functionality until toggled back on.

        1. image-2025-01-16-21-17-07-675.png
          image-2025-01-16-21-17-07-675.png
          9 kB

              csubraveti Chandravadan
              eslaughter@atlassian.com Evan Slaughter
              Votes:
              6 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: