-
Bug
-
Resolution: Fixed
-
Low
-
9.0.2, 9.1.2, 9.2.2, 8.19.12, 8.19.13, 9.3.3, 8.19.14, 9.5.1, 9.4.3
-
3
-
Severity 3 - Minor
-
22
-
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
- Navigate to System → Server Settings
- Uncheck the SSH access option to disable SSH access for the Bitbucket instance
- 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.
- causes
-
PS-177273 Loading...