在 centos 7.0 上启动 wso2 API Manager v2.0.0 失败 [英] Failed to start wso2 API Manager v2.0.0 on centos 7.0

查看:31
本文介绍了在 centos 7.0 上启动 wso2 API Manager v2.0.0 失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试 WSO2 API Manager 2.0,但无法启动服务器.你愿意帮忙吗?非常感谢迈克尔

I am trying WSO2 API Manager 2.0 and failed to start the server. Would you like give a hand? Thanks a lot Michael

以下是版本信息.

[wso2@srv11 bin]$ ./wso2server.sh --version

WSO2 API Manager v2.0.0  
WSO2 Carbon Framework v4.4.7

但是当我使用wso2server.sh --start"命令启动API Manager时,我在wso2carbon.log中发现了以下错误信息.

But when I start the API Manager with "wso2server.sh --start" command, I found following error information in wso2carbon.log.

ID: [-1234] [] [2016-08-15 09:48:32,824]  INFO {org.wso2.andes.server.security.auth.manager.PrincipalDatabaseAuthenticationManager} -  Initialised PLAIN SASL provider successfully {org.wso2.andes.server.security.auth.manager.PrincipalDatabaseAuthenticationManager}
TID: [-1234] [] [2016-08-15 09:48:32,825]  INFO {org.wso2.andes.server.security.auth.manager.PrincipalDatabaseAuthenticationManager} -  Additional SASL providers successfully registered. {org.wso2.andes.server.security.auth.manager.PrincipalDatabaseAuthenticationManager}
TID: [-1234] [] [2016-08-15 09:48:32,825]  INFO {org.wso2.andes.server.security.auth.manager.PrincipalDatabaseAuthenticationManager} -  Registering UserManagementMBean {org.wso2.andes.server.security.auth.manager.PrincipalDatabaseAuthenticationManager}
TID: [-1] [] [2016-08-15 09:48:35,634]  WARN {java.util.prefs.FileSystemPreferences} -  Could not lock System prefs. Unix error code 32577. {java.util.prefs.FileSystemPreferences}
TID: [-1] [] [2016-08-15 09:48:35,635]  WARN {java.util.prefs.FileSystemPreferences} -  Couldn't flush system prefs: java.util.prefs.BackingStoreException: Couldn't get file lock. {java.util.prefs.FileSystemPreferences}
TID: [-1] [] [2016-08-15 09:48:52,850]  WARN {org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever} -  Failed retrieving throttling data from remote endpoint: Connection refused. Retrying after 15 seconds... {org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever}
TID: [-1] [] [2016-08-15 09:48:52,862]  WARN {org.wso2.carbon.apimgt.gateway.throttling.util.BlockingConditionRetriever} -  Failed retrieving Blocking Conditions from remote endpoint: Connection refused. Retrying after 15 seconds... {org.wso2.carbon.apimgt.gateway.throttling.util.BlockingConditionRetriever}
TID: [-1] [] [2016-08-15 09:48:53,073]  WARN {org.wso2.carbon.application.deployer.internal.AppDeployerServiceComponent} -  Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService, {org.wso2.carbon.application.deployer.internal.AppDeployerServiceComponent}
TID: [-1] [] [2016-08-15 09:48:53,092]  WARN {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Waiting for required OSGi services: org.wso2.carbon.application.deployer.service.CappDeploymentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent, {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent}
TID: [-1] [] [2016-08-15 09:49:05,628]  WARN {java.util.prefs.FileSystemPreferences} -  Could not lock System prefs. Unix error code 32577. {java.util.prefs.FileSystemPreferences}
TID: [-1] [] [2016-08-15 09:49:05,628]  WARN {java.util.prefs.FileSystemPreferences} -  Couldn't flush system prefs: java.util.prefs.BackingStoreException: Couldn't get file lock. {java.util.prefs.FileSystemPreferences}
TID: [-1] [] [2016-08-15 09:49:07,854]  WARN {org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever} -  Failed retrieving throttling data from remote endpoint: Connection refused. Retrying after 15 seconds... {org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever}
TID: [-1] [] [2016-08-15 09:49:07,865]  WARN {org.wso2.carbon.apimgt.gateway.throttling.util.BlockingConditionRetriever} -  Failed retrieving Blocking Conditions from remote endpoint: Connection refused. Retrying after 15 seconds... {org.wso2.carbon.apimgt.gateway.throttling.util.BlockingConditionRetriever}
TID: [-1] [] [2016-08-15 09:49:24,583]  WARN {org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever} -  Failed retrieving throttling data from remote endpoint: Connection refused. Retrying after 15 seconds... {org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever}
TID: [-1] [] [2016-08-15 09:49:24,593]  WARN {org.wso2.carbon.apimgt.gateway.throttling.util.BlockingConditionRetriever} -  Failed retrieving Blocking Conditions from remote endpoint: Connection refused. Retrying after 15 seconds... {org.wso2.carbon.apimgt.gateway.throttling.util.BlockingConditionRetriever}

推荐答案

出现此警告可能是由于 Java 首选项子系统无法写入目录/etc/.java/.systemPrefs.您能否验证您的系统中是否存在/etc/.java/.systemPrefs 目录?如果存在,它对运行 JVM 实例的用户是否可写?如果没有,请提供权限并重新启动 APIM.

This warning could occur due to Java Preferences subsystem not being able to write to the directory /etc/.java/.systemPrefs. Can you verify that the the directory /etc/.java/.systemPrefs exist in your system? If it exists, is it writable for the user running the JVM instance? If not please provide permission and restart APIM.

如果上述方法不起作用,您也可以尝试以下解决方法.

If the above does not work you can also try the below workaround.

1) 在运行 JVM 的用户可以访问的地方创建一个目录,并具有以下子结构./.java/.systemPrefs

1) Create a directory in a place accessible to the user running the JVM and have the following substructure. /.java/.systemPrefs

2) 使用 Java 选项 -Djava.util.prefs.systemRoot=/.java

2) Start WSO2 APIM server with the Java option -Djava.util.prefs.systemRoot=<CREATED_DIR>/.java

这篇关于在 centos 7.0 上启动 wso2 API Manager v2.0.0 失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆