Confluence Data Center Clustering page throws 'Page Not Found' error
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
Confluence Data Center Clustering page throws 'Page Not Found' error when trying to access it. However, this page may be accessible from another node. If not, proceed with the solution proposed in this article for all affected nodes.
環境
This problem was identified in Confluence server and datacenter version 6.15.9. It could also affect other versions of Confluence.
診断
The following error appears in atlassian-confluence.log:
2020-11-13 09:33:13,208 ERROR [http-nio-8090-exec-103] [atlassian.plugin.servlet.DefaultServletModuleManager] getInstance Unable to create new reference LazyLoadedFilterReference{descriptor=com.atlassian.cluster.monitoring.cluster-monitoring-plugin:atlassianClusterMonitoring-filter (null), filterConfig=com.atlassian.plugin.servlet.filter.PluginFilterConfig@5eb58e37}
-- referer: https://localhost/plugins/servlet/cluster-monitoring | url: /rest/atlassian-cluster-monitoring/cluster/nodes | traceId: 3114bd3a5658378a | userName: admin
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.RuntimeException: Could not identify Bundle at location <reference:file:/confluence_home/plugins-osgi-cache/transformed-plugins/cluster-monitoring-plugin-1.0.3_1567061682000.jar>
at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
at com.atlassian.util.concurre
...
Caused by: java.lang.RuntimeException: Could not identify Bundle at location <reference:file:/confluence_home/plugins-osgi-cache/transformed-plugins/cluster-monitoring-plugin-1.0.3_1567061682000.jar>
at com.atlassian.plugins.rest.module.scanner.AnnotatedClassScanner.scan(AnnotatedClassScanner.java:56)
原因
Plugins cache on a specific node has become corrupted.
ソリューション
Follow How to clear Confluence plugins cache to resolve the plugins cache issue on the node.