时间戳

首页 > 解决方案 > Apim Analytics 不允许我同时启动 'worker' 和 'dashboard' 节点

wso2 - Apim Analytics 不允许我同时启动 'worker' 和 'dashboard' 节点

问题描述

场景：API Manager 和 APIM ANalytics 2.6.0 在同一台机器上运行。

问题：启动 APIM 工作节点后，APIM Dashboard 节点没有启动并给我很多警告如下：

JAVA_HOME environment variable is set to /usr/java/jdk1.8.0_211-amd64
CARBON_HOME environment variable is set to /opt/wso2am-analytics
RUNTIME_HOME environment variable is set to /opt/wso2am-analytics/wso2/dashboard
[2019-04-26 16:16:20,189]  INFORMAÇÕES {org.wso2.carbon.launcher.extensions.OSGiLibBundleDeployerUtils updateOSGiLib} - Successfully updated the OSGi bundle information of Carbon Runtime: dashboard
osgi> [2019-04-26 16:16:22,006]  INFO {org.wso2.msf4j.internal.websocket.EndpointsRegistryImpl} - Endpoint Registered : /websocket-provider/{topic}
[2019-04-26 16:16:22,559]  INFO {org.wso2.msf4j.internal.websocket.WebSocketServerSC} - All required capabilities are available of WebSocket service component is available.
[2019-04-26 16:16:22,571]  INFO {org.wso2.carbon.metrics.core.config.model.JmxReporterConfig} - Creating JMX reporter for Metrics with domain 'org.wso2.carbon.metrics'
[2019-04-26 16:16:22,599]  INFO {org.wso2.msf4j.internal.MicroservicesServerSC} - All microservices are available
[2019-04-26 16:16:22,599]  INFO {org.wso2.carbon.metrics.core.reporter.impl.AbstractReporter} - Started JMX reporter for Metrics
[2019-04-26 16:16:22,669]  INFO {org.wso2.msf4j.analytics.metrics.MetricsComponent} - Metrics Component is activated
[2019-04-26 16:16:22,673]  INFO {org.wso2.carbon.databridge.agent.internal.DataAgentDS} - Successfully deployed Agent Server
[2019-04-26 16:16:22,742]  INFO {org.wso2.transport.http.netty.listener.ServerConnectorBootstrap$HTTPServerConnector} - HTTP(S) Interface starting on host 0.0.0.0 and port 9643
[2019-04-26 16:17:22,535]  WARN {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} - Startup component carbon-deployment-service from bundle(org.wso2.carbon.deployment.engine:5.2.0) is in the pending state until Capability org.wso2.carbon.deployment.engine.Deployer from bundle(org.wso2.carbon.uiserver:0.19.5) is available as an OSGi service. Refer the Startup Order Resolver documentation for information.
[2019-04-26 16:17:22,536]  WARN {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} - Startup component carbon-ui-server-startup-listener from bundle(org.wso2.carbon.uiserver:0.19.5) is in the pending state, because of the Capability org.wso2.carbon.uiserver.spi.RestApiProvider from bundle(org.wso2.carbon.business.rules.core:2.0.423). If you've registered this capability as an OSGi service, you need to declare it using the Carbon-Component manifest header. Refer the Startup Order Resolver documentation for information.
[2019-04-26 16:17:22,536]  WARN {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} - Startup component carbon-ui-server-startup-listener from bundle(org.wso2.carbon.uiserver:0.19.5) is in the pending state, because of the Capability org.wso2.carbon.uiserver.spi.RestApiProvider from bundle(org.wso2.carbon.dashboards.api:4.0.38). If you've registered this capability as an OSGi service, you need to declare it using the Carbon-Component manifest header. Refer the Startup Order Resolver documentation for information.
[2019-04-26 16:17:22,536]  WARN {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} - Startup component carbon-ui-server-startup-listener from bundle(org.wso2.carbon.uiserver:0.19.5) is in the pending state until Capability org.wso2.carbon.uiserver.spi.RestApiProvider from bundle(org.wso2.carbon.data.provider:2.0.423) is available as an OSGi service. Refer the Startup Order Resolver documentation for information.
[2019-04-26 16:17:22,536]  WARN {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} - Startup component carbon-ui-server-startup-listener from bundle(org.wso2.carbon.uiserver:0.19.5) is in the pending state until Capability org.wso2.carbon.uiserver.spi.RestApiProvider from bundle(org.wso2.carbon.status.dashboard.core:2.0.423) is available as an OSGi service. Refer the Startup Order Resolver documentation for information.
[2019-04-26 16:17:22,537]  WARN {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} - Startup component sp-idp-service from bundle(org.wso2.carbon.analytics.idp.client:6.0.70) is in the pending state, because of the Capability org.wso2.carbon.analytics.idp.client.core.spi.IdPClientFactory from bundle(org.wso2.carbon.analytics.idp.client:6.0.70). If you've registered this capability as an OSGi service, you need to declare it using the Carbon-Component manifest header. Refer the Startup Order Resolver documentation for information.
[2019-04-26 16:17:22,537]  WARN {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} - Startup component sp-idp-service from bundle(org.wso2.carbon.analytics.idp.client:6.0.70) is in the pending state until Capability org.wso2.carbon.analytics.idp.client.core.spi.IdPClientFactory from bundle(org.wso2.carbon.analytics.idp.client:6.0.70) is available as an OSGi service. Refer the Startup Order Resolver documentation for information.

如果我先启动 Dashboard 节点，则在工作节点的启动中会显示相同的日志。

我只是遵循默认配置https://docs.wso2.com/display/AM260/Configuring+APIM+Analytics 和https://docs.wso2.com/display/AM260/Enabling+API-M+Analytics+Features+ in+WSO2+流+处理器

标签： wso2analyticsapi-manager

解决方案

你必须开始

  1. APIM 分析工作人员资料
  2. APIM 服务器
  3. APIM 分析仪表板配置文件，

按照上面提到的顺序一个接一个。

在这里，您必须等到第一个配置文件完全启动才能启动下一个配置文件。这样，所有的 OSGi 包都将根据Startup order resolver 文档中的顺序启动。

推荐阅读